TDD and Clean Architecture – Driven by Behaviour

TDD and Clean Architecture – Driven by Behaviour

YouTube recording: https://lnkd.in/eNBYHwdD


1. Why are we here – TDD is painful, but is there another way?
2. The Deeper Why – Don’t ship code, solve business needs
3. Executable Specifications – Do tests codify requirement specs or impl. specs?
4. What’s a Unit Test? – Are we testing module behaviour or class structure?
5. Testing Behaviour – Tests should be coupled to behaviour, not to structure
6. TDD vs TLD – How do we drive development through executable requirements?
7. TDD & Clean Architecture – Driving architecture through system behaviour

Thanks Software Crafts Romandie Community & Java User Group Switzerland! Slides have been posted on JUG CH website https://lnkd.in/eeXCwfJy

To go deeper into these topics, I recommend the classical book “Test Driven Development: By Example” (Kent Beck) https://lnkd.in/dgW_ESSp and also “Clean Architecture” (Uncle Bob) https://lnkd.in/eGgSMgm3