Timeline for How to avoid the need to Unit test private methods
Current License: CC BY-SA 4.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 1, 2018 at 12:10 | vote | accept | Fran Sevillano | ||
| Jul 30, 2018 at 12:05 | comment | added | GordonM | A thorough unit test should implicitly cover all private members of a given class, because while you can't call them directly, their behaviour will still have an effect on the output. If they don't then why are they there in the first place? Remember in unit testing what you care about is the result, not how the result was arrived at. | |
| Jul 30, 2018 at 9:41 | answer | added | Bernhard Hiller | timeline score: 0 | |
| Jul 30, 2018 at 3:01 | history | tweeted | twitter.com/StackSoftEng/status/1023765576123068416 | ||
| Jul 28, 2018 at 23:33 | answer | added | gnasher729 | timeline score: 4 | |
| Jul 28, 2018 at 20:40 | answer | added | bikeman868 | timeline score: 1 | |
| Jul 25, 2018 at 19:53 | answer | added | Timothy Truckle | timeline score: 5 | |
| S Jul 25, 2018 at 19:43 | history | suggested | Martin Spamer | CC BY-SA 4.0 |
Improve question summary to better reflect the question details
|
| Jul 25, 2018 at 17:15 | review | Suggested edits | |||
| S Jul 25, 2018 at 19:43 | |||||
| Jul 25, 2018 at 14:59 | answer | added | Thomas Owens♦ | timeline score: 29 | |
| Jul 25, 2018 at 14:55 | review | Close votes | |||
| Jul 30, 2018 at 3:05 | |||||
| Jul 25, 2018 at 14:35 | answer | added | Lewis Pringle | timeline score: 4 | |
| Jul 25, 2018 at 14:15 | answer | added | Ewan | timeline score: 0 | |
| Jul 25, 2018 at 14:10 | history | asked | Fran Sevillano | CC BY-SA 4.0 |