Skip to content

Commit ebfdfc0

Browse files
committed
don't talk about TAP (to be squashed)
Test::More generally talks about "tests", ok() evaluates the expression and "uses that to determine is the test succeeded or failed", so I've followed that. Unfortunately "test" is a little overloaded, so it might be more confusing.
1 parent d887ad2 commit ebfdfc0

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

t/test_pl.pod

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -203,7 +203,8 @@ Test::More compatible:
203203

204204
=head1 Extended test functions
205205

206-
These test some condition and produce TAP for a test.
206+
These perform some sort of test, in some cases results for multiple
207+
tests are produced:
207208

208209
=over
209210

@@ -254,7 +255,7 @@ C<@expect_qr> in sequence.
254255
warnings_like(sub { my $x; $x+1 }, [ qr/Undefined value/ ],
255256
"undefined value in addition");
256257

257-
Produces TAP for C< 1 + scalar(@expect_qr) > tests, one for the count
258+
Produces C< 1 + scalar(@expect_qr) > test results, one for the count
258259
of warnings, and one for each warning checked.
259260

260261
=item warning_is($subref, $expect, $name)
@@ -346,8 +347,8 @@ run them per C< run_multiple_progs($up, @test_progs) >.
346347

347348
=item run_multiple_progs($up, @test_progs)
348349

349-
Run each of the test programs, producing TAP for a test result for
350-
each test.
350+
Run each of the test programs, testing whether the output, and
351+
optionally the exit value, matches the expected output.
351352

352353
See L</run_multiple_progs() tests> for the details of the format of
353354
each test.

0 commit comments

Comments
 (0)