advocacy-testing-strategy

Spec-first test generation for advocacy software starts by encoding intent as tests before implementation. You define a clear specification, generate failing tests from it, and iteratively implement code until all tests pass. This minimizes silent failures in sensitive data workflows.

Common testing anti-patterns to avoid include snapshot traps and mock-everything approaches. This skill automatically detects and prevents these mistakes, ensuring assertion quality review catches issues that could otherwise lead to lost evidence or exposed activists.

Silent test failures occur when assertions lack the quality to catch defective code changes. Mutation testing prevents them by injecting mutants into your logic and enforcing assertion quality checks, verifying that failures are meaningful and robust before deployment.

Use mutation testing when standard spec-first tests pass but you need to verify failure robustness against code mutants. It enforces anti-pattern avoidance and assertion quality checks, ensuring your tests genuinely catch defects rather than passing silently through flawed logic.