Prefer TAP::Harness over Test::Harness
authorRichard Levitte <levitte@openssl.org>
Wed, 10 May 2017 10:58:36 +0000 (12:58 +0200)
committerRichard Levitte <levitte@openssl.org>
Wed, 10 May 2017 15:08:17 +0000 (17:08 +0200)
commitfbf09642692d3bf9343301d1e8befd37eef0277c
treecfa3a6f71730b5d60dc0ce141a30042159cf1ebd
parent410ab527b38ea99e1d897cc60c45aad0d9bac913
Prefer TAP::Harness over Test::Harness

TAP:Harness came along in perl 5.10.1, and since we claim to support
perl 5.10.0 in configuration and testing, we can only load it
conditionally.

The main reason to use TAP::Harness rather than Test::Harness is its
capability to merge stdout and stderr output from the test recipes,
which Test::Harness can't.  The merge gives much more comprehensible
output when testing verbosely.

Reviewed-by: Rich Salz <rsalz@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/3424)
(cherry picked from commit 76e0d0b21cc4e8a879d54f4d78a392826dadb1d1)
test/run_tests.pl