Test::BDD::Cucumber::Harness::Data - Builds up an internal data representation of test passes / failures

features
       An array-ref in which we store all the features executed, and completed. Until "feature_done" is called,
       it won't be in here.

   current_featurecurrent_scenariocurrent_step
       The current feature/step/scenario for which we've had the starting method, but not the "_done" method.

   featurefeature_done
       Feature hashref looks like:

        {
               object    => Test::BDD::Cucumber::Model::Feature object
               scenarios => []
        }

   scenarioscenario_done
       Scenario hashref looks like:

        {
               object  => Test::BDD::Cucumber::Model::Scenario object
               dataset => Data hash the scenario was invoked with
               steps   => [],
        }

   stepstep_done
       Step hashref looks like:

        {
               context => Test::BDD::Cucumber::StepContext object
               result  => Test::BDD::Cucumber::Model::Result object (after step_done)
        }

   feature_statusscenario_statusstep_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.

   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 "<-"text>> matches the string.

       Peter Sergeant "pete@clueball.com"

       A Test::BDD::Cucumber::Harness subclass which collates test data

         Copyright 2019-2023, Erik Huelsmann
         Copyright 2011-2019, Peter Sergeant; Licensed under the same terms as Perl

perl v5.40.1                                       2025-05-29             Test::BDD::Cucu...::Harness::Data(3pm)

       Test::BDD::Cucumber::Harness::Data - Builds up an internal data representation of test passes / failures

       version 0.87