Lines Matching refs:details
169 $out->{about}->{details} = $self->summary || undef;
183 details => $self->summary,
192 $out->{plan}->{details} = $plan[2] if defined $plan[2];
207 details => $self->summary,
220 details => $self->summary,
377 $facet_data->{assert} = {pass => 1, details => 'my assertion'};
415 =item $e->add_amnesty({tag => $TAG, details => $DETAILS});
425 amnesty with the 'TODO' tag. The details are the reason for the TODO.
545 B<Note:> Every single facet type has the C<'details'> field. This field is
556 name. The C<details> field for this facet is an overall summary of the event.
562 This facet is used if an assertion was made. The C<details> field of this facet
571 etc. In this facet the C<details> field explains why any special action was
581 the C<details> field has no special meaning, but may be present if something
582 sets the 'details' meta-key on the event.
588 This facet contains nested events and similar details for subtests. In this
589 facet the C<details> field will typically be the name of the subtest.
595 This facet tells the system that a plan has been set. The C<details> field of
607 In this facet the C<details> field overrides the "failed at test_file.t line
617 For each instance of amnesty the C<details> field explains why amnesty was
628 be listed. In this facet C<details> describes the error, or may contain the raw
651 For this facet the C<details> flag is the info itself. This info may be a