Coding screens
A coding screen is a timed take-home that a candidate works through in a real project, in the browser, with a terminal and the project's tests. These articles cover the settings on a screen, how candidates run tests, how your team reviews a submission, and which integrity signals Kendor records along the way.
Coding screen settingsSet the time limit, invite expiry, default reviewers and who can be invited, then unpublish, archive, restore or delete a screen.How candidates run tests in a coding screenCandidates run the project's own tests from the Tests tab or the terminal. Print TAP from the test command to get one row per test.How to review a coding screen submissionOpen the attempt from Candidates, read the code, replay and activity, rate it, record a recommendation, then advance or reject.What integrity signals does Kendor record?With proctoring on, Kendor logs tab switches, outside pastes and fullscreen exits, with times. It never decides anything from them on its own.