Timeline for Value of using private methods vs all public in classes for internal software for ease of unit testing
Current License: CC BY-SA 3.0
2 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 6, 2016 at 12:44 | comment | added | sara | Good points. I like the last sentence. People sometimes say "I chose an untestable design because it was better", but I don't buy that. An untestable design is inherently bad imo. All code needs to be tested. Doesn't matter if it's an automatic unit test runner, some big full-system tests or manual exploration tests or whatever. Teh code MUST be tested, so designing for testability is high prio. I'd rather have 10 well tested small classes than 3 large complex ones that cause brittle unmaintainable tests (or worse yet: force me to fire up IIS, compile all aspx files and launch my browser) | |
| Jun 6, 2016 at 11:10 | history | answered | Nathan | CC BY-SA 3.0 |