Timeline for Is it sensible to structure unit tests in one class for executing the tests and one for the setup?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 15, 2017 at 12:25 | vote | accept | Paul Kertscher | ||
| Dec 12, 2017 at 5:32 | history | tweeted | twitter.com/StackSoftEng/status/940454408067874819 | ||
| Dec 11, 2017 at 18:23 | comment | added | Greg Burghardt | Do these tests essentially contain the same steps, but the data changes? | |
| Dec 11, 2017 at 15:10 | history | edited | amon | CC BY-SA 3.0 |
added syntax highlighting
|
| Dec 11, 2017 at 9:22 | comment | added | JacquesB | The design is fine, but it is confusing to call the setup helper for a test fixture. | |
| Dec 11, 2017 at 9:09 | answer | added | Robbie Dee | timeline score: 0 | |
| Dec 11, 2017 at 8:30 | answer | added | ivenxu | timeline score: 3 | |
| Dec 11, 2017 at 7:54 | comment | added | Euphoric | I'm doing this myself and also find it very helpful. And often, this kind of facade has different API than the tested one, making tests clearer. | |
| Dec 11, 2017 at 7:41 | history | asked | Paul Kertscher | CC BY-SA 3.0 |