A work order for testing your exact kind of product: which risks are real, which tests are mandatory, in what order, and what to hand to whoever runs them.

46 product types. Every risk has a source. Every mandatory test has a reason and a done condition.

Pick your product type

46 product types

All types with risk and test counts: how-to-test index. Printable lists: checklists.

What a playbook page contains

  1. 01Direct answer

    What breaks untested, how many tests are mandatory, which to run first.

  2. 02Definition and scope

    What counts as this product type and which adjacent types are separate pages.

  3. 03Risk map

    Each risk with severity, evidence grade, a note for this type and its source.

  4. 04Mandatory tests

    Ordered list; each test names its risks, a done condition, a tool class and who runs it.

  5. 05Recommended and optional

    Tests with the condition that would make them mandatory.

  6. 06Not needed and why

    Tests often added to plans for this type without a risk behind them.

  7. 07Order of work

    First release sequence and ongoing cadence.

  8. 08Tools

    Tool names per test type, alphabetical, filtered to the platforms of the type.

  9. 09What to send

    Checklist download, brief and acceptance criteria wording.

  10. 10FAQ

    Questions people search for, answered from the page data.

  11. 11Evidence

    Every source used on the page, with publish and verification dates.

  12. 12Disclaimer

    What the page is and is not.

How to read evidence grades

primary
Regulator page, store guideline, standard, official post-mortem, court or fine record.
secondary
Engineering incident write-up, conference talk, audited industry report, or a by design analysis backed by a primary general requirement.
practitioner
Named practitioner post or answer. Two are needed to attach a risk.

A risk is attached only with one primary or secondary record, or two practitioner records. A test is mandatory only when it addresses an attached risk. Details are in the methodology, and the reasoning behind each test type is on the test type pages and risk pages.

Outside this site

Who this is for

Founders forwarding a page to a developer or vendor: what to forward and what to ask back. Product managers turning a page into tickets: tickets and acceptance criteria. Tool names by test type: tools.