- What is TestInvite?
- Build Your First Test
- Run Your First Assessment
- Taking the Assessment
- Viewing the Results
- Question Bank Overview
- Common Question Features
- Question Types
- Creating Questions
- Organizing Questions
- Content Blocks
- Roles & Access
- Media Library
- Import & Export
- Question Submissions
- Question Bank Schema
- Browsing Questions
- Cloning Questions
- Bulk Updating Questions
- Tests Overview
- My Tests
- Creating a Test
- The Test Editor
- Test Settings
- Sections & Pages
- Adding Questions
- Page Builders
- Test Profile
- Reporting
- Test Papers
- Analytics
- Publishing a Test
- Test Library
- Marketplace
- Tasks Overview
- Creating a Task
- Task Dashboard
- Steps
- Task Settings
- Candidates
- Test Sessions
- Sent Mails
- Proctoring
- Analytics
Code
Ask candidates to write code in a professional editor with syntax highlighting for 48 languages, optionally pre-fill starter code, and evaluate with AI grading, rubrics, or manual review.
A Code question gives the candidate a professional in-browser code editor (the same editor that powers VS Code) with syntax highlighting, bracket matching, and indentation for the language you choose. Candidates write or complete code as their answer; the code is stored as text and evaluated by AI, a rubric, or a human reviewer.
Language Selection
Choose the language when creating the question — it drives the editor's highlighting and tells the AI evaluator what to expect. 48 languages are supported, including:
JavaScript, TypeScript, Python, Java, C++, C#, Go, Rust, PHP, Ruby, Swift, Kotlin-style JVM code via Java, R, Perl, Lua, Scheme, Clojure, F#, Visual Basic, Objective-C, Solidity — plus SQL dialects (SQL, MySQL, PostgreSQL, Redshift, Redis, MSDAX, Power Query), web and markup languages (HTML, CSS, SCSS, Less, XML, JSON, YAML, Markdown, Pug, Handlebars, Razor), and ops formats (Shell, PowerShell, Bat, Dockerfile, INI, Azure CLI).
Initial Code Template
You can pre-fill the editor with starter code — a function signature to complete, a class skeleton, a buggy snippet to fix, or a dataset definition. The candidate edits from there.
Evaluation
Code is not compiled or executed — evaluation judges the written code itself:
- AI Evaluation — write a grading prompt describing what a correct solution must do and how to award partial credit (e.g. “full marks for a correct O(n) solution; half marks if correct but O(n²); check edge cases: empty input, negative numbers”). See AI Evaluation.
- Rubric scoring — attach a rubric with criteria such as correctness, readability, efficiency, and error handling for consistent human review. See Rubric Scoring.
- Manual review — reviewers read the code in the evaluation screens and score it directly.
Common Features
Code questions support all shared question features — layout with a sidebar (ideal for showing a specification or dataset next to the editor), hints, answer explanations, scoring multipliers and dimensions, folders and tags. See Common Question Features.
Combine a sidebar layout (the problem specification stays visible while coding) with an initial template (the function signature) and an AI grading prompt — candidates get a realistic coding experience and you get instant, consistent first-pass scoring.