Timeline for When is unit testing inappropriate or unnecessary?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot |
replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
|
|
| Sep 28, 2014 at 21:39 | comment | added | Benjamin Hodgson | This is an outstanding answer. It addresses the trade-offs involved in choosing a testing strategy in a measured and results-oriented way. | |
| May 12, 2012 at 14:52 | history | made wiki | Post Made Community Wiki by raffi | ||
| May 9, 2012 at 17:43 | comment | added | jakesandlund | @sleske: Yes, but fast-moving projects tend to lack the specific (and stable) requirements that you can unit test for. Often, all that's known is the higher level requirements, which lend more to integration tests. | |
| May 9, 2012 at 8:56 | comment | added | sleske | Actually, testing can help in fast-moving projects - but you must be more careful about what you test. You cannot test things where you have not yet decided what the right result is :-). | |
| May 7, 2012 at 16:02 | history | edited | jakesandlund | CC BY-SA 3.0 |
Remove sentence on assumption of existing test framework for flat cost line
|
| May 6, 2012 at 15:14 | comment | added | Steve Bennett | Great answer - testing is least valuable in fast-moving projects with unknown requirements, and also slow-moving projects with very stable code. Given that most of my work is in the former, this gels with me - but also makes clear that we need to get testing happening as things stabilise. | |
| May 5, 2012 at 19:06 | history | edited | jakesandlund | CC BY-SA 3.0 |
Added inline images and fixed links
|
| May 4, 2012 at 21:27 | history | edited | jakesandlund | CC BY-SA 3.0 |
remove TDD reference
|
| May 4, 2012 at 21:13 | history | answered | jakesandlund | CC BY-SA 3.0 |