My Roof CRM

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.

Intermediate 8 minTesters & video team, Platform administrator· Last checked 2026-10-03

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.

GuideScriptChecklist

Rough runtime

4:10

Scenes

7

Lesson

11.2 · For testers & video producers

File name

11-02 how-to-test-with-the-guides.mp4

Before you record

  • A staging workspace and a guide checklist open.
  • Record at 1920×1080, browser zoom 100%, light theme, sidebar expanded, no personal data on screen. See Recording standards.

Shot list

#TimeSceneScreenOn screenNarration
00:0020sIntro: How to test the product using the guides/help/[slug]Title card, then the first screen of the lesson.For testers: how to turn the course into a regression suite.
10:2043sPick 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.Every guide is a test plan. Open the checklist tab.
21:0343sPrepare preconditions/help/[slug]Set up the test workspace so every precondition is true (plan, data, verified email). Tick each.Do not start until the preconditions hold; otherwise failures are noise.
31:4643sExecute 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.Follow the words exactly. If the button is labelled differently, that is a finding too; the guide must match the product.
42:2943sProbe pitfalls/help/[slug]Work through "Known pitfalls to probe": trigger each problem deliberately and check the app handles it as described.Then try to break it the known ways. Expired links, missing emails, read-only workspaces.
53:1243sReport/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.Copy the checklist as Markdown into your tracker, fill the result, attach screenshots. Slug plus step number is all a developer needs to find the exact spot.
63:5515sRecap & next lesson/help/[slug]Hold on the finished result, then the end card.Next: the standards every tutorial video follows.

Narration, in order

  1. 0. Intro: How to test the product using the guides

    0:00 · 20s

    Title card, then the first screen of the lesson.

    For testers: how to turn the course into a regression suite.

  2. 1. Pick the lesson and open the checklist

    0:20 · 43s

    Open the guide to test and click "Test checklist". Read "Screens covered" and the last-checked date.

    Every guide is a test plan. Open the checklist tab.

    Show before cutting: Preconditions, numbered steps with Do/Expect, known pitfalls and a Result block.

  3. 2. Prepare preconditions

    1:03 · 43s

    Set up the test workspace so every precondition is true (plan, data, verified email). Tick each.

    Do not start until the preconditions hold; otherwise failures are noise.

    Show before cutting: All preconditions ticked before step 1.

  4. 3. Execute step by step

    1:46 · 43s

    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.

    Follow the words exactly. If the button is labelled differently, that is a finding too; the guide must match the product.

    Show before cutting: A list of ticks and a list of findings.

  5. 4. Probe pitfalls

    2:29 · 43s

    Work through "Known pitfalls to probe": trigger each problem deliberately and check the app handles it as described.

    Then try to break it the known ways. Expired links, missing emails, read-only workspaces.

    Show before cutting: Each pitfall ticked or logged as a finding.

  6. 5. Report

    3:12 · 43s

    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.

    Copy the checklist as Markdown into your tracker, fill the result, attach screenshots. Slug plus step number is all a developer needs to find the exact spot.

    Show before cutting: A report a developer can reproduce from.

  7. 6. Recap & next lesson

    3:55 · 15s

    Hold on the finished result, then the end card.

    Next: the standards every tutorial video follows.

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?