Test-driven Projects
Peter Bittner
- Developer (of people, companies, code)
- past: Capgemini, HolidayCheck, DACHCOM
- @peterbittner, django@bittner.it
Agenda
- Traditional Approach
- Test-driven Approach
- Advantages & Potentials
- Implementation
Traditional Approach
(Agency)
A Closing Test Phase
- Long acceptance test phase in the end
- A lot of manual testing
- Regression after bug fixes
- No guarantee of stable implementation
- Risky defects liability period
Test-driven Approach
(Agency)
Upfront Specification
- Acceptance test specification in concept phase
- Tests implemented by programmers
- Tests executed automatically
- Extremely short handover in the end
- Regression under control
Advantages & Potentials
Why it makes sense
Make The Same Things Earlier
- No additional budget required
- Product stability
- Waste less money for bug fixing
- Cheap repeatability of testing
- Focus on advanced quality topics
Implementation
It's all about acceptance criteria
What Do We Need?
- User stories
- Test specifications
Learning Resources
Testing. Take Back Control
