6 shots · about 1 min 05 s of finished video · lesson 2 of Recording tutorials & testing with the guides
Record as
Any staff login
Sign in at /demo on a demo-mode build
Screens
/help/production /demo /help/[course]/[lesson]
Length
1 min 05 s
narration at ~150 words/min + screen time
Status
Not yet recorded
Before recording
Use the demo school, follow a lesson exactly, and treat every “You should see” line as the pass/fail criterion.
| # | Screen | Action (on screen) | Must be visible | Voice-over | ~s |
|---|---|---|---|---|---|
| 1 | /help/production | Open Help → Recording plan and pick the course you are testing with the course filter. | One row per lesson with the persona to use, the number of shots and the video status. | The recording plan is also the test plan: every lesson is one scenario, and the persona column tells you which login it needs. | 13 |
| 2 | /demo | Go to /demo and sign in as the persona shown for the lesson (Owner, Principal, Accountant, Teacher, Parent or Student). Callout: Re-running pnpm db:seed resets the demo school. Do it before a full pass so earlier tests do not leave data behind. | The dashboard or portal opens for Malda Public School and the top bar shows the demo user with a switch link. | The demo school has data in every module, so each lesson can be run from a fresh seed without inventing records. | 12 |
| 3 | /demo | Open the lesson and perform each step exactly as written, in order. After each one, compare the screen with the You should see line and tick the step only if it matches. | Every step ticked = the scenario passes. | Do not improvise: the value of the test is that it follows the written path. | 10 |
| 4 | /demo | When a step does not match, note the lesson slug (shown under the title in the recording plan), the step number, what the guide says and what the screen actually shows. Take a screenshot. | A bug report that a developer can reproduce in under a minute. | A failed step is either a product bug or a documentation bug; the report should say which you think it is. | 12 |
| 5 | /demo | Also test the If something goes wrong entries: trigger the problem on purpose and confirm the fix works. | Each troubleshooting entry reproduces and resolves as described. | Error paths are part of the product too. | 7 |
| 6 | /demo | Repeat the lesson with a role that is not allowed (the lesson header lists the roles). | The page shows a permission notice instead of the content and the sidebar does not offer the section. | Negative tests are quick with the demo personas: switch user, open the same URL, expect a refusal. | 11 |
After the video is published
Add its YouTube id under video-testing-with-guides in src/lib/help/videos.ts, with a chapters map of step number → seconds. The lesson page then shows the video and a “Watch this step” link on every step. See the video production guide.