1 Mistake Every TDD Detractor Makes
Don’t dismiss TDD before you try Agile-Unit Testing
As someone who has been advocating for Test-Driven Development (TDD) for many years, I have read my fair share of articles and criticisms from those who claim that TDD simply doesn’t work. They argue that TDD is too time-consuming, too complicated, or too prone to errors to be a viable approach to software development. However, after reading through many of these articles, I have come to the conclusion that the detractors all seem to make the same mistake: they focus solely on QA-Unit Testing, rather than the more effective Agile-Unit Testing.
Probably you have never heard about them before, but QA-Unit Testing is the one that you already know.
Before I dive into the details of Agile-Unit Testing, let’s first clarify the difference between these two types of unit testing. QA-Unit Testing is what most people are familiar with. It involves writing test cases for individual units of code, with the goal of ensuring that each unit of code functions as intended. These tests are typically written after the code has already been implemented, and they are focused solely on the code itself. The problem with QA-Unit Testing is that it assumes that the code has already been written correctly. It doesn’t consider how the code is supposed to behave or interact…
