Timeline for What should you test with unit tests?
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2017 at 20:46 | comment | added | BugHunterUK | Your answer was featured in this popular medium article: hackernoon.com/… | |
| Jun 7, 2016 at 9:28 | comment | added | ankush981 | Having just started, I find I'm not very creative with devising tests. So I use them as #3 above, which ensures peace of mind that those bugs will never again go undetected. | |
| Oct 20, 2015 at 1:04 | comment | added | ryno | #3 seems like a very solid answer as it is a real life example of how a unit test could have helped. If it broke once, it can break again. | |
| Jun 30, 2012 at 10:49 | comment | added | mikera | +1, though I would also test the edge cases of any library/utility-type functions to ensure you have a logical API. e.g. what happens when a null is passed? what about empty input? This will help ensure your design is logical and document the corner case behaviour. | |
| Nov 27, 2010 at 2:13 | comment | added | Stephen | Thanks for this, I was floundering over here with the same questions as the OP. | |
| Sep 3, 2010 at 16:47 | history | answered | Fishtoaster | CC BY-SA 2.5 |