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