Acme-Test-Buffy
view release on metacpan or search on metacpan
lib/Acme/Test/Buffy.pm view on Meta::CPAN
The reason for writing this module is to demonstrate how you
can write testing modules that work together with B<Test::Builder>.
It also shows how to test such modules with B<Test::Builder::Tester>.
Look at the source code (which is heavily commented) for further
enlightenment.
This module simply exports one testing function that tests if a string
is the same as "Buffy" (case sensitive.)
=cut
# here's where we define the subroutine "is_buffy" that will be
# exported. Note the prototype that does the right thing. More
# can be found out about prototypes in the 'perlsub' perldoc.
# This one simply says "one scalar argument and possibly another"
sub is_buffy($;$)
{
# simply call the other subroutine. There's no reason why this
# couldn't be done here, I just want to show how to call other
# subroutines in this class. This supplied a default test
# description
_do_buffy_test(shift(), shift() || "is 'Buffy'");
}
# this is a second subroutine that's used to demonstrate how you
# should deal with calling subroutines.
sub _do_buffy_test
{
# as we've entered another subroutine we need to increase the
# counter that Test::Builder uses to state where the error
# comes from (so we get an error at the line in your test
# script not from within the call to this routine in 'is_buffy')
# we use a local so that the level is returned to the previous
# value when we exit the subroutine. Note that we can't use
# the ++ operator here as it doesn't do what you might think.
local $Test::Builder::Level = $Test::Builder::Level + 1;
# get the args
my ($maybe_buffy, $text) = @_;
# do the test
if ($maybe_buffy eq "Buffy")
{
# print okay with the right text ("ok <number> - <text>")
$Tester->ok(1,$text);
# return a true value (don't have to do this but it's nice)
return 1;
}
else
{
# We failed. We want to test Test::Builder to print something
# like:
# Failed test at line <line number>
# Expected 'Buffy' but got '<what we got>' instead
# that is to say we print failure first, _then_ the extra diag
# stuff that will help people debug the code better.
# print not okay with the right text ("not ok <number> - <text>")
$Tester->ok(0,$text);
# print diagnostics of *why* it failed. Don't just print to
# STDERR this is bad and wrong as it prevents the test output
# being properly caught. Note the "\n" on the end of the
# line.
$Tester->diag("Expected 'Buffy' but got '$maybe_buffy' instead\n");
# return a false value (don't have to do this, but it's nice)
return 0;
}
}
=head1 BUGS
None known. Please report, including documentation bugs to
the author. You may use the CPAN RT system.
L<http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Acme-Test-Buffy>
=head1 AUTHOR
Copyright Mark Fowler
E<lt>mark@twoshortplanks.comE<gt> 2002-2004
All rights reserved.
This program is free software; you can redistribute it
and/or modify it under the same terms as Perl itself.
=head1 NOTES
Module also written to annoy Leon Brocard, who will have to update his
YAPC::Europe talk slides to include it a mere ten minutes before his
talk.
=head1 SEE ALSO
L<Test::Builder>, L<Test::Builder::Tester>, L<Test::More>.
=cut
# and return true
1;
( run in 2.868 seconds using v1.01-cache-2.11-cpan-39bf76dae61 )