Skip to content

CONDUCTOR-GUIDE.md

Latest commit

 

History

History
53 lines (34 loc) · 3.93 KB

CONDUCTOR-GUIDE.md

File metadata and controls

53 lines (34 loc) · 3.93 KB
Raw

Aerele Proctor — Conductor's Quick Guide

One page. Everything you need to run today's proctored coding test.

Audience. This guide is for a non-technical on-site conductor (e.g. a college contact or room supervisor) running the test day with support on call. If you are the platform operator/admin setting the round up and watching the live console, use EXAM-DAY-OPS.md instead (it names the exact admin surfaces and routes).

TODAY • The admin console URL, admin password, and the candidate (test) link are sent to you separately by message — keep them handy. The admin URL and password are for you only; never share them with students. • Exam window: __:__ – __:__ • Stuck? Call / WhatsApp Aerele: __________ — we answer instantly during the test.

What it is (10 seconds)

A coding test wrapped in proctoring: each student shares their screen + camera and works in locked fullscreen while it's recorded. You watch a live admin console; afterwards you get ranked results with integrity flags.

1 · Before students arrive — admin console (do this first)

Open …/admin and unlock with the admin password.

  • Contests tab → open today's contest (it may already be created) and check the exam window.
  • Turn "Simplified fullscreen recovery" ON (Contests → today's contest → settings). Confirm it's ON before anyone logs in — it lets a student who drops fullscreen just click a button to return, instead of typing a phrase under a countdown. Keeps honest students from being penalised. It can be flipped live, but set it now.
  • Copy the candidate link and get it to students (project it / paste in chat / share the URL). This link is the test link.

2 · What each student does (read this out)

  1. Open the candidate link in Google Chrome.
  2. Grant permissions: share the ENTIRE screen (not a tab/window), and allow camera, microphone, and clipboard. Recording starts here.
  3. Enter fullscreen.
  4. Type their own details — roll number (this is their identity; there is no pre-loaded roster today), name, email, and Room (tell them what to enter — today: __________). Confirm.
  5. Solve the problems, then press End test when finished.

3 · While the test runs — what to watch

The Live stats · Alerts · Sessions tabs are your main view — everyone, in real time. If you glance at a student's screen: a slim dark strip on top = healthy; a big RED banner = a live problem (left fullscreen, lost screen-share, or recording stopped) → walk over.

Three things that come up:

  • Camera / mic won't start. Use Chrome. Click the camera icon in the address bar → Allow → reload. On Mac: System Settings → Privacy → Camera and Screen Recording → enable Chrome → reload. Still stuck after two tries → call support.
  • A session LOCKS (student left fullscreen too many times). Sessions tab → open that student → Generate unlock code → read the 6-digit code aloud to that one student (it's a one-time code, not their login). They type it to resume. A plain refresh on the same device resumes on its own — no action needed.
  • "Pending approval" on a roll. Someone opened that roll on a second device while the first session is still live (anti-impersonation — we never run two live sessions on one roll). Genuine device switch → Approve from the Sessions tab. Not sure it's the same person → leave it; it clears when the first session ends.

Roll typos: rolls ignore case and spaces, so a duplicate sees "already logged in" → have them re-check and retype their exact roll.

4 · After the test

Results tab → ranked scores with an integrity column → export CSV, and run the on-demand evaluation for integrity signals. Recordings tab → screen + camera playback with an events timeline.

Aerele Proctor