Timeline for How to avoid logical mistakes in code, when TDD didn't help?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 16, 2018 at 12:21 | comment | added | Toby Speight | Another observation: adding the test for this case will improve the design, by forcing us to take that datetime.utcnow() out of the function, and instead to pass now as a (reproducible) argument instead. | |
| Jul 13, 2018 at 20:09 | comment | added | Mindwin Remember Monica | TDD is only as good as the tests written. | |
| Jul 13, 2018 at 6:29 | comment | added | Caleb | And, on top of that, think about how much time was saved when they we're fixing the bug? By having the existing tests in place, they knew instantly that their change didn't break existing behavior. And they were free to add the new test cases and refactor without having to run extensive manual tests afterward. | |
| Jul 13, 2018 at 6:27 | comment | added | Caleb | Anything point could be made that if the developer hadn't used tdd, they would have been much more likely to miss other cases as well. | |
| Jul 12, 2018 at 21:54 | history | answered | esoterik | CC BY-SA 4.0 |