3 ms·
Yes a lot of people kept parroting TDD (as most people parrot the latest fad without thinking for 3 seconds if they should actually do that) > I absolutely thi
by raverbashing 9y ago
Yes a lot of people kept parroting TDD (as most people parrot the latest fad without thinking for 3 seconds if they should actually do that)
> I absolutely think _tests_ are useful, but have never found any advantages to test-DRIVEN-development (test-first).
Seconded. Especially the crap about "make the test fail first" (making the test fail is useful, especially if you're unfamiliar with some aspect of it), but it should not be an obligation
- rsyntax 9y agoYeah I dislike that mantra, but I think it was a guideline for novice. I think the phrase should be updated to "make the test fallible".
- UK-AL 9y agoThe term making the test fail, isn't about explicitly making the test fail. It's about the fact that it's not implemented yet, so of course it going to fail!
- ehsanu1 9y ago> Especially the crap about "make the test fail first" (making the test fail is useful, especially if you're unfamiliar with some aspect of it), but it should not be an obligation Sometimes I write code to fix a bug, then a test the tests my bugfix. Test passes. I'm done right? Well, I make sure my test fails without the bugfix. About half the time, the test still passes. ie I wasn't testing what I thought I was testing. That's why you make the test fail.
- raverbashing 9y agoYes, that's why I say "making the test fail is useful" ;) And yes, I've seen this happen as well, either you're not testing the bug-causing issue or you're using a "Magical Mock Library" where x.does_thing() just returns true and you thought it did the thing but it didn't.