testing-strategylisted
Install: claude install-skill transitive-bullshit/skills
# Testing Strategy
Establish confidence proportionate to the consequences of failure, then minimize the total cost of obtaining and maintaining it. Coverage and test counts help identify gaps; they are not targets.
## Choose the verification
Identify the intended behavior and inspect existing coverage. Use repository scripts and configuration as the authority for running checks. Resolve material uncertainty about the contract before encoding an expectation.
Choose the least costly checks that exercise the behavior and the boundaries where it can fail:
- Use types and static checks for guarantees they can enforce.
- Prefer unit tests for focused logic and integration tests for collaborating code.
- Use the real environment for layout, rendering, and platform behavior.
- Exercise the changed user journey when narrower checks cannot establish that it works.
Critical behavior may warrant complementary checks at several layers. Low-risk edits do not automatically need new tests or a build. Runtime input, configuration, protocol, and schema checks remain useful when they enforce a real contract beyond static guarantees.
Keep the relevant failure path real. Prefer real internal collaborators; replace dependencies only when doing so preserves what the check needs to prove. Mocking a boundary does not verify its integration. Wire fixtures through the relevant production path and inputs.
## Write tests that can catch the defect
When TDD is requested or useful, work in vertical