What I have begun to do, in large test cases, is to insert logic at the beginning of each test file which sets-up the correct environment for that test file. In other words, instead of putting the setup responsibility into “the wrapper,” so to speak, I push it down into some bit of common-code that all of the individual test files use or include. “It just works out better that way,” one very nice feature being that tests can be run individually (they are Perl programs, after all...) or in a given harness, and everything works out the same way regardless. The test files no longer depend upon “I am being run within this-or-that harness” (and I use the word “harness” loosely here). They run consistently no matter how they are run. (And, the necessary changes need only be done in one file or unit which they all reference.)
-
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.
|