Gecko [ 0.0.0.0 ]

Name	Size	Permission
API	[ DIR ]	drwxr-xr-x
AsyncSubtest	[ DIR ]	drwxr-xr-x
Bundle	[ DIR ]	drwxr-xr-x
Compare	[ DIR ]	drwxr-xr-x
Event	[ DIR ]	drwxr-xr-x
EventFacet	[ DIR ]	drwxr-xr-x
Formatter	[ DIR ]	drwxr-xr-x
Hub	[ DIR ]	drwxr-xr-x
IPC	[ DIR ]	drwxr-xr-x
Manual	[ DIR ]	drwxr-xr-x
Plugin	[ DIR ]	drwxr-xr-x
Require	[ DIR ]	drwxr-xr-x
Tools	[ DIR ]	drwxr-xr-x
Util	[ DIR ]	drwxr-xr-x
Workflow	[ DIR ]	drwxr-xr-x
API.pm	48.43 KB	-rw-r--r--
AsyncSubtest.pm	19.08 KB	-rw-r--r--
Bundle.pm	1.52 KB	-rw-r--r--
Compare.pm	11.53 KB	-rw-r--r--
Event.pm	22.11 KB	-rw-r--r--
EventFacet.pm	1.46 KB	-rw-r--r--
Formatter.pm	3.86 KB	-rw-r--r--
Hub.pm	22.31 KB	-rw-r--r--
IPC.pm	3.1 KB	-rw-r--r--
Manual.pm	1.49 KB	-rw-r--r--
Mock.pm	22.27 KB	-rw-r--r--
Plugin.pm	1.83 KB	-rw-r--r--
Require.pm	2.65 KB	-rw-r--r--
Suite.pm	9.26 KB	-rw-r--r--
Todo.pm	3.77 KB	-rw-r--r--
Tools.pm	2.51 KB	-rw-r--r--
Transition.pod	13.17 KB	-rw-r--r--
Util.pm	10.33 KB	-rw-r--r--
V0.pm	11.56 KB	-rw-r--r--
Workflow.pm	7.13 KB	-rw-r--r--

Code Editor : Tools.pm

package Test2::Tools;
use strict;
use warnings;

our $VERSION = '0.000162';

__END__

=pod

=encoding UTF-8

=head1 NAME

Test2::Tools - Documentation for Tools.

=head1 DESCRIPTION

Tools are packages that export test functions, typically all related to a
specific aspect of testing. If you have a couple different categories of
exports then you may want to break them into separate modules.

Tools should export testing functions. Loading tools B<should not> have side
effects, or alter the behavior of other tools. If you want to alter behaviors
or create side effects then you probably want to write a L<Test2::Plugin>.

=head1 FAQ

=over 4

=item Why is it called Test2::Tools, and not Test2::Tool?

This question arises since Tools is the only namespace in the plural. This is
because each Plugin should be a distinct unit of functionality, but a Tools
dist can (and usually should) export several tools. A bundle is also typically
described as a single unit. Nobody would like Test2::Bundles::Foo.

=item Should my tools subclass Test2::Tools?

No. Currently this class is empty. Eventually we may want to add behavior, in
which case we do not want anyone to already be subclassing it.

=back

=head1 HOW DO I WRITE A 'TOOLS' MODULE?

It is very easy to write tools:

package Test2::Tools::Mine
    use strict;
    use warnings;

# All tools should use the context() function.
    use Test2::API qw/context/;

our @EXPORTS = qw/ok plan/;
    use base 'Exporter';

sub ok($;$) {
        my ($bool, $name) = @_;

# All tool functions should start by grabbing a context
        my $ctx = context();

# The context is the primary interface for generating events
        $ctx->ok($bool, $name);

# When you are done you release the context
        $ctx->release;

return $bool ? 1 : 0;
    }

sub plan {
        my ($max) = @_;
        my $ctx = context();
        $ctx->plan($max);
        $ctx->release;
    }

See L<Test2::API::Context> for documentation on what the C<$ctx> object can do.

=head1 SOURCE

The source code repository for Test2-Suite can be found at
F<https://github.com/Test-More/Test2-Suite/>.

=head1 MAINTAINERS

=over 4

=item Chad Granum E<lt>exodist@cpan.orgE<gt>

=back

=head1 AUTHORS

=over 4

=item Chad Granum E<lt>exodist@cpan.orgE<gt>

=back

=head1 COPYRIGHT

This program is free software; you can redistribute it and/or
modify it under the same terms as Perl itself.

See F<http://dev.perl.org/licenses/>

=cut

${this.title}

Code Editor : Tools.pm