15 years of insights from a TDD practitioner
summary
15 years of TDD experience yields a pragmatic claim: test slightly bigger slices, not every tiny class, to avoid brittle tests and constant rewrites. Examples include a real Azure Function that propagates collective agreements to subsidiaries, using .NET/C#, HTTP mocking for backend calls, test data builders and Fluent Assertions to compare payloads, JetBrains Rider and Nuke for local runs, testcontainers for DBs, and a rule-of-three refactor workflow that reduced a 25,000-test maintenance nightmare. Key practices: test data builders, characterization tests, and CI-enforced non-flakiness.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:22Pragmatic approach to test-driven development
- 10:05Unit testing myths
- 17:55TDD example with functional tests
- 29:13Refactoring tests
- 35:33Coverage pitfalls
- 42:35Fixture classes and mocking
- 47:26CI/CD flaky tests
- 50:36Legacy code testing
- 53:05Conclusion
