Test cases & runs
Test cases are what you check. Runs are a pass through those test cases with live status.
Test cases
Each test case has:
- Title: short name
- Steps: what to do (numbered steps work well)
- Expected: what should be true afterward
- Tags: optional filters (e.g.
smoke,auth) - Suite: optional group
- Priority: 1 high … 3 low
Filter the list by suite, tag, or search when it gets long.
Suites
Suites group related test cases for browsing and focused runs. Create them from the suites sidebar on the Test cases page, then assign a suite when you create or edit a test case.
People
Project owners can invite teammates by email from People. Existing accounts join immediately; others get an invite and join after signing up with that email.
Runs
Start a run from all test cases, or only those matching a suite or tag. Optionally set an environment (staging, prod, …). Every included test case begins as untested. As you work, mark:
passfailblockeduntested
Open a test case from the run to record evidence: failed step, what you observed, notes, and evidence URLs. Agents can send the same fields via MCP.
Open the run to see progress and a summary you can share.