To refresh the canonical definition

[rakibhasan]

of TDD, you should go back to the basics and review the materials which we can easily find surfing the Internet.

The most straightforward source of knowledge is Wikipedia. It is a mix of all universal knowledge, so it is the right place to start. We can learn there how TDD cycle looks like, what are the benefits of it and a lot more.

However, if we want to understand bulgaria mobile number the process deeply, we should jump to its origins. According to the Wikipedia article, the person credited for the development of TDD is Kent Beck. It seems that his book “Test Driven Development: By Example” is the main and primary source of knowledge about Test-driven development.

Two rules of TDD by Kent Beck
The author of “Test Driven Development: By Example” guides readers through sample problems solving them using the TDD technique.

It might be the best way to learn the process however we would like to have some clear rules which we would call TDD definition. At the very beginning of the book, Kent mentions that the roots of TDD can be described as:

Don’t write a line of new code unless you first have a failing automated test
Eliminate duplication
The first rule seems to be quite obvious. It just says that we shouldn’t start writing application code until we have a single failing automated test. When the test is Green, and we want to continue working on the production code, we should add a new test. Actually, we should do Refactor first but it is the second rule.