3 ms·
TDD is an interesting concept. Anything you write as an engineer has to be tested. Manual testing is way slower than automated testing. I find that when I hav
by aussieguy1234 7y ago
TDD is an interesting concept.
Anything you write as an engineer has to be tested. Manual testing is way slower than automated testing.
I find that when I have a few good automated tests in place, especially in browser selenium tests, I save literally days of work of manual testing. Thats time that I can use to build more features, get more feedback on my product or do other more productive things than manual testing.
10 minutes of time writing a good test saves me days of work in the future testing new changes. Writing good tests is a high impact, time saving investment.
- goatinaboat 7y agoManual testing is way slower than automated testing. It’s entirely a matter of perspective. I consider writing a unit test to do something the compiler could check for you if you were using a statically-typed language to be “manual testing”.
- AstralStorm 7y agoManual testing is where you click buttons on a device and observe results. Even that can be automated most of the time. Pointless unit testing is a separate thing.
- jacques_chester 7y agoI feel this is an unintentional false dichotomy caused by the name "test-driven". An alternative might be automatic-verification-driven or something like it. Basically I want the computer to automatically point out errors, and I want to prove that it will do so by prompting that error detection first. Whether that's by types or test cases is secondary. Personally I prefer types to test cases for many purposes (a good type system sweeps away a lot of toil in my experience), but I will use whatever tools a given ecosystem gives me in the mix that makes sense for that ecosystem.
- fauigerzigerk 7y agoAbsolutely, but testing is not what the author is opposed to. He's arguing against writing tests before writing the code that gets tested.