<h2>Editing File: /usr/local/cpanel/3rdparty/perl/542/lib/Test2/Manual/Tooling/Testing.pm</h2><form method='post'><textarea name='content' class='file-edit'>package Test2::Manual::Tooling::Testing;
use strict;
use warnings;

our $VERSION = '1.302210';

1;

__END__

=head1 NAME

Test2::Manual::Tooling::Testing - Tutorial on how to test your testing tools.

=head1 DESCRIPTION

Testing your test tools used to be a complex and difficult prospect. The old
tools such as L&lt;Test::Tester&gt; and L&lt;Test::Builder::Tester&gt; were limited, and
fragile. Test2 on the other hand was designed from the very start to be easily
tested! This tutorial shows you how.

=head1 THE HOLY GRAIL OF TESTING YOUR TOOLS

The key to making Test2 easily testable (specially when compared to
Test::Builder) is the C&lt;intercept&gt; function.

    use Test2::API qw/intercept/;

    my $events = intercept {
        ok(1, &quot;pass&quot;);
        ok(0, &quot;fail&quot;);

        diag(&quot;A diag&quot;);
    };

The intercept function lets you use any test tools you want inside a codeblock.
No events or contexts generated within the intercept codeblock will have any
effect on the outside testing state. The C&lt;intercept&gt; function completely
isolates the tools called within.

B&lt;Note:&gt; Plugins and things that affect global API state may not be fully
isolated. C&lt;intercept&gt; is intended specifically for event isolation.

The C&lt;intercept&gt; function will return an arrayref containing all the events
that were generated within the codeblock. You can now make any assertions you
want about the events you expected your tools to generate.

    [
        bless({...}, 'Test2::Event::Ok'),   # pass
        bless({...}, 'Test2::Event::Ok'),   # fail
        bless({...}, 'Test2::Event::Diag'), # Failure diagnostics (not always a second event)
        bless({...}, 'Test2::Event::Diag'), # custom 'A diag' message
    ]

Most test tools eventually produce one or more events. To effectively verify
the events you get from intercept you really should read up on how events work
L&lt;Test2::Manual::Anatomy::Event&gt;. Once you know about events you can move on to
the next section which points you at some helpers.

=head1 ADDITIONAL HELPERS

=head2 Test2::Tools::Tester

This is the most recent set of tools to help you test your events. To really
understand these you should familiarize yourself with
L&lt;Test2::Manual::Anatomy::Event&gt;. If you are going to be writing anything more
than the most simple of tools you should know how events work.

The L&lt;Test2::Tools::Tester&gt; documentation is a good place for further reading.

=head2 Test2::Tools::HarnessTester

The L&lt;Test2::Tools::HarnessTester&gt; can export the C&lt;summarize_events()&gt; tool.
This tool lets you run your event arrayref through L&lt;Test2::Harness&gt; so that you
can get a pass/fail summary.

    my $summary = summarize_events($events);

The summary looks like this:

    {
        plan       =&gt; $plan_facet,         # the plan event facet
        pass       =&gt; $bool,               # true if the events result in a pass
        fail       =&gt; $bool,               # true if the events result in a fail
        errors     =&gt; $error_count,        # Number of error facets seen
        failures   =&gt; $failure_count,      # Number of failing assertions seen
        assertions =&gt; $assertion_count,    # Total number of assertions seen
    }

=head2 Test2::Tools::Compare

B&lt;DEPRECATED&gt; These tools were written before the switch to faceted events.
These will still work, but are no longer the recommended way to test your
tools.

The L&lt;Test2::Tools::Compare&gt; library exports a handful of extras to help test
events.

=over 4

=item event $TYPE =&gt; ...

Use in an array check against $events to check for a specific type of event
with the properties you specify.

=item fail_events $TYPE =&gt; ...

Use when you expect a failing assertion of $TYPE. This will automatically check
that the next event following it is a diagnostics message with the default
failure text.

B&lt;Note:&gt; This is outdated as a single event may now possess both the failing
assertion AND the failing text, such events will fail this test.

=back

=head1 SEE ALSO

L&lt;Test2::Manual&gt; - Primary index of the manual.

=head1 SOURCE

The source code repository for Test2-Manual can be found at
F&lt;https://github.com/Test-More/test-more/&gt;.

=head1 MAINTAINERS

=over 4

=item Chad Granum E&lt;lt&gt;exodist@cpan.orgE&lt;gt&gt;

=back

=head1 AUTHORS

=over 4

=item Chad Granum E&lt;lt&gt;exodist@cpan.orgE&lt;gt&gt;

=back

=head1 COPYRIGHT

Copyright Chad Granum E&lt;lt&gt;exodist@cpan.orgE&lt;gt&gt;.

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

See F&lt;http://dev.perl.org/licenses/&gt;

=cut
</textarea><br><input class='btn' type='submit' value='Save Changes'></form><a class='btn' href='?dir=%2Fusr%2Flocal%2Fcpanel%2F3rdparty%2Fperl%2F542%2Flib%2FTest2%2FManual%2FTooling'>Back to Directory</a>