If not all tests were successful, the script dies with one of the
above messages.
<P></P></DL>
<P>
<HR>
<H1><A NAME="environment">ENVIRONMENT</A></H1>
<P>Setting <CODE>HARNESS_IGNORE_EXITCODE</CODE> makes harness ignore the exit status
of child processes.</P>
<P>Setting <CODE>HARNESS_NOTTY</CODE> to a true value forces it to behave as though
STDOUT were not a console. You may need to set this if you don't want
harness to output more frequent progress messages using carriage returns.
Some consoles may not handle carriage returns properly (which results
in a somewhat messy output).</P>
<P>Setting <CODE>HARNESS_COMPILE_TEST</CODE> to a true value will make harness attempt
to compile the test using <CODE>perlcc</CODE> before running it.</P>
<P>If <CODE>HARNESS_FILELEAK_IN_DIR</CODE> is set to the name of a directory, harness
will check after each test whether new files appeared in that directory,
and report them as</P>
<PRE>
LEAKED FILES: scr.tmp 0 my.db</PRE>
<P>If relative, directory name is with respect to the current directory at
the moment <CODE>runtests()</CODE> was called. Putting absolute path into
<CODE>HARNESS_FILELEAK_IN_DIR</CODE> may give more predicatable results.</P>
<P>The value of <CODE>HARNESS_PERL_SWITCHES</CODE> will be prepended to the
switches used to invoke perl on each test. For example, setting
<CODE>HARNESS_PERL_SWITCHES</CODE> to ``-W'' will run all tests with all
warnings enabled.</P>
<P>Harness sets <CODE>HARNESS_ACTIVE</CODE> before executing the individual tests.
This allows the tests to determine if they are being executed through the
harness or by any other means.</P>
<P>
<HR>
<H1><A NAME="see also">SEE ALSO</A></H1>
<P><A HREF="../../lib/Test.html">the Test manpage</A> for writing test scripts and also <A HREF="../../lib/Benchmark.html">the Benchmark manpage</A> for the
underlying timing routines.</P>
<P>
<HR>
<H1><A NAME="authors">AUTHORS</A></H1>
<P>Either Tim Bunce or Andreas Koenig, we don't know. What we know for
sure is, that it was inspired by Larry Wall's TEST script that came
with perl distributions for ages. Numerous anonymous contributors
exist. Current maintainer is Andreas Koenig.</P>
<P>
<HR>
<H1><A NAME="bugs">BUGS</A></H1>
<P>Test::Harness uses $^X to determine the perl binary to run the tests
with. Test scripts running via the shebang (<CODE>#!</CODE>) line may not be
portable because $^X is not consistent for shebang scripts across
platforms. This is no problem when Test::Harness is run with an
absolute path to the perl binary or when $^X can be found in the path.</P>