Allowing Candidates To Use Their Own IDE
Typically candidates will take a coding assessment within Qualified's web based IDE. However it is also possible to allow them to take Project Code Challenges within their own IDE. Candidates who utilize this option will be delighted to take the challenge using their own familiar development environment.
The functionality discussed is currently available as a labs feature for all customers. You must enable it before you can utilize it within your assessments.
Qualified's External IDE feature uses a small node terminal app that synchronizes files from a candidate's file system back to Qualified’s web IDE. This allows developers to work in their own IDE without needing to worry about running the challenge's dependencies on their own system.
Why a Node App?
The Node terminal app ensures that all candidate's will have a consistent testing experience, as the code that candidate's develop will still be tested against Qualified's servers, not their local machine.
Over 70% of developers surveyed by Qualified already have Node installed on their machines.
The following requirements are necessary:
- The candidate must have Node 10+ installed
- The candidate must be willing to add the qualified NPM package to their machine.
All code for the Node utility is open source and can be found here.
Enabling The Option
If you want to allow developers to use their External IDE, you can enable or disable the feature team-wide although the global setting can also be overridden for any given challenge. This feature only works with Project Code Challenges, where the value of working in your own IDE is that much more significant.
Here’s how a candidate be prompted to select their own IDE at the outset of taking a Qualified challenge.
If the candidate chooses to complete a Qualified challenge using their own IDE, they will then be asked to follow the steps outlined below to begin using your External IDE.
Once these setup steps are completed candidates can work on Qualified challenges in the comfort of their own development environment.
Code written within a candidate's external IDE will not be subject to detailed code playback—you can still use our code playback feature but it will be limited to when the candidate saves code. It is best to enable this option for candidates only if you don't wish to review detailed code playback.
External IDE is best suited to letting candidates work independently—you can’t launch an interactive session with a candidate if they’re using their own IDE, but you can still review the code that they’ve written with them via a pair-programming session thereafter.