Timeline for Test Internals with TDD?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 16, 2018 at 10:54 | history | tweeted | twitter.com/StackSoftEng/status/974599697066283008 | ||
| Mar 14, 2018 at 3:01 | review | First posts | |||
| Mar 14, 2018 at 12:40 | |||||
| Mar 10, 2018 at 22:12 | vote | accept | Adam Thompson | ||
| Mar 8, 2018 at 8:49 | answer | added | Ant P | timeline score: 6 | |
| Mar 8, 2018 at 7:18 | answer | added | Kilian Foth | timeline score: 3 | |
| Mar 8, 2018 at 5:14 | comment | added | Fabio | You can always create some factory/builder classes which create setup for every test case in readable and maintainable way | |
| Mar 8, 2018 at 5:12 | comment | added | Fabio | Having large/complex tests is ok, but by covering with tests as much as possible you will get benefits of refactoring and changing code design for free. | |
| Mar 8, 2018 at 4:39 | review | Close votes | |||
| Mar 16, 2018 at 3:02 | |||||
| Mar 8, 2018 at 4:24 | comment | added | Robert Harvey | Possible duplicate of How do you unit test private methods? | |
| Mar 8, 2018 at 3:57 | history | edited | Adam Thompson | CC BY-SA 3.0 | added 214 characters in body |
| Mar 8, 2018 at 3:49 | history | asked | Adam Thompson | CC BY-SA 3.0 |