Stream tests
A stream holds a scheduled series of assessments. Each one is an ordinary assessment from your account, given a window, a weight and optionally its own pass mark.
Adding a test
Pick an existing assessment and set:
| Setting | Effect |
|---|---|
| Start and end date | The window students may sit it in |
| Display order | The order students see the series in |
| Weight | How much it counts toward the overall score (default 1.0) |
| Pass threshold | An optional pass mark for this test specifically |
| Reminder overrides | Per-test reminder days, replacing the stream defaults |
Because these are ordinary assessments, everything in Creating assessments applies — question types, per-question time limits, proctoring, shuffling.
Windows
The window is what makes a stream a programme rather than a pile of links. Students get access when it opens and lose it when it closes; the stream's timezone decides what "Friday" means for everyone.
Windows can overlap. A long project assessment running for two weeks alongside weekly short ones is a normal shape, and display order rather than dates is what tells students where they are in the series.
Leave enough room for a resit if your policy allows one. A window that closes the hour a deadline passes gives you nowhere to put a student whose connection died.
Weights
Weight is relative, not a percentage. Three tests weighted 1, 1 and 2 mean the third counts for half the total; the same result comes from 0.5, 0.5 and 1.
Use weights to say what the programme is actually about. Equal weights across a warm-up quiz and a final project tell students both matter equally, and they will allocate their time accordingly.
Pass thresholds
A per-test threshold marks that test passed or failed for each student. The stream's own overall pass threshold applies to the weighted total.
These are labels for your team, not gates: a student below a threshold is not blocked from later tests, and nothing removes them from the cohort. Deciding what a failure means is yours — see Stream results.
Reminders
Two reminders per test, by default 5 days and 1 day before the deadline, inherited from the stream and overridable per test.
Set the overrides where the shape differs. A two-week project wants an early nudge; a one-hour quiz released on the day does not need a five-day warning it will never send.
How students receive tests
Each student gets their own invitation per test, with its own link and expiry, tracked from sent through opened, started and completed.
You do not send these by hand. Enrolment plus the schedule is what produces them, which is the labour Streams exists to remove — one cohort of 200 across six tests is 1,200 invitations nobody has to manage.
Changing the schedule mid-stream
Editing a window or weight after students have started affects everyone still to sit that test, and changes the weighted total for those who already have.
Moving a deadline outward is usually safe and kind. Changing a weight after results exist is not — it silently re-ranks the cohort, and students who allocated their effort based on the published weights were told something that is no longer true. If you must, tell the cohort you did.