3 ms·
The point is to have tests. What came first the chicken or the egg? Either the test came first and the code after or the code came first and test after. An i
by acd 7y ago
The point is to have tests.
What came first the chicken or the egg?
Either the test came first and the code after or the code came first and test after.
An issue can arise in fast agile test driven development environments if you develop the code first and then do not get time to do the tests. If you start with the test you will be ensured to have time to write code otherwise the software will not work.
"The muscle doesn't see what you're holding in your hands." Arnold Schwarzenegge
- The tests doesnt care how you got them in place
- mytailorisrich 7y agoRequirements come before implementation. In many organisations it often happens that the test team implements tests and is ready to test a feature before the dev team has actually implemented it. IMO, that's the basis for TDD, really. When you start coding you should know what the result should be and thus you should write tests first to capture this and guide implementation.