What is browser lockdown testing, and how do you verify it works before a live exam?
TL;DR: Browser lockdown testing means running a dry-run exam session yourself, on the same device types your test-takers use, to confirm tab-switching, copy-paste, screenshotting, and app-switching are actually blocked before anyone's grade depends on it. Skipping this step is how institutions discover a lockdown "hole" mid-exam, when it's too late to fix.
Claim
A lockdown browser you haven't tested is a lockdown browser you're hoping works. Reddit threads on "students can still cheat with lockdown browsers" exist because someone shipped without testing the edge cases.
Evidence
- Multiple 2026 guides ("How to Cheat Respondus Lockdown Browser," "LockDown Browser Bypass Methods") exist specifically because untested lockdown configurations leave gaps — virtual machines, secondary devices, and browser exploits are the most common.
- A Reddit r/Professors thread ("Students Can STILL Cheat With Lockdown Browsers") shows real instructor reports of workarounds that testing would have caught before go-live.
- Respondus's own documentation confirms LockDown Browser does not verify identity or detect external devices by design — it only restricts the browser tab, so testing must cover what it explicitly can't do.
Comparison: what to test vs what breaks if you skip it
| Test | What it confirms | What breaks if skipped |
|---|---|---|
| Full-screen enforcement | Can't minimize or alt-tab out | Silent tab-switching during the real exam |
| Copy/paste block | Can't paste in answers from elsewhere | Pre-written AI answers pasted undetected |
| Second-monitor check | Extra displays are flagged or blocked | Answers displayed on an unmonitored screen |
| Virtual machine/emulator check | VM environments are flagged | Candidate runs the exam inside a sandboxed VM to fake compliance |
| Network/webcam pre-flight | Confirms camera, mic, and bandwidth work | Mid-exam technical failures with no fallback plan |
Step-by-step: run a browser lockdown test before go-live
- Install the lockdown software on the same OS/browser versions your population actually uses (not just your admin laptop).
- Attempt every known bypass yourself: alt-tab, virtual machine, second device, screenshot tools.
- Test with a second monitor connected and disconnected.
- Time a full mock exam start-to-finish, including ID verification and camera checks.
- Document every failure and fix it before the live exam window opens, not during it.
FAQ
How long does a proper lockdown test take? Budget 30-60 minutes per device/OS combination you support — most institutions test 3-4 configurations (Windows, Mac, Chromebook, tablet).
Does testing the browser lockdown replace webcam monitoring? No. Lockdown browsers restrict the browser tab; they don't verify identity, watch the room, or detect a phone off-screen. You need both layers, tested separately.
What's the single most-skipped test? The second-device test. Most lockdown failures in real exams involve a phone or tablet outside the browser's control, which pure browser lockdown was never designed to catch.
By Pinal Dave Last updated: 2026-07-24