Timeline for When is unit testing inappropriate or unnecessary?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 12, 2012 at 14:52 | history | made wiki | Post Made Community Wiki by raffi | ||
| May 9, 2012 at 8:54 | comment | added | sleske | While I agree that all production code needs tests, they do not necessarily need to be unit tests - in some scenarios integration tests make more sense. | |
| May 4, 2012 at 21:48 | comment | added | Thymine | @SteveBennett It should be only "If the requirements will need modification, the tests will also cost more" | |
| May 4, 2012 at 13:47 | comment | added | Bill Michell | Yes, I test those scripts. And they can't be tested with unit tests, but they can still be tested. | |
| May 4, 2012 at 8:04 | comment | added | Steve Bennett | Ok - but if the code "will need modifications", the tests will also cost more, right? Also, do you test shell scripts? Build scripts? | |
| May 3, 2012 at 16:34 | comment | added | Bill Michell | @noahz Yes, I'll buy that. But on the "must, should, would" scale, I selected "should" and not "must"... | |
| May 3, 2012 at 15:03 | comment | added | noahz | Did not down-vote, but I would offer that the idea that all code must have a test is border-line religious, and not always practical. | |
| May 3, 2012 at 13:38 | comment | added | Bill Michell | I'd appreciate an insight into why somebody down voted this post. | |
| May 3, 2012 at 10:57 | history | answered | Bill Michell | CC BY-SA 3.0 |