However what I did not do was write a test case to prove it was fixed or know that one of the developers had already downloaded a copy of the buggy code (during that 4 hour or so window) which promptly stomped on the bug fix when it got committed.
CVS?
Adding insult to injury, I once fixed a bug and added a unit test, only to have both overwritten.
But that's a rarity. 99%+ of the time, adding a unit test pays off not only in detected when one particular problem regresses, but also in catching problems as they percolate. The last few times I tracked down problems in a medium-sized J2EE application, I started by running the full set of unit tests. By resolving any failing tests first, even if the tests seemed to have nothing to do with the symptoms we were seeing, problems seemed to voluntary step forward waving surrender flags.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.