Passing tests can still conceal serious risk: a feature may satisfy its happy path while failing under adversarial input, production load, or an integrating build system. section 1.6
Treat verification as several deliberate attempts to break the implementation:
- Use property tests to probe invariants beyond expected examples. section 1.6
- Use performance tests to validate service-level objectives and expose production-scale resource failures. section 1.6
- Use mutation tests to prove that the test suite can detect meaningful defects. section 1.6
- Derive security tests from a threat model rather than checking only whether the feature works. section 1.6
The missing attacker
Enrichlead had tests, but none were written by someone imagining an attacker; vulnerabilities therefore remained invisible during ordinary feature review. section 1.6
