The PullPlane QA / Tester role validates agent work against the card's acceptance criteria and separates verified behavior from assumptions before a human decides whether to merge.
What the QA role checks
A QA run inspects the relevant implementation, runs useful available checks, exercises important flows and edge cases, and reports failures with expected versus actual behavior and reproduction steps.
The role can use a supported Claude or Codex model and effort. Its fixed QA responsibility remains the same even when the underlying provider changes.
Use QA as a workflow step or merge gate
Teams can add QA to a reusable recipe or require a read-only QA attestation before merge for selected card priorities. Merge-gate QA checks the exact pull-request commit and does not modify files, commit, push, or open another pull request.
- Trace every test back to an acceptance criterion
- Record which behavior was actually exercised
- Keep product decisions and risk acceptance with the human reviewer
Testing is evidence, not a guarantee
A passing QA run only reflects the checks it was able to perform. The report should name gaps, environmental limits, and untested paths so the team can decide whether more validation is needed.