TestSetGo
Test security

Secure online testing built on integrity, not surveillance.

Access codes, shuffled questions, timers and attempt limits make cheating more work than the test itself. No webcam, no lockdown.

Free plan, no card neededNo webcam, no lockdownNothing tracked without disclosure
Control who gets in

Access that is easy to share and hard to abuse

Give a run a short access code, or send each participant a link that is theirs alone. Require a verified email when identity matters.

  • Access codes stored as hashes, not plain text
  • Per-participant invitation tokens you can revoke
  • Verified-email identity and rate-limited endpoints
How invitations work β†’
Keep the test fair

Every sitting is a little bit different

Shuffle questions and answer options per participant, so neighbours don't see the same order. Timers and attempt limits hold even if a tab closes.

  • Per-participant question and answer-order shuffling
  • Timers a closed tab can't extend
  • One active attempt, enforced atomically
More on the test experience β†’
Watch it live

Deterrence you can see, as it happens

Focus tracking records every switch away from the test page, question by question, after telling participants exactly what is watched. No camera, no keystrokes.

  • Focus tracking participants are told about before they start
  • Optional auto-submit after too many exits β€” answers are kept and scored
  • A live monitor with progress, time remaining and seat usage
What the results show β†’
Protect the record

Answers you can trust after the fact

Answers autosave, so a dropped connection never loses a participant's progress. If someone flags a bad question, your correction regrades every affected attempt.

  • Autosave that keeps a partial attempt intact
  • Participant abuse and problem reporting
  • Corrections regrade with an auditable trail
How corrections work β†’
The measures

Practical integrity, plainly explained

Hashed access codes

Run codes are stored as hashes, so even a glimpse of the database won't reveal them.

Question shuffling

Questions and options are ordered per participant, so copying from a neighbour is harder.

Server-side timers

The clock runs on the server, so closing the tab can't buy extra time.

Attempt limits

Cap attempts per run, with one active attempt at a time to stop parallel sittings.

Verified identity

Require a verified email when you need to be confident who is behind an answer.

Identity options β†’

Rate limiting

Entry points are rate-limited, so access codes and links can't be guessed by brute force.

Focus tracking

Record when a participant leaves the test page β€” a disclosed signal, never proof on its own.

Live monitor

Watch attempts in progress with time remaining, and end one with a recorded reason.

Seat caps

Cap how many participants can enter a run. Anyone who already started keeps their place.

Questions

Frequently asked questions

Does TestSetGo have webcam proctoring?

No, by design: no camera, no microphone, no keystroke logging, no browser lockdown. If you want behavioural deterrence, opt-in focus tracking records how often a participant leaves the test page, and tells them so before they start. Everything else is structural: access control, shuffling, timers, attempt limits and verified identity.

Can I see cheating attempts as they happen?

The live monitor shows every in-progress attempt with its progress, time remaining and focus signals. Signals are indicators, not verdicts β€” a notification or an accidental click counts too β€” so the record shows which question each exit happened on, and you decide what it means.

How are access codes kept safe?

Access codes are stored hashed rather than in plain text, and the endpoints that accept them are rate-limited, so they can't be read from the data or guessed.

Can someone open the test twice to get an advantage?

No. Only one active attempt is allowed at a time, so nobody can run two windows in parallel. Attempt limits per run also cap how often a test can be taken.

Are the time limits enforceable?

Yes. Timers run on the server, not the browser, so closing the tab, reloading or tampering with the page can't extend the window.

What stops people copying from each other?

Questions and answer options can be shuffled per participant, so no two people see the same order. With timers and one active attempt, casual copying gets much harder, without surveillance.

What happens if a participant loses connection mid-test?

Their answers autosave as they go, so a dropped connection or closed tab doesn't lose their work. They resume where they left off, within the run's time limit.

Run a test you can stand behind

Set an access code, a timer and an attempt limit, and deliver a fair test without spying on anyone.

Create a free testFree plan Β· no card required