3 ms·
TDD doesn't give you documentation, it gives you tests. Typically automatic unit tests, which is code. Tests serve a different purpose. They are not for humans
by GuB-42 4y ago
TDD doesn't give you documentation, it gives you tests. Typically automatic unit tests, which is code.
Tests serve a different purpose. They are not for humans to read, they are to make sure your software works ("working software"). They are an important component of Agile because it makes it easier to change your code without breaking things.
Now, I am not big into TDD, but for me, it is an approach that is fully compatible with the Agile manifesto.
- randomdata 4y ago> TDD doesn't give you documentation, it gives you tests Test is the action that is carried out from the documentation, possibly by a human, but more likely by a machine. We are talking about the document that describes what the program is intended to do, which is then followed to carry out the tests. > They are not for humans to read I should hope your documentation is there for humans to read. If not, even small modifications required as business needs change would become a complete nightmare. The tests you need to perform, and thereby the documentation that needs to be followed, will not remain static through the entire lifetime of the application.