.\" Automatically generated by Pod::Man 4.14 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" Set up some character translations and predefined strings.  \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote.  \*(C+ will
.\" give a nicer C++.  Capital omega is used to do unbreakable dashes and
.\" therefore won't be available.  \*(C` and \*(C' expand to `' in nroff,
.\" nothing in troff, for use with C<>.
.tr \(*W-
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
.ie n \{\
.    ds -- \(*W-
.    ds PI pi
.    if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
.    if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\"  diablo 12 pitch
.    ds L" ""
.    ds R" ""
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds -- \|\(em\|
.    ds PI \(*p
.    ds L" ``
.    ds R" ''
.    ds C`
.    ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\"
.\" If the F register is >0, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.\"
.\" Avoid warning from groff about undefined register 'F'.
.de IX
..
.nr rF 0
.if \n(.g .if rF .nr rF 1
.if (\n(rF:(\n(.g==0)) \{\
.    if \nF \{\
.        de IX
.        tm Index:\\$1\t\\n%\t"\\$2"
..
.        if !\nF==2 \{\
.            nr % 0
.            nr F 2
.        \}
.    \}
.\}
.rr rF
.\" ========================================================================
.\"
.IX Title "Test::BDD::Cucumber::Harness::Data 3pm"
.TH Test::BDD::Cucumber::Harness::Data 3pm "2023-08-29" "perl v5.36.0" "User Contributed Perl Documentation"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH "NAME"
Test::BDD::Cucumber::Harness::Data \- Builds up an internal data representation of test passes / failures
.SH "VERSION"
.IX Header "VERSION"
version 0.86
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
A Test::BDD::Cucumber::Harness subclass which collates test data
.SH "ATTRIBUTES"
.IX Header "ATTRIBUTES"
.SS "features"
.IX Subsection "features"
An array-ref in which we store all the features executed, and completed. Until
\&\f(CW\*(C`feature_done\*(C'\fR is called, it won't be in here.
.SS "current_feature"
.IX Subsection "current_feature"
.SS "current_scenario"
.IX Subsection "current_scenario"
.SS "current_step"
.IX Subsection "current_step"
The current feature/step/scenario for which we've had the starting method, but
not the \f(CW\*(C`_done\*(C'\fR method.
.SS "feature"
.IX Subsection "feature"
.SS "feature_done"
.IX Subsection "feature_done"
Feature hashref looks like:
.PP
.Vb 4
\& {
\&        object    => Test::BDD::Cucumber::Model::Feature object
\&        scenarios => []
\& }
.Ve
.SS "scenario"
.IX Subsection "scenario"
.SS "scenario_done"
.IX Subsection "scenario_done"
Scenario hashref looks like:
.PP
.Vb 5
\& {
\&        object  => Test::BDD::Cucumber::Model::Scenario object
\&        dataset => Data hash the scenario was invoked with
\&        steps   => [],
\& }
.Ve
.SS "step"
.IX Subsection "step"
.SS "step_done"
.IX Subsection "step_done"
Step hashref looks like:
.PP
.Vb 4
\& {
\&        context => Test::BDD::Cucumber::StepContext object
\&        result  => Test::BDD::Cucumber::Model::Result object (after step_done)
\& }
.Ve
.SS "feature_status"
.IX Subsection "feature_status"
.SS "scenario_status"
.IX Subsection "scenario_status"
.SS "step_status"
.IX Subsection "step_status"
Accepting one of the data-hashes above, returns a
Test::BDD::Cucumber::Model::Result object representing it. If it's a Feature
or a Scenario, then it returns one representing all the child objects.
.SS "find_scenario_step_by_name"
.IX Subsection "find_scenario_step_by_name"
Given a Scenario and a string, searches through the steps for it and returns
the data-hash where the Step Object's \f(CW\*(C`<\-\*(C'\fRtext>> matches the string.
.SH "AUTHOR"
.IX Header "AUTHOR"
Peter Sergeant \f(CW\*(C`pete@clueball.com\*(C'\fR
.SH "LICENSE"
.IX Header "LICENSE"
.Vb 2
\&  Copyright 2019\-2023, Erik Huelsmann
\&  Copyright 2011\-2019, Peter Sergeant; Licensed under the same terms as Perl
.Ve