CONTENTS

• NAME
• DESCRIPTION
• SYNOPSIS
• METHODS
  • !!! IMPORTANT NOTES ON DESIGN !!!
  • ATTRIBUTES
  • DUPLICATION
  • CONDENSED MULTI-FACET DATA
  • DIRECT ARBITRARY FACET ACCESS
  • TRACE FACET
  • ASSERT FACET
  • SUBTESTS (PARENT FACET)
  • CONTROL FACET (BAILOUT, ENCODING)
  • PLAN FACET
  • AMNESTY FACET (TODO AND SKIP)
  • ERROR FACET (CAPTURED EXCEPTIONS)
  • INFO FACET (DIAG, NOTE)
• SOURCE
• MAINTAINERS
• AUTHORS
• COPYRIGHT

#NAME

Test2::API::InterceptResult::Event - Representation of an event for use in testing other test tools.

#DESCRIPTION

intercept { ... } from Test2::API returns an instance of Test2::API::InterceptResult which is a blessed arrayref of Test2::API::InterceptResult::Event objects.

This POD documents the methods of these events, which are mainly provided for you to use when testing your test tools.

#SYNOPSIS

use Test2::V0;
use Test2::API qw/intercept/;

my $events = intercept {
    ok(1, "A passing assertion");
    plan(1);
};

# This will convert all events into instances of
# Test2::API::InterceptResult::Event. Until we do this they are the
# original Test::Event::* instances
$events->upgrade(in_place => 1);

# Now we can get individual events in this form
my $assert = $events->[0];
my $plan   = $events->[1];

# Or we can operate on all events at once:
my $flattened = $events->flatten;
is(
    $flattened,
    [
      {
        causes_failure => 0,

        name => 'A passing assertion',
        pass => 1,

        trace_file => 'xxx.t',
        trace_line => 5,
      },
      {
        causes_failure => 0,

        plan => 1,

        trace_file => 'xxx.t',
        trace_line => 6,
      },
    ],
    "Flattened both events and returned an arrayref of the results
);

#METHODS

#!!! IMPORTANT NOTES ON DESIGN !!!

Please pay attention to what these return, many return a scalar when applicable or an empty list when not (as opposed to undef). Many also always return a list of 0 or more items. Some always return a scalar. Note that none of the methods care about context, their behavior is consistent regardless of scalar, list, or void context.

This was done because this class was specifically designed to be used in a list and generate more lists in bulk operations. Sometimes in a map you want nothing to show up for the event, and you do not want an undef in its place. In general single event instances are not going to be used alone, though that is allowed.

As a general rule any method prefixed with the_ implies the event should have exactly 1 of the specified item, and and exception will be thrown if there are 0, or more than 1 of the item.

#ATTRIBUTES

#$hashref = $event->facet_data

This will return the facet data hashref, which is all Test2 cares about for any given event.

#$class = $event->result_class

This is normally Test2::API::InterceptResult. This is set at construction so that subtest results can be turned into instances of it on demand.

#DUPLICATION

#$copy = $event->clone

Create a deep copy of the event. Modifying either event will not effect the other.

#CONDENSED MULTI-FACET DATA

#$bool = $event->causes_failure

#$bool = $event->causes_fail

These are both aliases of the same functionality.

This will always return either a true value, or a false value. This never returns a list.

This method may be relatively slow (still super fast) because it determines pass or fail by creating an instance of Test2::Hub and asking it to process the event, and then asks the hub for its pass/fail state. This is slower than bulding in logic to do the check, but it is more reliable as it will always tell you what the hub thinks, so the logic will never be out of date relative to the Test2 logic that actually cares.

#STRING_OR_EMPTY_LIST = $event->brief

Not all events have a brief, some events are not rendered by the formatter, others have no "brief" data worth seeing. When this is the case an empty list is returned. This is done intentionally so it can be used in a map operation without having undef being included in the result.

When a brief can be generated it is always a single 1-line string, and is returned as-is, not in a list.

Possible briefs:

# From control facets
"BAILED OUT"
"BAILED OUT: $why"

# From error facets
"ERROR"
"ERROR: $message"
"ERROR: $partial_message [...]"
"ERRORS: $first_error_message [...]"

# From assert facets
"PASS"
"FAIL"
"PASS with amnesty"
"FAIL with amnesty"

# From plan facets
"PLAN $count"
"NO PLAN"
"SKIP ALL"
"SKIP ALL: $why"

Note that only the first applicable brief is returned. This is essnetially a poor-mans TAP that only includes facets that could (but not necessarily do) cause a failure.

#$hashref = $event->flatten

#$hashref = $event->flatten(include_subevents => 1)

This ALWAYS returns a hashref. This puts all the most useful data for the most interesting facets into a single hashref for easy validation.

If there are no meaningful facets this will return an empty hashref.

If given the 'include_subevents' parameter it will also include subtest data:

Here is a list of EVERY possible field. If a field is not applicable it will not be present.

#always present

causes_failure => 1,    # Always present

#Present if the event has a trace facet

trace_line    => 42,
trace_file    => 'Foo/Bar.pm',
trace_details => 'Extra trace details',    # usually not present

#