Eric Wilhelm wrote:
# from Aristotle Pagaltzis
# on Sunday 30 March 2008 23:14:
Except that the test program might be running at the other end of
an HTTP connection. Or at the other end of a serial port. Or the
harness might be parsing an archived TAP stream. Or a TAP archive
generated offline in batch mode. Or…
That's a good point, but what does it have to do with plans?
$ perl -e 'use Test::More qw(no_plan); ok(1); die;' 2> /dev/null
ok 1
1..1
This will look like a success.
$ perl -wle 'use Test::More "no_plan"; pass(); die; pass()' 2>/dev/null
ok 1
1..1
This will look like a failure.
$ perl -wle 'use Test::More tests => 2; pass(); die; pass()' 2>/dev/null
1..2
ok 1
If you can't see the exit code of the test then the plan protects you.
There is a TAP proposal to add meta information such as the exit codes.
http://testanything.org/wiki/index.php/TAP_meta_information
--
Being faith-based doesn't trump reality.
-- Bruce Sterling
