For founders: what to forward and what to ask back

You do not need to run the tests yourself. You need to send the right page, ask for the right proof, and refuse work that has no risk behind it.

What to forward

  1. Find your product type on the how-to-test index. If two types fit, forward both pages and say which flows belong to which.
  2. Send the page link with the "Copy link to forward" button at the top of the page. The page is the work order: each mandatory test names its risk, its order and its done condition.
  3. Attach the PDF from the checklist page for the same type. The PDF has the same items in the same order as section 4 of the page.
  4. Paste the brief from section 9 into the email or ticket. It already says what to report back.

What to ask back

For every mandatory test, ask for three things: pass or fail against the done condition as written, the build or version tested, and the proof (a screenshot, a log line, a report file). A reply that says "tested" without a done condition is not an answer.

Ask which tool class was used for each test. The tools page lists names by test type in alphabetical order; it does not rank them, so the choice of tool is the tester's.

How to push back on a padded plan

Section 6 of each playbook lists tests that plans often include for that product type without a risk behind them, with the reason and what would change it. If a quote includes one of those, ask which risk it addresses. If the answer names a risk that is not in the page's risk map, ask for the evidence; the methodology explains what counts.

Section 5 lists recommended tests with the condition that makes each one mandatory. If the condition is not true for your product yet, the test can wait.

How to read the grades

Each risk on a page has an evidence grade. Primary means a regulator, a store, a standard or the affected company said it. Practitioner means named practitioners reported it, and two are needed. The risk pages list every source; the glossary defines the terms on the page.

Turning a page into tickets is covered in the product manager guide.