RIP Test Driven Development
Or are we just thinking about it wrong? The core philosophy behind TDD
There is a misconception on what test driven development really is. We all know what it is, but at the same time, we don’t really.
Usually it’s the word ‘test ’ that throws us off. So we end up writing long convoluted test units, sometimes the test code being more than the actual code itself. It’s all fun and games in the first iteration but if something needs to be changed, then massive refactoring of the test units is required before you can do anything in particular. This is often the first sign that TDD has been implemented incorrectly.
By the third round, we developers simply throw our hands up towards testing our code and decide to just go agile instead. We collapse under the weight of the tests that are supposed to save us time and ensure the robustness of our final product.
“RIP TDD” we whisper, then never speak of it again.
But test driven development isn’t that bad, it’s just badly misunderstood.
Crashing into the idea behind TDD
What many of us tend to do when we first encounter test driven programming is that we write tests for every possible method and classes. This often causes an issue down…
