Once you've finally gotten it into your teammates' heads that checking in code that breaks the build is a Very Bad Thing, you can break the build yourself, and not get blamed for it. How? Very simply. When you discover that one of your teammates has checked in flakey code, add a test case that demonstrates a failure, and check in the test case. Boom, there goes the build. But is is your fault? Heh heh, no.
I'm really loving this aspect of unit testing right now.
(Cue maniacal laughter)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||