Timeline for How to do Test Driven Development
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 16, 2015 at 14:51 | comment | added | Andres F. | You could also look into doing automated unit/integration testing without doing TDD. The two are often confused, but they are not the same thing. | |
| Nov 26, 2014 at 15:28 | audit | Suggested edits | |||
| Nov 27, 2014 at 12:55 | |||||
| Nov 20, 2014 at 11:00 | vote | accept | Yogesh | ||
| Nov 17, 2014 at 10:26 | answer | added | Jörg W Mittag | timeline score: 22 | |
| Nov 16, 2014 at 21:47 | answer | added | Paul | timeline score: 4 | |
| Nov 16, 2014 at 17:56 | history | tweeted | twitter.com/#!/StackProgrammer/status/534042292424691712 | ||
| Nov 16, 2014 at 15:41 | answer | added | Doc Brown | timeline score: 5 | |
| Nov 16, 2014 at 14:55 | answer | added | miraculixx | timeline score: 4 | |
| Nov 16, 2014 at 13:29 | comment | added | Giorgio | "I am identifying components and just writing test for them before I actually write components.": I find this correct: you first identify the coarse architecture of your system and then start coding. During coding (TDD) you work out the details of the individual components and possibly discover problems with your architecture that you can fix along the way. But I find it OK that you do not start coding without any prior analysis. | |
| Nov 16, 2014 at 13:03 | review | First posts | |||
| Nov 16, 2014 at 21:00 | |||||
| Nov 16, 2014 at 13:03 | history | asked | Yogesh | CC BY-SA 3.0 |