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)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|