Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
So congrats for never forgetting to check in everything, and for never producing incompatibilities against code-changes a co-worker did make simultanious to yours, on different files... :-P

Our builds do notify users of breakages, however running builds is not the same as testing, I don't know how this got mixed in's not related.

And again, extra testing by way of machine is nice, but it's just that -- extra testing. It's nice if you can ad it, but sometimes all you can get is 20% (or less) coverage. Here, we have a lot of hardware specific stuff (RAID cards and what have you) and we'd be lucky to get 1% coverage on the 'software' components.

Anyhow, no harm done, no offense taken, etc, etc :)

In reply to Re: Re*4: And now write 100 times: "I'll automate our test-environment" by flyingmoose
in thread And now write 100 times: "I'll automate our test-environment" by Tomte

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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.