Arrange Act Assert

Step 1: Define one observable behavior

1. IDENTIFY the public seam, precondition, one focal behavior, and observable outcome before editing the test.
2. NAME the test as behavior + condition + expected result in repository vocabulary; avoid names that restate a method or say only “works.”
3. CONFIRM the test layer and real contract are already chosen. ROUTE test-first red/green sequencing to tdd, seam/module design to codebase-design, and framework-specific setup to its development skill.
4. USE Arrange-Act-Assert for an example-based scenario with a focal action. If the test is naturally property-based, model-based/state-machine, benchmark, fuzz, approval/snapshot, or long Given-When-Then workflow, preserve that framework’s clearer native structure.
5. READ references/phase-rules.md before deciding whether a call belongs to Arrange, Act, or Assert.

Completion: a reader can state “Given [precondition], when [behavior], then [outcome]” without reading implementation details.

Step 2: Inspect candidate tests

RUN from the repository root:

python3 scripts/inspect-tests.py --root . --json