Skip to content

Online exams you can stand behind.

You decide what students can run, see and do during a test, and every result comes with what happened. No browser test rules cheating out: Echelio makes it harder, and makes it visible.

Harder to cheat, easy to see.

Each control is on by default, and what it records is in the test’s results.

  • Copy and paste blocked

    During a test, the editor blocks copy, cut, paste and dropped text.

  • Tab switches recorded

    Each time a student leaves the test, you see when and for how long.

  • Similar code side by side

    After a code test, you see the answers most alike in the class, side by side.

Fair from the problem to the report.

  1. Before the test

    A problem’s reference solution must pass all of its cases before it can be published, so a failed case is the student’s, not the problem’s.

  2. During the test

    Code runs in an isolated sandbox with time and memory limits. Problems are shuffled per student, and leaving the page is recorded.

  3. After the test

    The report keeps the problem versions students answered, every submission and each tab switch with the time away. Each student’s final code is compared with their classmates’, and the closest answers show side by side.

The details.

Every control, and what it does.

Sandbox
Student code runs in an isolated Judge0 sandbox, never inside Echelio. Each case gets a fresh execution with time and memory limits.
Hidden cases
Students see only whether each hidden case passed, never its input, its expected result or the output.
Shuffling
Code tests run from easy to hard and shuffle the problems within each level. Quizzes shuffle questions and answer options per student.
Clipboard
Copy, cut, paste and dropped text are blocked in the editor during tests, and paste in practice too.
Similar code
Once a test with code problems ends, each student’s final code is compared with their classmates’ answers to the same problem, in JavaScript, Java, Python, PHP and SQL. Renaming, reformatting and comments don’t hide shared code. The starter code, and code most of the class writes, never make two answers alike, and problems with very short answers aren’t compared.
Quiz answers
Students move forward only, and correct answers appear only once the test closes, so a finished student can’t pass them on.

Questions about fair testing.

What schools ask before giving exams online.

Can Echelio stop all cheating?
No browser-based test can. Echelio blocks copy and paste, records every tab switch with the time away, keeps hidden cases out of the browser, shuffles problems and, after a code test, shows you the answers most alike in the class, so cheating is harder and what happened is visible.
Is it safe to run student code?
Yes. Student code never runs inside Echelio. Each case runs in an isolated sandbox, in a fresh execution with time and memory limits, and the results are compared on the server.
What does a tab switch record show?
For each switch, when the student left the test and how long they were away. It appears in the test’s results and in the CSV export.
Does Echelio use webcam proctoring?
No. Echelio does not use the camera, the microphone or screen recording.
Can I turn the controls off for a test?
Yes. Blocking copy and paste, recording tab switches, shuffling and comparing code across the class are settings of each test, all on by default.
Does Echelio check whether students’ code is alike?
Yes, once a code test ends. You see only the few pairs or groups of answers most alike, or that nothing stands out, and can open any of them side by side: shared code is highlighted in matching colours, and cases both students fail the same way are pointed out. Answers can be alike by chance, so it is a signal for you to look at: it never flags anyone or changes a score. Students are told while they take the test, and the comparison runs on Echelio’s servers, without sending code anywhere.

Give a test you can stand behind.