Evolutionary Testing Strategy
summary
Claim: testing strategy must evolve alongside architecture or it creates costly tech debt; concrete moves include fitness functions (unit, contract, architecture, chaos and performance tests) wired into CI/CD, keeping test suites version-controlled, and recording testing impact in ADR/BDR impact records. Examples: 30–40 year legacy codebases and rapid shifts from web UI to API or event streams break e2e coverage; industry data shows ~50% of organisations have developers spending only 30–40% time on new features, proving the financial hit.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:38Evolutionary architectures principles
- 10:04Stagnant testing consequences
- 11:32Testing strategy failures examples
- 26:25Financial impact of poor testing
- 28:55Evolutionary testing strategy
- 29:55Version control for tests
- 31:44Documenting changes
- 33:10Accountability for testing
- 35:16Testing contingency planning
- 36:42Communicating testing strategy
- 37:47Closing remarks & Q&A
related talks
55mQuality Engineering Evolution: What Lies Ahead in
58mTesting Strategy - New Model, Better Outcomes
43mTesting Software Architectures
46mEvolution & Future of Software Testing
47mHow Testing is Evolving in DevOps
40mTesting Software Architecture
22mTest Effective Development
42mIntroducing the benefits of the testing diamond