Test a lesson against the app
Use a lesson's Test checklist to confirm every step still matches the app, and report what does not.
The written steps below are complete. The Video script tab shows exactly what the video will cover.
The app changes, and a lesson is only useful while it matches. Every lesson has a Test checklist made from its own steps, so testing a lesson means doing it exactly as written and ticking what you saw.
By the end you can
- Run a lesson's checklist
- Tell a wording difference from a real fault
- Report a lesson that needs updating
Screens used
Before you start
- A test login for the role shown at the top of the lesson, with made-up data only.
Steps
- 1
Open the lesson's checklist
On: /docs/courseOpen the lesson and choose the Test checklist tab. Each row is one step and what you should see after it.
You should see: A list of rows with tick boxes.
- 2
Do each step as written
On: The appIn a second window do step 1 exactly as the Guide tab says. Do not use your own shortcuts: the point is to check the written route.
You should see: The result on screen matches the row's "You should see" text.
- 3
Tick or note
On: /docs/courseTick the row if it matched. If a button has a different name, a screen moved or the result was different, leave it unticked and write down the step number and what you saw instead.
You should see: Every row is either ticked or has a note.
- 4
Try the problem cases
On: The appRows that begin "Problem case" come from the lesson's Troubleshooting. Cause each one on purpose where it is safe, and check the fix works.
You should see: The fix in the row solves the problem.
- 5
Report the result
On: Your team chatSend the lesson's address and your notes to whoever maintains the course. A lesson with all rows ticked is ready to record.
You should see: The maintainer knows which steps need rewriting.
Tips
- Ticks are kept in your own browser only. They are a working aid, not a record.
- The date under the lesson title, "Last checked", is updated when a lesson is re-tested and corrected.
Troubleshooting
- The screen does not match a step.
- That is a finding, not a mistake of yours. Note the step number and what you saw, and report it. Do not record a video for this lesson until it is corrected.
- Your ticks have gone.
- Ticks are kept in your own browser. A different browser, a private window or cleared browsing data starts empty.
One row per shot, in the same order as the guide. Estimated length 2:11. Use made-up data only. How to record
Say: Test a lesson against the app. Use a lesson's Test checklist to confirm every step still matches the app, and report what does not.
Hold until you see: Lesson title on screen for three seconds.
Say: Open the lesson and choose the Test checklist tab. Each row is one step and what you should see after it.
Hold until you see: A list of rows with tick boxes.
Say: In a second window do step 1 exactly as the Guide tab says. Do not use your own shortcuts: the point is to check the written route.
Hold until you see: The result on screen matches the row's "You should see" text.
Say: Tick the row if it matched. If a button has a different name, a screen moved or the result was different, leave it unticked and write down the step number and what you saw instead.
Hold until you see: Every row is either ticked or has a note.
Say: Rows that begin "Problem case" come from the lesson's Troubleshooting. Cause each one on purpose where it is safe, and check the fix works.
Hold until you see: The fix in the row solves the problem.
Say: Send the lesson's address and your notes to whoever maintains the course. A lesson with all rows ticked is ready to record.
Hold until you see: The maintainer knows which steps need rewriting.
Say: That is test a lesson against the app. The written steps are on this lesson's page in the ItzSEO course.
Hold until you see: End card with the lesson link.
Mark it complete to keep your place in the course.