Considering that I do QA automation.

1) edit the files locally using vim.
2) test it on my computer.
3) check it in using CVS.
4) goto the production box (ssh or telnet depending on which one) and check it out and test it out. install any moduals required.
5) if needed (like the cgi scripts) put it in apaches cgi-bin directory.
6) remind the head developer to update his copy of the QA scripts tree. This is so that when he releases a build, no one has to check out the tagged version of the source tree , build the program, install it and then check out the recent version so that my code can test it.
7) if no new code drop is set to tested that day. Start it up and watch the bugs fly.*grin*

In reply to Re: Whats your development environment by Pug
in thread Whats your development environment by hakkr

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


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.