Timeline for Documenting Unit Tests
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 23, 2016 at 13:34 | history | edited | dzieciou | CC BY-SA 3.0 |
deleted 2 characters in body
|
| Dec 23, 2016 at 12:34 | history | edited | Bharat Mane♦ | CC BY-SA 3.0 |
improved question
|
| Jun 20, 2011 at 16:19 | answer | added | k3b | timeline score: 2 | |
| Jun 17, 2011 at 13:27 | vote | accept | stuartf | ||
| Jun 14, 2011 at 14:37 | answer | added | Bj Rollison | timeline score: 3 | |
| Jun 14, 2011 at 14:07 | answer | added | user246 | timeline score: 9 | |
| Jun 14, 2011 at 13:07 | comment | added | stuartf | They mostly deal with the internals details of the implementation | |
| Jun 14, 2011 at 13:06 | history | tweeted | twitter.com/#!/StackSQA/status/80622064410701824 | ||
| Jun 14, 2011 at 12:52 | comment | added | user246 | Before I answer, can you clarify something about the extra unit tests? Would the extra unit tests stick to testing the interfaces that are part of the specification, or would they actually communicate with the internals of the implementation? | |
| Jun 14, 2011 at 10:59 | answer | added | ReneS | timeline score: 7 | |
| Jun 14, 2011 at 9:11 | history | asked | stuartf | CC BY-SA 3.0 |