Timeline for Is unit testing or test-driven development worthwhile?
Current License: CC BY-SA 3.0
2 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 17, 2012 at 9:50 | comment | added | S.Robins | For my 2c: In order to to know if your tests are actually working, you need to see them fail before you see them pass. I've sadly witnessed many developers write tests that seemed to be working, yet when the test conditions were changed, the code would still pass the test, even though it should have failed. If the test fails first and passes second, then it is more likely that you've written a test without error. If you end up modifying the test after the code has changed, then you can't be certain the code is sound. Yes it's tedious, but it's got a better chance of being correct. :-) | |
| Mar 17, 2012 at 9:31 | history | answered | tylerl | CC BY-SA 3.0 |