Pareeksa
Team testing guide

The app is live. Here's how to test it — step by step.

No technical knowledge needed. Just follow along.
pareeksa.pages.dev ↗
01 / 10
First, what are we testing?

Pareeksa is an app for marking exams on a screen.

Instead of marking paper answer sheets by hand, teachers open scanned answer sheets in this app, write on them, and give scores — while a webcam confirms the right teacher is doing the marking.

We've built the whole thing. Now we need you to use it like a real teacher or exam officer would, and tell us anything that breaks, confuses you, or just feels wrong. You don't need to understand how it works — if a normal person can't figure it out, that's exactly what we want to know.

02 / 10
Step 1 · The one thing we need from you first

Send Adnan 5 to 7 email addresses.

Different people play different roles, so together we can test the whole exam from start to finish. Here's exactly who we need and why:

How manyRoleWhat it's used for
1Exam Controller
(Admin)
Sets up the exam, uploads the question paper, assigns markers, and publishes results. The “in charge” account. Needs a Google email.
1Moderator When two markers give different scores to the same paper, this person decides the final mark — without ever seeing the student's name. Needs a Google email.
3–5Markers
(Teachers)
The people who actually read and score answer sheets. We need at least two so two can mark the same paper and the moderator can settle a clash. More = more realistic. Any email works.
0–1Sub-admin
(optional)
A helper who only sees the parts you allow. Nice to test, not essential. Any email.
5–7Send these to Adnan — he switches each account on. Then everyone just signs in.
03 / 10
Step 1 · A note on the emails

Google email, or any email?

  • GAdmin & Moderator → must be a Google account (a Gmail address, or a Google Workspace email). These powerful roles sign in with the “Continue with Google” button, so the address has to be a Google one.
  • Markers → any email at all Teachers sign in by typing their email and clicking a one-time link we send them — so any email address works, Google or not.

Also handy to know: one person can hold more than one role. But to test the full flow you want at least 2 different markers + 1 moderator + 1 admin = 4 real people minimum.

04 / 10
Step 2 · Getting in

Signing in takes three clicks.

  • 1Open pareeksa.pages.dev in Chrome, Edge, or Safari. Use a laptop, or a tablet if you want to test marking with a pen.
  • 2Sign in. Admin / Moderator → click “Continue with Google”. Marker → type your email, then open the link we email you.
  • 3You arrive on your home screen. That's it — you're in. If it says you're not allowed in, your account isn't switched on yet — message Adnan your email + role.
05 / 10
Step 3 · Your tick-box checklist

Download the checklist and just go down the list.

We've written out every single thing to try, in plain language — “do this, you should see that.” Open it in Excel or Google Sheets, do each row, and pick Worked / Broke / Felt off / Couldn't test from the dropdown. Only do the rows for your role — others cover the rest.

XLSX Download the testing checklist

Three tabs inside: Start Here (this summary), Test Checklist (every step), and Report a Bug (to log anything that goes wrong).

06 / 10
Good news — the basics already work

You're not starting from zero.

The app runs hundreds of automatic tests on every change, and they all pass. So these already work — you don't need to prove they function, just notice if they feel wrong:

  • The whole exam flow runs end-to-end automatically: set up an exam → scan in papers → assign markers → mark → settle disagreements → publish results & mark sheets.
  • Markers never see student identities; the system keeps that wall up, and it's tested on the live servers.
  • The live app is healthy — sign-in, the databases, and file storage are all connected and responding right now.

Translation: focus your energy on how it feels to use, not on whether the buttons technically work.

07 / 10
This is where we really need you

Things a computer can't test for us.

  • The face check (most important). Does it capture your face when you enrol? When you start marking, does it recognise YOU? If you walk away, does it lock — and let you back in when you return? Does it ever wrongly lock you out, or let the wrong person in?
  • Does marking actually feel good? On a laptop, and a tablet with a pen if you have one. Score several papers in a row — is it quick, comfortable, easy to read?
  • Can you read the scanned handwriting? Zoom, rotate, pan — can you actually read and fairly mark a real answer sheet on the screen?
  • Does the AI rubric make sense? As an admin, upload a real question paper and see if the marking scheme it suggests is sensible before you edit it.
  • Is it fast on your internet? Do scanned pages load quickly where you are? Tell us if anything drags.
08 / 10
When something goes wrong

Tell us four simple things.

  • 1Where were you? (which screen, or copy the web address)
  • 2What did you do just before?
  • 3What did you expect to happen?
  • 4What actually happened? A screenshot helps a lot.

Use the “Report a Bug” tab in the checklist, or just message Adnan. Nothing is too small — “this felt slow” or “I couldn't find the button” is gold to us.

09 / 10
Quick reference

Everything in one place.

Send Adnan5–7 emails · 1 admin · 1 moderator · 3–5 markers
Admin / Moderatorsign in with Google
Markersany email → one-time link
Test hardestthe webcam / face check, and real marking
Problems →the “Report a Bug” tab, or Adnan
Pareeksa — the exam, examined.
10 / 10
↓ scroll  ·  → / space to advance