Timeline for Sporadic unittests or TDD?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 15, 2012 at 9:14 | comment | added | dbalakirev | For me it is hard (as i said i might not be pragmattic enough) because there is no supporting force or urge. I like to be forced (or encouraged) to write good code. Also to your question, it less likely that my future change would break a business functionality as my tests will fail. It requires some time to alter the tests every now and then. But in my experience still less than when you have to figure out what a variable value was after a production error. | |
| Aug 15, 2012 at 9:11 | history | edited | dbalakirev | CC BY-SA 3.0 | deleted 82 characters in body |
| Aug 13, 2012 at 20:27 | comment | added | Gere | OK, but now as you have experience with TDD, can you just do the nice coding and merely imaging you'd unit test? Just pretend you're testing and code such that it would theoretically be testable?! | |
| Aug 13, 2012 at 15:49 | history | answered | dbalakirev | CC BY-SA 3.0 |