We are happy to announce that we have added support for version 1.7 of Kotlin on our general-purpose backend coding environment (CodeLysis).
This update comes with support for auto-complete and language support (IntelliSense) in Kotlin as well.
Clients will be able to select Kotlin 1.7 while creating or editing questions and test takers will be able to attempt coding questions in Kotlin 1.7 wherever available.
We are happy to announce that we have added support for the latest LTS (Long Term Support) version available for Java i.e., Java 17 on our general-purpose backend coding environment (CodeLysis).
This update comes with support for IntelliSense in Java 17 as well.
Clients will be able to select Java 17 while creating or editing questions and test-takers will be able to attempt coding questions in Java 17 wherever available.
We are excited to announce a much-awaited feature to view the console output for “Run Test Cases” while creating project-based questions (I/O). This feature will allow access to logs and will further improve the overall debugging process involved in writing test cases while creating project-based questions questions.
In case there are multiple command sets and/or prerequisite goals, output for each of them will be displayed separately.
To understand more about Mercer | Mettl’s project-based development environment, click here.
We are thrilled to share that we have revamped the UI and UX of our Front-end Simulator (FES). The improved UI provides test-takers with larger area for writing codes and viewing the output.
The new UX brings along a walkthrough, highlighting the key components of the interface and features like auto code complete and language support (IntelliSense) to assist test-takers in writing faster and efficient codes.
Hope you are as excited as us to let test-takers take a feel of the all-new interface of our front-end coding environment!
In continuation with our enhancements on our general purpose backend coding environment (CodeLysis) w.r.t Plagiarism calculation, we have added specific reasoning for test-takers whose plagiarism score is tagged as N/A.
There are multiple reasons a test-taker’s plagiarism score can be tagged as N/A and hence, this enhancement will let users know the exact reason behind this particular tag.
Alongside this, accessing Mercer | Mettl’s documentation on Plagiarism calculation directly from the test-taker’s report is now just a click way.
We are officially an assessment partner of Workable, a leading global Applicant Tracking System!
Workable is used by the likes of Eurostar, Luxasia, Ryanair, etc. and our partnership with Workable is an important milestone in our journey of Going Global!
Through this integration, you will be able to:
The older/existing invite email was limited in customizations. Customers weren’t able to change the subject, changes to the email body were restrictive and there were no dynamic variables to create more effective emails. This created multiple pain-points for customers and internal teams for a feature that was heavily used.
Invite emails are now fully customizable, easier to use and also come bundled with preview emails capability, dynamic variables and many useful features. Here’s a quick overview of some exciting new possibilities:
Template customization view:
Preview Email:
We have introduced an option to add and view notes for environments that are created in project-based questions (I/O).
This will be helpful in storing and accessing important information or metadata related to the environments such as DB credentials, configurations, environment variables, value for properties used in a project, etc.
Notes for an environment can be added/viewed by clicking the “Notes” action icon present towards the right of the environment name on the manage and select environment pages.
Users will be able to add, edit and view notes to the environments that they create. For “Mettl Environments”, users will only be able to view the notes.
To understand more about Mercer | Mettl’s project-based development environment, click here.
We are extremely excited to inform that we have made major enhancements w.r.t plagiarism score calculations on our general-purpose backend coding environment (CodeLysis).
Below mentioned are the key highlights:
We will now be able to support even larger-scale drives seamlessly.
The recent changes have optimized the plagiarism calculation, thereby reducing the overall TAT drastically.
We have made multiple advancements and changes to improve the quality of scores calculated in order to provide valid potential matches between test-taker codes. The changes in our improvement have significantly brought-down the number of false positives.
Additionally, we have introduced new tags such as N/A and No Matches to classify test-takers basis their plagiarism scores for faster and easier filtration rather than using the traditional Acceptable and Not-Acceptable.
Find more details here: [Link]
By default, our plagiarism threshold is fixed at 60%, but now users can customise this value basis their requirement. As soon as the threshold is configured (before or after the drive), the changes will be reflected in the reports and the test-takers will be tagged into suitable plagiarism tags accordingly.
Here’s a step-by-step guide: [Link]
Behavioral Competencies
Cognitive Competencies
Coding Competencies
Domain Competencies
