How to test the product using the guides
Turn any lesson into a test run: prepare the preconditions, follow the steps exactly, tick expected results, probe the known pitfalls and report findings in a consistent format.
Video tutorial coming soon
The written steps below are complete. Producing the video? Use the video script tab — it follows these steps one for one.
Each step in a guide has an action and an expected result. That is a test case. The Test checklist tab lists them with checkboxes, plus the preconditions and the known pitfalls from the troubleshooting section. A finding is any step where the screen did not match the expected text.
Guides state when they were last checked against the product. If the product changed and the guide is stale, that is also a finding: report it so the guide is updated.
By the end you can
- Run a lesson as a test
- Write a finding that a developer can act on
- Know when a guide, not the product, is wrong
Screens used
/help/[slug]
Step by step
Pick the lesson and open the checklist
/help/[slug]Open the guide to test and click "Test checklist". Read "Screens covered" and the last-checked date.
You should see: Preconditions, numbered steps with Do/Expect, known pitfalls and a Result block.
Prepare preconditions
/help/[slug]Set up the test workspace so every precondition is true (plan, data, verified email). Tick each.
You should see: All preconditions ticked before step 1.
Execute step by step
/help/[slug]Perform each Do exactly as written, with the exact labels. Compare the screen with Expect. Tick only on an exact match. Note anything else with the step number, what you saw, browser and device.
You should see: A list of ticks and a list of findings.
Probe pitfalls
/help/[slug]Work through "Known pitfalls to probe": trigger each problem deliberately and check the app handles it as described.
You should see: Each pitfall ticked or logged as a finding.
Report
/help/[slug]Fill the Result block (tester, date, build, browser, notes). Report findings as: guide slug, step number, expected, actual, screenshot, environment. Use "Copy checklist as Markdown" to paste into your tracker.
You should see: A report a developer can reproduce from.
Tips
- Test on a phone-sized window for the Board, Capture and Calendar lessons; they have mobile-specific behaviour.
Related lessons
How to use this help center
Search, browse by module or role, follow the course in order, mark lessons complete, print a guide, and switch between the Guide, Video script and Test checklist tabs.
For testers & video producersBeginner4 min
Recording standards for tutorial videos
Resolution, browser setup, demo data, narration style, pacing, chapters, thumbnails and the file naming every My Roof CRM tutorial follows so the series feels like one course.
For testers & video producersIntermediate8 min
Finished this lesson?