Building an automated test (before the implementation code) is a challenge, and every passing test should feel like small win.
“Test driven” feels like a chain of focused fun problems to solve, the opposite of “test-after” which can feel like chores to complete.
Discussions for your team
- How often are we doing “test-after” instead of “test-first” development?
- How can we make writing test-first feel more fun?