I worked a project using KSH script on UNIX machines to execute test scripts against embedded code. Please note, the goal was to test the code.
Biggest problems we had were migrating non-Unix users into an "environment" environment. If PERL could get you around the number of wasted man-hours we invested in debugging scripts that worked under one sign-in and not the next due to environment variables....
We burned a lot of man-hours NOT testing the target code, with scripts that "should" have run; all due to a nominally controlled user environment.
Is PERL going to help me avoid the difficulties induced by a bad environment to begin with? Will it help you?
Emmett
-
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.
|