Timeline for What are the design principles that promote testable code? (designing testable code vs driving design through tests)
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 10, 2017 at 21:33 | history | tweeted | twitter.com/StackSoftEng/status/862420326646505476 | ||
| Mar 18, 2017 at 5:18 | history | protected | gnat | ||
| Jun 21, 2012 at 11:30 | vote | accept | CKing | ||
| Jun 21, 2012 at 11:30 | vote | accept | CKing | ||
| Jun 21, 2012 at 11:30 | |||||
| Jun 19, 2012 at 23:51 | comment | added | Chris Pitman | This is one of my interview questions ("How do you design code to be easily unit tested?"). It single-handidly shows me if they understand unit testing, mocking/stubbing, OOD, and potentially TDD. Sadly, the answers usually are something like "Make a test database". | |
| Jun 19, 2012 at 16:41 | answer | added | barjak | timeline score: 6 | |
| Jun 19, 2012 at 16:32 | history | edited | gnat | edited tags | |
| Jun 19, 2012 at 15:53 | answer | added | KeithS | timeline score: 63 | |
| Jun 19, 2012 at 14:47 | answer | added | bwalk2895 | timeline score: 3 | |
| Jun 19, 2012 at 11:55 | history | migrated | from stackoverflow.com (revisions) | ||
| Jun 19, 2012 at 7:22 | answer | added | k.m | timeline score: 16 | |
| Jun 19, 2012 at 7:13 | answer | added | Morten | timeline score: 8 | |
| Jun 19, 2012 at 6:27 | comment | added | bot | Thank you. I only just started reading the article and it already makes sense. | |
| Jun 19, 2012 at 6:10 | comment | added | S2S2 | Look at this: googletesting.blogspot.in/2008/08/… | |
| Jun 19, 2012 at 6:05 | history | asked | CKing | CC BY-SA 3.0 |