An instructor helping two students at their computers

For instructors of university programming courses

Assess the code. Check the understanding.

Review programming submissions against your own criteria, then check understanding with questions generated from each student's submitted code.

See how it works Try GradeInstant

Used in programming courses atVilnius Universityplus a university in Canada and 7 more institutions on 4 continents · 700+ assignments · 320+ quizzes

Working code is not the same as understood code.

Tests and autograders show whether code behaves correctly. They don't show whether the student can explain the logic and choices in the code they handed in.

Vivas and walkthroughs can, but they're hard to repeat for every student and every assignment.

How it works

1
Set the assignment and criteria
You define what gets assessed.
2
Students submit their work
A file or ZIP, a GitHub repository or a Google Colab link.
3
Review the code assessment
Scores per criterion, with the reasoning and code evidence behind them.
4
Check individual understanding
Each student answers questions generated from their own code.

GradeInstant feedback view: a criterion with its score, comments and the code evidence it is based on — The feedback view for a test submission.

The instructor keeps the final say.

You set the criteria and their weighting. For each criterion you see a score, the reasoning behind it and the lines of code it's based on, and you can change any grade. Quiz length, timing and attempts are yours to set too.

Questions tied to the student's own code.

Questions come from each student's submitted implementation, not a shared question bank, so every student gets a different quiz. The result is an extra signal of understanding for you to weigh alongside the work itself.