Meet us at DIDAC India 2026DIDAC 2026· 25–27 Nov · BIEC Bengaluru · Stall G-60· Stall G-60 · 25–27 NovBook a 20-min slot →Book →
Assessments · Coding Challenges

Coding questions that run. Marks that follow the test cases.

Learners write code in an editor inside the lesson or the exam. Each answer runs against your sample and hidden test cases, and the marks follow the hidden cases it passes. Staff see every verdict, the runtime and the code itself.

  • Python, JavaScript, C, C++, Java and Go
  • Sample and hidden test cases
  • Marks for each hidden case passed
  • Every submission saved for review
two-sum · DSA 101 · Time 2.0s · Mem 256 MB
Proctored
solution.pyPython 3.11Saved
1def two_sum(nums, target):
2 seen = {}
3for i, n in enumerate(nums):
4if target - n in seen:
5return [seen[target - n], i]
6 seen[n] = i
7return []
Run sampleSubmit · Judge0
Test cases · 5 / 6 passed83%
Sample 14ms14.2 MB AC
Sample 23ms14.1 MB AC
Hidden 16ms14.4 MB AC
Hidden 25ms14.3 MB AC
Hidden 3 · 10^6 array>2000ms— TLE
Hidden 4 · empty input3ms14.1 MB AC
Hidden case 6 failed: wrong answer on an empty list

Staff can open this answer with its runtime and code · sample data

Auto-graded: 17.5 / 20 · partial credit (5/6 cases) · answer kept for staff review.

Why teams switch

The status quo is costing your team time and money

Generic exam tools cannot run code

Most exam tools treat code as a block of text. Learners paste it in, a teaching assistant reads it by eye, and results take a week.

Code runs against your test cases automatically

A separate coding platform is one more tool

A stand-alone judge means another login for learners, another place for marks, and a spreadsheet to join the two.

Coding questions sit in the same exam as the rest

Pass or fail hides what a learner half knows

A single verdict tells a learner nothing about how close the answer was, and tells you nothing about which cases trip the class up.

Marks in proportion to the hidden cases passed

Inside the IDE

Run code, see the verdict, review the answer: one screen

An in-browser editor with sample and hidden test cases, a result for each case, and the submitted code kept for staff to review.

two-sum · DSA 101 · Time 2.0s · Mem 256 MB
Proctored
solution.pyPython 3.11Saved
1def two_sum(nums, target):
2 seen = {}
3for i, n in enumerate(nums):
4if target - n in seen:
5return [seen[target - n], i]
6 seen[n] = i
7return []
Run sampleSubmit · Judge0
Test cases · 5 / 6 passed83%
Sample 14ms14.2 MB AC
Sample 23ms14.1 MB AC
Hidden 16ms14.4 MB AC
Hidden 25ms14.3 MB AC
Hidden 3 · 10^6 array>2000ms— TLE
Hidden 4 · empty input3ms14.1 MB AC
Hidden case 6 failed: wrong answer on an empty list

Staff can open this answer with its runtime and code · sample data

Auto-graded: 17.5 / 20 · partial credit (5/6 cases) · answer kept for staff review.

How a coding question works

From problem statement to marked answer in one workspace

Writing the problem, attempting it, running it and reviewing it all happen inside the same exam or lesson.

01

Write the problem

Write the statement, add sample test cases that learners can see and hidden ones that decide the marks, and choose the languages you allow.

02

The learner solves it in the browser

An editor inside the exam, with nothing to install. Learners run their code on the sample cases before they submit.

03

Submit and mark

The answer runs against every test case and comes back with a verdict and a result for each case. Marks follow the share of hidden cases passed.

04

Review

Staff open any answer to see its verdict, a bar of the cases passed, each test result, the runtime and the submitted code.

What's inside

Coding practice in lessons, coding questions in exams

Map these to your workflow →

Six languages

Python 3, JavaScript, C, C++, Java and Go. You choose which of them a question accepts.

Sample and hidden test cases

Sample cases show the format and give quick feedback. Hidden cases decide the marks, and reports show the two separately.

Partial marks

An answer earns marks in proportion to the hidden test cases it passes, so a nearly right solution is not scored as zero.

Code inside lessons

Code editor slides let learners write and run code against starter files inside a course. Jupyter notebooks and Scratch projects can be lessons too.

Every answer kept

Each submission is saved. Staff list the answers for a question and open any one with its verdict, runtime and source code.

Camera proctoring for exams

Optional camera checks, snapshots and flags when a learner leaves the tab or full screen. There is no secure browser and no code-similarity checker.

The facts

What a coding question gives you

6
Languages

Python 3, JavaScript, C, C++, Java and Go.

2
Kinds of test case

Sample cases the learner can see, and hidden cases that decide the marks.

1
Paper

Multiple choice, written and coding questions in the same exam, with one total.

Every
Submission kept

Staff open any answer with its verdict, runtime and code.

Wired into the platform

Coding marks count like any other marks

A coding answer is part of the exam, not a file beside it. Its marks join the total, the report and the result.

Marks for a coding question add to the exam total with the multiple choice and written answers.

Reports show results on hidden and sample test cases separately.

A chapter can stay locked until the one before it is finished.

Results follow the exam's release rule: at once, after the exam, or when a teacher releases them.

Built for every team

Who uses coding questions on Vacademy

Coding schools and academies

  • Weekly tests marked against hidden test cases
  • Practice inside the lesson, with starter code
  • One record of every learner's answers over a term

Colleges and universities

  • Lab assignments submitted and run online
  • Coding and theory questions in one paper
  • Camera proctoring for tests taken at a distance

Schools

  • Scratch projects for younger learners
  • Python lessons with a code editor on the page
  • Jupyter notebooks for data and science topics

Example scenario

A coding school

“Our weekly tests used to mean a teaching assistant reading code by eye. Now each answer runs against hidden test cases, the marks appear at once, and we open only the answers that need a second look.”

— Founder, coding school

A made-up example to show how this is used. No customer said these words, and the numbers are not measurements.

Marks follow the hidden test cases passed
Every submission kept with its runtime and code
Coding and theory questions in one paper

Frequently asked

Common questions from buyers

Which programming languages are supported?+

Python 3, JavaScript, C, C++, Java and Go. You choose which of them each question accepts.

How is a coding answer marked?+

The answer runs against your test cases. Sample cases are for the learner's own check. Hidden cases decide the marks, in proportion to how many the answer passes.

What about cheating in remote tests?+

You can switch on camera proctoring: checks for a missing face or a second person, snapshots, and flags when a learner leaves the tab or full screen. Vacademy has no secure browser and no code-similarity checker, so plan for those separately if a test needs them.

Can learners practise before the exam?+

Yes. Code editor slides inside a course let learners write and run code against starter files, and every submission is saved for staff to review. Jupyter notebooks and Scratch projects can be added as lessons.

Can a coding question sit in the same paper as other questions?+

Yes. A paper can mix multiple choice, written and coding questions, each marked in its own way, with one total and one report.

Try it with your own problems

Bring one problem set to a call

We set it up with its test cases, run a trial test with your batch, and show you the answers and marks as your staff will see them.