]>
git.saurik.com Git - apple/security.git/blob - SecurityTests/regressions/inc/Test/Builder/Tester.pm
1 package Test
::Builder
::Tester
;
12 Test::Builder::Tester - test testsuites that have been built with
17 use Test::Builder::Tester tests => 1;
20 test_out("not ok 1 - foo");
23 test_test("fail works");
27 A module that helps you test testing modules that are built with
30 The testing system is designed to be used by performing a three step
31 process for each test you wish to test. This process starts with using
32 C<test_out> and C<test_err> in advance to declare what the testsuite you
33 are testing will output with B<Test::Builder> to stdout and stderr.
35 You then can run the test(s) from your test suite that call
36 B<Test::Builder>. At this point the output of B<Test::Builder> is
37 safely captured by B<Test::Builder::Tester> rather than being
38 interpreted as real test output.
40 The final stage is to call C<test_test> that will simply compare what you
41 predeclared to what B<Test::Builder> actually outputted, and report the
42 results back with a "ok" or "not ok" (with debugging) to the normal
51 my $t = Test
::Builder-
>new;
58 our @ISA = qw(Exporter);
60 our @EXPORT = qw(test_out test_err test_fail test_diag test_test line_num);
62 # _export_to_level and import stolen directly from Test::More. I am
63 # the king of cargo cult programming ;-)
65 # 5.004's Exporter doesn't have export_to_level.
70 (undef) = shift; # XXX redundant arg
71 my $callpkg = caller($level);
72 $pkg->export($callpkg, @_);
81 $t->exported_to($caller);
85 foreach my $idx (0..$#plan) {
86 if( $plan[$idx] eq 'import' ) {
87 @imports = @{$plan[$idx+1]};
92 __PACKAGE__-
>_export_to_level(1, __PACKAGE__
, @imports);
99 # create some private file handles
100 my $output_handle = gensym
;
101 my $error_handle = gensym
;
103 # and tie them to this package
104 my $out = tie
*$output_handle, "Test::Builder::Tester::Tie", "STDOUT";
105 my $err = tie
*$error_handle, "Test::Builder::Tester::Tie", "STDERR";
111 # for remembering that we're testing and where we're testing at
115 # remembering where the file handles were originally connected
116 my $original_output_handle;
117 my $original_failure_handle;
118 my $original_todo_handle;
120 my $original_test_number;
121 my $original_harness_state;
123 my $original_harness_env;
125 # function that starts testing and redirects the filehandles for now
128 # even if we're running under Test::Harness pretend we're not
129 # for now. This needed so Test::Builder doesn't add extra spaces
130 $original_harness_env = $ENV{HARNESS_ACTIVE
} || 0;
131 $ENV{HARNESS_ACTIVE
} = 0;
133 # remember what the handles were set to
134 $original_output_handle = $t->output();
135 $original_failure_handle = $t->failure_output();
136 $original_todo_handle = $t->todo_output();
138 # switch out to our own handles
139 $t->output($output_handle);
140 $t->failure_output($error_handle);
141 $t->todo_output($error_handle);
143 # clear the expected list
147 # remeber that we're testing
149 $testing_num = $t->current_test;
152 # look, we shouldn't do the ending stuff
158 These are the six methods that are exported as default.
166 Procedures for predeclaring the output that your test suite is
167 expected to produce until C<test_test> is called. These procedures
168 automatically assume that each line terminates with "\n". So
170 test_out("ok 1","ok 2");
174 test_out("ok 1\nok 2");
176 which is even the same as
181 Once C<test_out> or C<test_err> (or C<test_fail> or C<test_diag>) have
182 been called once all further output from B<Test::Builder> will be
183 captured by B<Test::Builder::Tester>. This means that your will not
184 be able perform further tests to the normal output in the normal way
185 until you call C<test_test> (well, unless you manually meddle with the
192 # do we need to do any setup?
193 _start_testing
() unless $testing;
200 # do we need to do any setup?
201 _start_testing
() unless $testing;
208 Because the standard failure message that B<Test::Builder> produces
209 whenever a test fails will be a common occurrence in your test error
210 output, and because has changed between Test::Builder versions, rather
211 than forcing you to call C<test_err> with the string all the time like
214 test_err("# Failed test ($0 at line ".line_num(+1).")");
216 C<test_fail> exists as a convenience function that can be called
217 instead. It takes one argument, the offset from the current line that
218 the line that causes the fail is on.
222 This means that the example in the synopsis could be rewritten
225 test_out("not ok 1 - foo");
228 test_test("fail works");
234 # do we need to do any setup?
235 _start_testing
() unless $testing;
237 # work out what line we should be on
238 my ($package, $filename, $line) = caller;
239 $line = $line + (shift() || 0); # prevent warnings
241 # expect that on stderr
242 $err->expect("# Failed test ($0 at line $line)");
247 As most of the remaining expected output to the error stream will be
248 created by Test::Builder's C<diag> function, B<Test::Builder::Tester>
249 provides a convience function C<test_diag> that you can use instead of
252 The C<test_diag> function prepends comment hashes and spacing to the
253 start and newlines to the end of the expected output passed to it and
254 adds it to the list of expected error output. So, instead of writing
256 test_err("# Couldn't open file");
260 test_diag("Couldn't open file");
262 Remember that B<Test::Builder>'s diag function will not add newlines to
263 the end of output and test_diag will. So to check
265 Test::Builder->new->diag("foo\n","bar\n");
269 test_diag("foo","bar")
271 without the newlines.
277 # do we need to do any setup?
278 _start_testing
() unless $testing;
280 # expect the same thing, but prepended with "# "
282 $err->expect(map {"# $_"} @_)
287 Actually performs the output check testing the tests, comparing the
288 data (with C<eq>) that we have captured from B<Test::Builder> against
289 that that was declared with C<test_out> and C<test_err>.
291 This takes name/value pairs that effect how the test is run.
295 =item title (synonym 'name', 'label')
297 The name of the test that will be displayed after the C<ok> or C<not
302 Setting this to a true value will cause the test to ignore if the
303 output sent by the test to the output stream does not match that
304 declared with C<test_out>.
308 Setting this to a true value will cause the test to ignore if the
309 output sent by the test to the error stream does not match that
310 declared with C<test_err>.
314 As a convience, if only one argument is passed then this argument
315 is assumed to be the name of the test (as in the above examples.)
317 Once C<test_test> has been run test output will be redirected back to
318 the original filehandles that B<Test::Builder> was connected to
319 (probably STDOUT and STDERR,) meaning any further tests you run
320 will function normally and cause success/errors for B<Test::Harness>.
326 # decode the arguements as described in the pod
334 $mess = $args{name
} if exists($args{name
});
335 $mess = $args{title
} if exists($args{title
});
336 $mess = $args{label
} if exists($args{label
});
339 # er, are we testing?
340 croak
"Not testing. You must declare output with a test function first."
343 # okay, reconnect the test suite back to the saved handles
344 $t->output($original_output_handle);
345 $t->failure_output($original_failure_handle);
346 $t->todo_output($original_todo_handle);
348 # restore the test no, etc, back to the original point
349 $t->current_test($testing_num);
352 # re-enable the original setting of the harness
353 $ENV{HARNESS_ACTIVE
} = $original_harness_env;
355 # check the output we've stashed
356 unless ($t->ok( ($args{skip_out
} || $out->check)
357 && ($args{skip_err
} || $err->check),
360 # print out the diagnostic information about why this
365 $t->diag(map {"$_\n"} $out->complaint)
366 unless $args{skip_out
} || $out->check;
368 $t->diag(map {"$_\n"} $err->complaint)
369 unless $args{skip_err
} || $err->check;
375 A utility function that returns the line number that the function was
376 called on. You can pass it an offset which will be added to the
377 result. This is very useful for working out the correct text of
378 diagnostic functions that contain line numbers.
380 Essentially this is the same as the C<__LINE__> macro, but the
381 C<line_num(+3)> idiom is arguably nicer.
387 my ($package, $filename, $line) = caller;
388 return $line + (shift() || 0); # prevent warnings
393 In addition to the six exported functions there there exists one
394 function that can only be accessed with a fully qualified function
401 When C<test_test> is called and the output that your tests generate
402 does not match that which you declared, C<test_test> will print out
403 debug information showing the two conflicting versions. As this
404 output itself is debug information it can be confusing which part of
405 the output is from C<test_test> and which was the original output from
406 your original tests. Also, it may be hard to spot things like
407 extraneous whitespace at the end of lines that may cause your test to
408 fail even though the output looks similar.
410 To assist you, if you have the B<Term::ANSIColor> module installed
411 (which you should do by default from perl 5.005 onwards), C<test_test>
412 can colour the background of the debug information to disambiguate the
413 different types of output. The debug output will have it's background
414 coloured green and red. The green part represents the text which is
415 the same between the executed and actual output, the red shows which
418 The C<color> function determines if colouring should occur or not.
419 Passing it a true or false value will enable or disable colouring
420 respectively, and the function called with no argument will return the
423 To enable colouring from the command line, you can use the
424 B<Text::Builder::Tester::Color> module like so:
426 perl -Mlib=Text::Builder::Tester::Color test.t
428 Or by including the B<Test::Builder::Tester::Color> module directly in
436 $color = shift if @_;
444 Calls C<<Test::Builder->no_ending>> turning off the ending tests.
445 This is needed as otherwise it will trip out because we've run more
446 tests than we strictly should have and it'll register any failures we
447 had that we were testing for as real failures.
449 The color function doesn't work unless B<Term::ANSIColor> is installed
450 and is compatible with your terminal.
452 Bugs (and requests for new features) can be reported to the author
453 though the CPAN RT system:
454 L<http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Test-Builder-Tester>
458 Copyright Mark Fowler E<lt>mark@twoshortplanks.comE<gt> 2002, 2004.
460 Some code taken from B<Test::More> and B<Test::Catch>, written by by
461 Michael G Schwern E<lt>schwern@pobox.comE<gt>. Hence, those parts
462 Copyright Micheal G Schwern 2001. Used and distributed with
465 This program is free software; you can redistribute it
466 and/or modify it under the same terms as Perl itself.
470 This code has been tested explicitly on the following versions
471 of perl: 5.7.3, 5.6.1, 5.6.0, 5.005_03, 5.004_05 and 5.004.
473 Thanks to Richard Clamp E<lt>richardc@unixbeard.netE<gt> for letting
474 me use his testing system to try this module out on.
478 L<Test::Builder>, L<Test::Builder::Tester::Color>, L<Test::More>.
484 ####################################################################
485 # Helper class that is used to remember expected and received data
487 package Test
::Builder
::Tester
::Tie
;
490 # add line(s) to be expected
497 foreach my $check (@checks) {
498 $check = $self->_translate_Failed_check($check);
499 push @{$self->{wanted
}}, ref $check ? $check : "$check\n";
504 sub _translate_Failed_check
506 my($self, $check) = @_;
508 if( $check =~ /\A(.*)# (Failed .*test) \((.*?) at line (\d+)\)\Z(?!\n)/ ) {
509 $check = "/\Q$1\E#\\s+\Q$2\E.*?\\n?.*?\Qat $3\E line \Q$4\E.*\\n?/";
517 # return true iff the expected data matches the got data
523 # turn off warnings as these might be undef
526 my @checks = @{$self->{wanted
}};
527 my $got = $self->{got
};
528 foreach my $check (@checks) {
529 $check = "\Q$check\E" unless ($check =~ s
,^/(.*)/$,$1, or ref $check);
530 return 0 unless $got =~ s/^$check//;
533 return length $got == 0;
537 # a complaint message about the inputs not matching (to be
538 # used for debugging messages)
543 my $type = $self->type;
544 my $got = $self->got;
545 my $wanted = join "\n", @{$self->wanted};
547 # are we running in colour mode?
548 if (Test
::Builder
::Tester
::color
)
551 eval { require Term
::ANSIColor
};
556 my $green = Term
::ANSIColor
::color
("black").
557 Term
::ANSIColor
::color
("on_green");
558 my $red = Term
::ANSIColor
::color
("black").
559 Term
::ANSIColor
::color
("on_red");
560 my $reset = Term
::ANSIColor
::color
("reset");
562 # work out where the two strings start to differ
564 $char++ while substr($got, $char, 1) eq substr($wanted, $char, 1);
566 # get the start string and the two end strings
567 my $start = $green . substr($wanted, 0, $char);
568 my $gotend = $red . substr($got , $char) . $reset;
569 my $wantedend = $red . substr($wanted, $char) . $reset;
571 # make the start turn green on and off
572 $start =~ s/\n/$reset\n$green/g;
574 # make the ends turn red on and off
575 $gotend =~ s/\n/$reset\n$red/g;
576 $wantedend =~ s/\n/$reset\n$red/g;
578 # rebuild the strings
579 $got = $start . $gotend;
580 $wanted = $start . $wantedend;
584 return "$type is:\n" .
585 "$got\nnot:\n$wanted\nas expected"
589 # forget all expected and got data
595 type
=> $self->{type
},
611 return $self->{wanted
};
617 return $self->{type
};
626 $self->{got
} .= join '', @_;
630 my($class, $type) = @_;