Application testing

Question

Are the actual benefits of TDDactually testing the application, or are the benefits that the test application is writing bring to the table? I ask because I too often feel that the conversation revolves around testing, and not a general package of benefits.

Answer 1

TDD helps you develop software. Tests become a design. After writing the test, you first think about your code from the point of view of the consumer, creating a more convenient and compact software design.

In addition, when using TDD, you usually write your code in such a way that you can supply test mocks and stubs. This leads to less complex software, which makes it easy to change and maintain over time.

So, I think that talking about TDD is related to testing, but when doing this, other great advantages follow, such as quality (coverage), flexibility (decoupling), better design (I think as a consumer of API).

Answer 2

The real improvement is that this is a good way to get you to really think about design and implementation. Then, once you have prepared the tests and written the code, solutions for unforeseen problems look more easy.

-, , : IRC, , , .

Answer 3

, TDD , // , , . , -, , , TDD, , .

TDD, . . .

Answer 4

- , , . , . , - , - .

TDD . TDD- .

Answer 5

Michael Feathers The Flawed Theory Behind Unit Testing. , .

All of these methods have been shown to improve quality. And if we look closely, we can understand why: they all make us think about our code.

but you should read the full post for context.

Answer 6

Automatic testing keeps people from completing a machine task.

The development under test maximizes the volume of automated testing.

In addition to a certain point, of course, a person is still required. You decrease returns when you try to apply TDD to this point.