Manual tests

Before a ticket is merged, a person tests it by hand. The run writes the script, qa-notes.md, one step per acceptance criterion that a command cannot check; you answer it as a checklist in Pitwall. A run whose script has no steps goes straight to its merge.

Where to find it

• On the ticket: Open checklist, on the Manual tests card
• In the inbox: a Test item
• Manual tests, in the sidebar: every ticket waiting to be tested

The checklist shows the script as the ticket’s branch has it now, the commit under test, and where the project is tested: a line or a link set on the project’s page, shown on every checklist.

Answering a step

Result	Key	Note
Passed	P	Optional
Failed	F	Required
Not clear	N	Required
Observation	O	Required

J and K move between steps. Choosing the same result again clears it. Each answer is saved as you give it, on any device.

Paste or drop a screenshot (⌘V), or take a photo on a phone: it attaches to the step. A finding is something you noticed that is no step; it gets its own screenshots.

A failure

Each failed step has a route:

Route	Does
Send back to this ticket	The run goes back to implement, then forward again to a new round
File a linked bug	Sends nothing back. Once you submit, a bug is ready to file, with the step’s screenshots

A finding is a proposal by default: once recorded, it comes back as a ticket you can file or dismiss. Fix on this ticket sends it back instead, as a new criterion.

Submitting

Submit review (⌘↵) once every step has an answer. test-results then:

• writes the round to test-results.md in the ticket’s directory, in English whatever language you wrote in; your words stay as written in Pitwall;
• reads your screenshots, to understand your notes;
• answers each step you found not clear, and each finding with a proposal;
• may ask you, when a note contradicts a criterion, whether to change the criterion or keep it.

A defect a screenshot shows that you did not mention comes back as a finding marked Found by agent. It sends nothing back; only you file or dismiss it.

Round 2 and after

When something was sent back, the run goes through implement again and a new round opens, with what passed kept: you test only what changed. There is no limit on rounds but the run’s token budget.

When nothing was sent back, the run waits for its pull request to be merged (Pull requests and merging). Merging stays disabled until the round is submitted.

A milestone’s tests

A milestone is tested once, after its last phase: one checklist with a step per numbered step of every phase’s block in manual-tests.md, named Phase N, step M. Two things differ from a ticket’s:

• Waived is a fifth result, with a required note: the step was not run and you accept the risk. A waived step is never asked again.
• A failed step sends nothing to implement: test-results writes one phase of fixes at the end of the milestone, which runs through the agents before the next round asks the step again. After three rounds that send something to fix, the run stops and waits for you.