Our Product, Engineering, and Content teams hit the ground running in Q3 with a major round of product updates, new features, bug fixes, and behind-the-scenes improvements. We’re highlighting 3 major updates that went live in July:
- Archiving tests
- Creating frontend tasks with Puppeteer tests
- More flexibility in connecting to databases
Do you have one or more tests in your CodeSignal account that your company no longer uses? You may find it helpful to archive these tests—especially if you have a high volume of tests in your account. Archived tests can easily be accessed or unarchived if needed.
Learn more about how to archive tests in this article:
Creating frontend tasks with Puppeteer tests
Creating test cases for algorithmic tasks is fairly simple: all you need to do, at a minimum, is specify the input and the output. Creating tests for frontend tasks is a bit more complex, since you want to evaluate how well a candidate’s code runs in a browser. With the browser testing tool, Puppeteer, creating test files for frontend tasks is much easier.
With this update, CodeSignal now supports adding and writing custom Puppeteer tests for frontend tasks directly from our task creation UI. This allows your custom frontend tasks to have automated scoring—and lets you skip the step of collaborating with our Content team to do this.
Learn more about creating a frontend task with Puppeteer tests in this article:
More flexibility in connecting to databases
With a major infrastructure change we launched this month, any supported database can now be accessed by any of CodeSignal’s general coding languages. A candidate, for instance, can access a MySQL database from Java or PostgreSQL from C#—or any other combination of coding languages and supported databases!
Learn more about creating database tasks in this article:
Here's a comprehensive list of everything else we pushed live in July, grouped by product area:
- Auth Integrations
- Admin Tools
- B2B General
- Data Migrations
- Saved run requests now store all source code to make debugging easier for CodeSignal’s content team.
- Candidates will now only receive a score of 300 if they don't ever press “submit” for any task.
- The proctoring setup progress bar has been moved to the left side of the screen. This guarantees it will not conflict with Chrome or Firefox's screen sharing notification.
- Candidates may now elect to share a currently-ongoing test session in response to another company's request for the same test result.
- The histograms for task score distribution have been visually updated.
- The practice test now includes illustrative slides for free-text questions.
- It is now possible to download a PDF report of an Interview session.
- CodeSignal admins viewing a client user's dashboard can now edit pending and active interviews.
- When within an interview template, opening the Tasks & Templates menu and selecting the same task outside of the template will close the template.
- When within a loaded test session, selecting the already-selected task from the dropdown will no longer cause the candidate's page to spin infinitely.
- Performing the "reset code" action during an interview with a test session loaded now resets to the solution from the test session, rather than to the generic starter code for the task.
- CodeSignal no longer prompts for confirmation before unselecting an interview template during an interview in the case where there is no customized feedback associated with the template.
- Users are now prompted to select their preferred IDE layout when first viewing the IDE.
- The user’s choice is then saved for later.
- This will not show during real tests or interviews (but it can show up during the practice test or in review mode).
- Fixed an issue with the frontend task type where the script & stylesheet resources were not being properly included when running Puppeteer tests, even though they were included in the preview.
- The hotkeys for Run & Submit have been updated.
- Old hotkeys were Ctrl + R and Ctrl + Enter; new hotkeys are Ctrl + Enter and Ctrl + Alt + Enter (Cmd + Return and Cmd + Opt + Return, for Mac users.)
- To mitigate accidental refreshes for those familiar with the old hotkeys, we've added a confirmation before leaving the page or refreshing when viewing a task during an assessment or in the task creator/editor.
- Filesystem: Developers are now blocked from attempting to edit or rename a folder containing a locked file.
- Free-coding: Fixed an incorrect print syntax in the Python 3 "Syntax Tips" section for free-coding tasks.
- Fixed an issue with replays of filesystem tasks where very large output could crash recordings.
- Fixed a bug with recovery tasks where users were not warned about changes outside of the recovery area if they were added at the very beginning or very end of the file.
- The IDE settings sidebar is now available for all coding task creation types.
- SQL Task creation: Fixed an issue where test case numbers weren't correctly updated in error messages after reordering.
- GraphQL: Labels can now be queried on a task.
- The authentication/authorization flow for LinkedIn Talent Hub has been updated to allow confirming the CodeSignal account or returning to LinkedIn.
- The Lever integration will no longer post duplicate notes if the API key is incorrectly configured with permission to create notes but not delete them.
- We now expose SCIM endpoints compatible with SCIM v2.0.
- It is now possible for CodeSignal admins to delete unused system or company roles.
- Universal search
- We’ve added a search bar in the top-right of the B2B header that allows searching across the company account for candidates (test sessions & interview sessions) and resources (certification tests, company tests, interview templates & tasks).
- Automatically migrated Java filesystem tasks in all environments to use Gradle 7-compatible syntax instead of deprecated syntax from Gradle 6 or earlier.
- Coderunner releases v5.1.2, v4.16.3, v5.0.0, v5.1.0 & v5.1.1
- Fixed issue with running sample tests in TypeScript/Mocha.
- MySQL driver for Go.
- tidyverse package for R.
- Java 16, Gradle 7 for filesystem tasks.
- Updated which Java filesystem libraries are cached to reflect the ones used most often.