Build & authorAssessments
Coding Problems & Test Cases
Author multi-language coding challenges with starter templates, sample cases, and hidden evaluation suites.
Clevid's coding workspace gives candidates a clean code editor with syntax highlighting, language switching, and instant feedback against sample test cases.
Anatomy of a coding question
When authoring a coding problem in Question Banks or directly inside an assessment, you define:
- Problem Statement: Clear instructions, input/output examples, and expected constraints.
- Allowed Languages & Starter Code: Provide starter function templates per language so candidates can focus on solving the problem rather than boilerplate.
- Public Sample Cases: Visible to the candidate during the test so they can verify their basic logic.
- Hidden Evaluation Suite: Used when grading the submission to check edge cases and larger inputs.
Test case verdicts
Each test case returns a clear status in the candidate's scorecard:
| Verdict | Meaning | Scoring Impact |
|---|---|---|
Passed (AC) | Output matches expected result within the time limit | Full test case points awarded |
Wrong Answer (WA) | Code ran to completion, but output did not match expected | 0 points |
Time Limit Exceeded (TLE) | Solution took longer than the allowed time limit | 0 points |
Runtime Error (RE) | Unhandled exception or crash during execution | 0 points |
Compilation Error (CE) | Syntax or build error | 0 points |