3 ms·
> A great idea hiding behind a terrible implementation TDD is a method. TDD forces you be clear about what the result of your code should be before you start
by mytailorisrich 7y ago
> A great idea hiding behind a terrible implementation
TDD is a method.
TDD forces you be clear about what the result of your code should be before you start coding. It also ensures that there is a test to check your code. This is certainly not dumb.
You will write tests anyway (right?) so it does seem smarter and more effective to write them first in the same way as you write requirements first before writing code. Nothing prevents you from iterating as progress and discover corner cases, for example.
People who say that TDD moves slower are simply admitting that they don't test. Automated tests are also crucial because 99% of testing is regression testing and that obviously cannot be done manually every time the code changes.
I found it rather ironic that the article ends by praising behaviour-driven development, which is an extension of TDD...
- XCabbage 7y ago> TDD forces you be clear about what the result of your code should be before you start coding ... which is often difficult and inefficient. A large part of the point of the article is that when making changes to an existing system, you often DON'T know until doing some experimentation what the result of your particular new bit of code should be. You know what change you want to happen to the behaviour of the system as a whole, but don't yet understand how the pieces that make up the system slot together. That permits you to dive in and try making changes and see what their effect is, but doesn't permit you to write a unit test right away. > it is smarter and more effective to write them first. But... why? You're asserting this without any justification. > People who say that TDD moves slower are simply admitting that they don't test. This accusation is pretty tedious. The article was explicitly comparing the test-first-code-second approach against the code-first-test-second approach and giving a reasoned argument (which you've not acknowledged or engaged with) for why the second was usually superior. The author isn't saying they don't test or arguing for not testing. > I found it rather ironic that the article ends by praising behaviour-driven development That was sarcasm.
- mytailorisrich 7y agoIf you start coding before knowing what you are implementing then you have a bigger problem than TDD. Experimentation is not the same as implementation, by the way. Obviously nothing is adhered to 100% of the time in real life, this is not a dogma, but the point that you should know what the result of your code should be before you write it and should thus write tests first (which can also help you clarify your understanding) is eminently reasonable and valid. > That was sarcasm. Article is poor overall. Sarcasm does not help.