Integration & Boundaries Defects
Defects at system boundaries that are invisible to unit tests and often survive until production. Contract testing and deliberate boundary design are the primary defenses.
less than a minute
Defects at system boundaries are invisible to unit tests and often survive until production. Contract testing and deliberate boundary design are the primary defenses.
| Issue | Earliest Detection (Automation) | Automated Detection | Earlier Detection with AI | Systemic Prevention |
|---|---|---|---|---|
| Interface mismatches | CI | Consumer-driven contract tests, API schema validators | Predict which consumers break from API changes based on usage patterns | Mandatory contract tests per boundary; API-first with generated clients |
| Wrong assumptions about upstream/downstream | Design | Chaos engineering platforms, synthetic transactions, fault injection | ▲ Review code and docs to identify undocumented behavioral assumptions | Document behavioral contracts; defensive coding at boundaries |
| Race conditions | Pre-commit | Thread sanitizers, race detectors, formal verification tools, fuzz testing | Flag concurrency anti-patterns but cannot replace formal detection tools | Idempotent design; queues over shared mutable state |
Related Content
- Defect Sources - full catalog overview and how to use it
- Testing - testing types and best practices
- Contract Tests - verify that your test doubles still match reality