From: Jan Dubois <jand@activestate.com>
Date: Wed, 24 Feb 1999 22:34:56 +0000 (+0100)
Subject: Test::Harness setting $ENV{HARNESS_ACTIVE}
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=f19ae7a76ae03aca964bfc271ce674fffe816d24;p=p5sagit%2Fp5-mst-13.2.git

Test::Harness setting $ENV{HARNESS_ACTIVE}

	Message-ID: <36d86f1e.11495549@smtp1.ibm.net>

p4raw-id: //depot/perl@3030
---

diff --git a/lib/Test/Harness.pm b/lib/Test/Harness.pm
index 219ffb9..738f36d 100644
--- a/lib/Test/Harness.pm
+++ b/lib/Test/Harness.pm
@@ -13,6 +13,8 @@ $have_devel_corestack = 0;
 
 $VERSION = "1.1602";
 
+$ENV{HARNESS_ACTIVE} = 1;
+
 # Some experimental versions of OS/2 build have broken $?
 my $ignore_exitcode = $ENV{HARNESS_IGNORE_EXITCODE};
 
@@ -458,6 +460,10 @@ If relative, directory name is with respect to the current directory at
 the moment runtests() was called.  Putting absolute path into 
 C<HARNESS_FILELEAK_IN_DIR> may give more predicatable results.
 
+Harness sets C<HARNESS_ACTIVE> before executing the individual tests.
+This allows the tests to determine if they are being executed through the
+harness or by any other means.
+
 =head1 SEE ALSO
 
 L<Test> for writing test scripts and also L<Benchmark> for the