Maximizing Unit Tests: Embracing Test-Driven Development
summary
Argues for writing the unit test first, using the AAA (arrange act assert) pattern, and treating every PR as needing 100% coverage for the new code so regressions surface early. CI pipelines enforce tests and static analysis with SonarQube, and team productivity improves by catching bugs faster and reducing manual setup. Recommends using GitHub Copilot to scaffold tests, measures coverage per change rather than global targets, and reports that this practice produces more robust releases and faster bug fixes.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker intro
- 1:02About Dan Mella and Arcadis
- 7:26Health and safety moment
- 9:35Test-driven development story
- 13:49Why TDD is underutilized
- 19:56Integrating TDD at Arcadis
- 24:28Overcoming resistance to TDD
- 25:32AAA pattern in unit tests
- 26:54Benefits of reliable test suites
- 28:24AI tools for unit testing
- 29:47AAA pattern recap
- 30:28Q&A and closing remarks
related talks
42mUse testing to Develop Better Software Faster
32mThinking in tests
49mESSENTIALS - Canon Test-Driven Development
20mThe Road to Continuous Testing
42mIntroducing the benefits of the testing diamond
48mEffective Unit Testing
29mHow I Learned to Stop Worrying and Love Unit Testing
44mStrategy for Acing Continuous Testing in DevOps