How Testability Supports Your Agility
summary
Claim: teams with a blazingly fast automated test suite become more agile because they can deliver smaller batches more often. Concrete practice shown: refactor a validate-and-transform function to map JSON to a domain entity, extract business logic into pure functions, and push IO into adapters so tests run against ports-and-adapters (hexagonal)/onion architecture. Use test doubles and simple in-memory fakes for adapters to get fast whole‑use‑case tests (author cites ~90% safety); recommends TDD/BDD styles and tools like ArcUnit for enforcing architectural rules.
AI-written summary · about
chapters (6)
- 0:00Start
- 5:05Typical Symptoms
- 8:36How Dare They?
- 14:13Lots of Dependencies
- 23:06Architectural Styles
- 28:12Patterns & Styles for Testability
related talks
42mAgility in Software Engineering - Concepts and Misconceptions
01h 05mMicrotesting
33mAgile Software Testing
42mUse testing to Develop Better Software Faster
58mAppendix A: What We´ve Learned Since Agile Testing
30mMastering Testing in a Hexagonal Architecture
57mAdvanced Testing Techniques: Tips from the trenches
42mIntroducing the benefits of the testing diamond