Timeline for Does TDD's "Obvious Implementation" mean code first, test after?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 5, 2012 at 14:36 | comment | added | ThomasX | It is obviously obvious that any code can only be tested after it is written... | |
| Apr 5, 2012 at 12:24 | answer | added | k3b | timeline score: 1 | |
| Apr 5, 2012 at 11:55 | history | edited | BЈовић | CC BY-SA 3.0 | deleted 17 characters in body |
| Sep 15, 2011 at 16:29 | vote | accept | natasky | ||
| Sep 14, 2011 at 21:26 | answer | added | Chris Lee | timeline score: 1 | |
| Sep 14, 2011 at 20:51 | answer | added | pdr | timeline score: 6 | |
| Sep 14, 2011 at 20:46 | comment | added | Carl Manaster | I agree with your interpretation. Test first and "just implement" when the problem is easy enough to solve without iterations. But definitely test first. | |
| Sep 14, 2011 at 20:45 | answer | added | Oded | timeline score: 11 | |
| Sep 14, 2011 at 20:37 | history | asked | natasky | CC BY-SA 3.0 |