How to make an online test, start to finish.

A weekly class test

A teacher builds a twelve-question test from the week's chapter: eight single choice, three fill-in-the-blank, and one free text question asking students to explain a key idea. She sets a twenty-minute whole-quiz timer, shuffles questions, allows one attempt, and shares the link in the class group on Friday with a Sunday evening deadline.

On Monday, Question Performance shows which two questions most students missed, and the lesson begins there.

A coaching centre mock test

A coaching centre runs a full mock with the same number of questions and time limit as the real exam, questions shuffled, and the leaderboard turned on so students can see their rank. Each student must enter their email and verify it with a one-time code, so the rankings reflect real, identifiable students.

A job applicant screening test

An employer creates a fifteen-question test on skills the role actually requires, using scenario questions based on real tasks. Candidates provide their name, email, and phone, verify their email, and get one attempt with a thirty-minute limit. Results are exported as CSV and shared with the hiring team.

A post-training check

After a workshop, a trainer shares a ten-question test by QR code before participants leave the room. Questions are drafted by AI from the workshop handout and reviewed. The results show which parts of the session were understood and which need a follow-up email or a short refresher.

A revision test with retakes

Before exams, a teacher creates a revision test from questions bookmarked in Revision across the term. Multiple attempts are allowed, and there is no timer. Students take it, check what they got wrong, revise, and try again, watching their scores improve with each attempt.

Common setup mistakes

The most common mistakes are unrealistic time limits, forgetting to turn off multiple attempts for graded tests, collecting no contact details and then being unable to identify participants, and sharing before checking the answer key. A quick review of the settings step, and taking the test yourself once, prevents almost all of them.

Choosing the length

Match length to purpose. A quick check needs five questions, a weekly test ten to fifteen, and a unit test or mock enough to cover every topic fairly. Longer is not better: every question should earn its place by testing something that matters. Participants concentrate better on shorter, focused tests.

Sharing the right way

For remote participants, send the link by message or email with a short note on topic, time limit, attempts, and deadline. For in-person sessions, display or print the QR flyer. Participants open the test in a browser without an account, so the only barrier is getting the link to them.

After every test

Look at results the same day if you can, while the test is still fresh for participants. Fix any flawed questions, bookmark weak topics into Revision, and save good questions with tags. Each test you make then improves the next one.

Frequently asked questions

How many questions should a test have? Enough to cover every topic fairly, and no more; ten to fifteen suits most weekly tests. Can participants take it on phones? Yes, in any browser without an account. Can I change a test after sharing it? Yes, but avoid changing answers once people have responded, since earlier and later results would no longer be comparable.

Building your first test today

Pick a topic you taught or trained on this week, generate or write ten questions, and review each one. Build the test with a realistic timer and the right attempt setting, share the link with one group, and read Question Performance once the responses arrive.

That single cycle shows the whole value of online testing: less time preparing and marking, and clearer insight into what people actually learned.