Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

test::bdd::cucumber::stepcontext(3pm) [debian man page]

Test::BDD::Cucumber::StepContext(3pm)			User Contributed Perl Documentation		     Test::BDD::Cucumber::StepContext(3pm)

NAME
Test::BDD::Cucumber::StepContext - Data made available to step definitions VERSION
version 0.11 DESCRIPTION
The coderefs in Step Definitions have a single argument passed to them, a "Test::BDD::Cucumber::StepContext" object. This is an attribute- only class, populated by Test::BDD::Cucumber::Executor. ATTRIBUTES
data Step-specific data. Will either be a text string in the case of a """ string, or an arrayref of hashrefs if the step had an associated table. stash A hash of hashes, containing three keys, "feature", "scenario" and "step". The stash allows you to persist data across features, scenarios, or steps (although the latter is there for completeness, rather than having any useful function). feature scenario step Links to the Test::BDD::Cucumber::Model::Feature, Test::BDD::Cucumber::Model::Scenario, and Test::BDD::Cucumber::Model::Step objects respectively. verb The lower-cased verb a Step Definition was called with. text The text of the step, minus the verb. Placeholders will have already been multiplied out at this point. harness The Test::BDD::Cucumber::Harness harness being used by the executor. matches Any matches caught by the Step Definition's regex. These are also available as $1, $2 etc as appropriate. METHODS
background Boolean for "is this step being run as part of the background section?". Currently implemented by asking the linked Scenario object... AUTHOR
Peter Sergeant "pete@clueball.com" LICENSE
Copyright 2011, Peter Sergeant; Licensed under the same terms as Perl perl v5.14.2 2012-05-20 Test::BDD::Cucumber::StepContext(3pm)

Check Out this Related Man Page

Test::BDD::Cucumber::Harness::Data(3pm) 		User Contributed Perl Documentation		   Test::BDD::Cucumber::Harness::Data(3pm)

NAME
Test::BDD::Cucumber::Harness::Data - Builds up an internal data representation of test passes / failures VERSION
version 0.11 DESCRIPTION
A Test::BDD::Cucumber::Harness subclass which collates test data ATTRIBUTES
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_feature current_scenario current_step The current feature/step/scenario for which we've had the starting method, but not the "_done" method. feature feature_done Feature hashref looks like: { object => Test::BDD::Cucumber::Model::Feature object scenarios => [] } scenario scenario_done Scenario hashref looks like: { object => Test::BDD::Cucumber::Model::Scenario object dataset => Data hash the scenario was invoked with steps => [], } step step_done Step hashref looks like: { context => Test::BDD::Cucumber::StepContext object result => Test::BDD::Cucumber::Model::Result object (after step_done) } feature_status scenario_status 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. 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. AUTHOR
Peter Sergeant "pete@clueball.com" LICENSE
Copyright 2011, Peter Sergeant; Licensed under the same terms as Perl perl v5.14.2 2012-05-20 Test::BDD::Cucumber::Harness::Data(3pm)
Man Page