one of the most significant benefits

[rakibhasan]

of TDD is that we are allowed to work in really small steps. By “step” we mean the size of the code which we need to add to complete one Red, Green, Refactor cycle round.

Here comes the next misunderstanding which we have faced. How big should be such a step?

Some people claim that smaller bulgaria mobile number steps are better, others prefer to do a bigger one, but in fact, both ways seem to be correct. What to choose? It depends on your experience and understanding of the problem you are working on.

Thanks to TDD we can start with a big step that covers a significant part of the problem (even application level test), but in case of any difficulties, we can easily switch to smaller steps.

The important thing is that thanks to TDD you can work in tiny steps. The step’s size should be flexible and should depend on your preferences.

Thanks to all of these benefits, TDD gives us an easy and smooth way to create better design and the excellent interface of our module/class. Of course, it is not guaranteed by TDD (everything can be done wrong), but for sure it helps to achieve this goal.

The Three Laws of TDD by Uncle Bob
After the lecture of Kent’s book, we should have good knowledge of TDD. We can get good intuition going through examples from the book, but still, we can have doubts.

Looking for a more detailed description, we found Uncle Bob’s “The Three Laws of TDD ” article. It introduces three short but stringent rules on how to do TDD right: