This November, our Product and Engineering teams delivered a cornucopia of awesome autumnal updates across all product areas. We’re highlighting three noteworthy changes in these release notes:
- Revised cooldown period rules for candidates taking certified assessments
- Rejected assessment results are now maintained in the Certify dashboard
- Enhanced safeguards for deleting teams
Revised cooldown period rules for candidates taking certified assessments
Cooldown periods help maintain the validity of CodeSignal assessments by preventing candidates from taking a certified assessment (like the GCA) over and over again in a short period of time. However, the cooldown period occasionally caused difficulties for candidates invited to take both proctored and non-proctored versions of an assessment.
Now, candidates will now be able to automatically bypass the cooldown period for a proctored assessment after they have completed a non-proctored version of the same assessment. Note that if a candidate has pending requests for both proctored and non-proctored versions for the same assessment, the candidate has to take the proctored request first.
Want more information to share with your candidates about cooldown periods and proctoring in CodeSignal? Have them check out these candidate-facing support articles:
- What is a cooldown period and how does it impact my ability to take a certified assessment?
- What is proctoring and how does it work?
Rejected assessment results are now maintained in the Certify dashboard
All candidates who complete a CodeSignal certified assessment receive a coding score and coding report, even if those results are rejected due to a violation of our proctoring rules. CodeSignal previously did not maintain rejected results in customers’ Certify dashboards—until now.
Company users can now see coding scores and coding reports for all their certified assessments results, including rejected results.
For more information on viewing certified assessment results and statuses, check out these articles:
Enhanced safeguards for deleting teams
For companies with a large library of custom CodeSignal tests and interview templates, teams are an excellent way to stay organized and enhance security. A new update to our platform makes it easier and safer to delete teams you no longer need—even when those teams have specific resources assigned to them.
Now, when an admin attempts to delete a team that has tests, templates, and active or pending interviews assigned to that team, the admin will be prompted to reassign those resources and interviews before the team can be deleted. This ensures that resources and interviews assigned to a team are not lost if that team is removed.
Here's a comprehensive list of everything else we pushed live in November, grouped by product area:
- Fixed bug that prevented core skills charts in Certify coding reports from showing colors
- Candidates will now have the expiration date of their retakes communicated directly in the retake email
- Fixed bug where a randomly selected author received notifications when a Test was sent from an ATS when no default sender was configured
- Fixed bug where candidates needed to re-select their environment choice for each multi-environment task in a Test
- Users are now told to enable third-party cookies if Miro doesn’t load
- IDE panel is now fully responsive to resizing
- Fixed bug with React Native preview in candidates’ solutions
- Fixed bug where default React libraries were duplicated when duplicating a free-frontend task
- Fixed bug where filesystem frontend tasks missing the preview were being re-imported with the Puppeteer testing framework
- Fixed bug in multi-environment tasks where, when switching between environments, leaving, and returning, the prior language would sometimes be selected instead of the latest one
- Fixed bug where, when reviewing solutions for a frontend task, all languages used would show up instead of just those from the final solution (e.g., users might see both SCSS and CSS)
- Fixed bug where users would sometimes receive a "ghost" notification on session timeout, which could prompt an email saying "You have 1 unread notification(s) on CodeSignal."
- Candidates’ code is now automatically updated when the replay slider is dragged
- Replay speed is now retained after pauses
- Added new Segment tracking for task/companyTest/practiceTest/certificationTest/interviewTemplate created/Updated events
- Switched to using recaptcha.net instead of google.com. Now, ReCaptcha should load in China (to help with logging in).
- A single authentication error message is now used to prevent user enumeration/
- Previous messages of “User not found" error when user tries to login with password” and "User not found" error when user tries to reset password are now replaced with a single “sign-in failed” message.
- Permissions are now properly checked when test reports are shared with client users
- Coderunner releases v6.1.4 & v6.1.5
- SQL stability fixes
- Compensates for the time spent on creating database pool resources
- Fixed race condition that could lead to occasional Microsoft SQL execution error
- Filesystem unit tests
- Now, Mocha unit tests run in the same directory regardless of whether they are run "raw" or in "pretty" mode
- Language image updates
- Dart updated from v1 to v2
- Flutter support added
- Improved support for Jupyter in Python & R images
- DevOps tasks
- Trimmed MongoDB begin/end output
- Other execution improvements
- Fixed bug where Solution.class artifact wasn't cleaned up on each execution. In persistent session tasks where Java code was run once but then had a compilation error introduced later, this bug could cause confusion by showing older results instead of the latest error.
- Allow configurable default 'main' file name for non-filesystem tasks
- Improve syntax vs. runtime error classification for PHP, Scala, & Python 3
- SQL stability fixes