Timeline for Unit testing coverage
Current License: CC BY-SA 2.5
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 6, 2011 at 20:45 | comment | added | Péter Török | @Ptolemy, my point is, if testing that code line brings the most benefits compared to its costs, test it indeed, right away. However, if there are 999 other untested code lines with a better testing cost/benefit ratio, this one should be tested only by the 1000th unit test. And if you only have time to write 500 unit tests before deadline, then sorry, this line won't get unit tested in this release. I agree with you 100% that error/exception handling is important in general. | |
| Apr 6, 2011 at 19:01 | comment | added | Michael Shaw | Testing error code can bring a major benefit to your customer. It makes the difference between the feature not working, user clicks OK on an error dialog or the alternative outcome of the application crashing and loosing your customers data. | |
| Mar 29, 2011 at 11:48 | history | edited | Péter Török | CC BY-SA 2.5 | added 55 characters in body |
| Mar 29, 2011 at 11:42 | history | answered | Péter Török | CC BY-SA 2.5 |