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

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

NAME

       Test::BDD::Cucumber::Model::TagSpec - Encapsulates tag selectors

VERSION

       version 0.11

DESCRIPTION

       Try and deal with the crazy-sauce tagging mechanism in a sane way.

OVERVIEW

       Cucumber tags are all sortsa crazy. This appears to be a direct result of trying to shoe-horn the syntax in to something you can use on the
       command line. Because 'Cucumber' is the name of a gem, application, language, methodology etc etc etc look of disapproval.

       Here is some further reading on how it's meant to work: <https://github.com/cucumber/cucumber/wiki/Tags>. This is obviously a little
       insane.

       Here's how they work here, on a code level: You pass in a list of lists that look like Lisp expressions, with a function: "and", "or", or
       "not". You can nest these to infinite complexity, but the parser is pretty inefficient, so don't do that. The "not" function accepts only
       one argument.

       eg:

       @important AND @billing: "[and =" 'important', 'billing']>

       (@billing OR @WIP) AND @important: "[ and =" [ or => 'billing', 'wip' ], 'important' ]>

       Skipping both @todo and @wip tags: "[ and =" [ not => 'todo' ], [ not => 'wip' ] ]>

ATTRIBUTES

   tags
       An arrayref representing a structure like the above.

	TagSet->new({
	       tags => [ and => 'green', 'blue', [ or => 'red', 'yellow' ], [ not => 'white' ] ]
	})

METHODS

   filter
       Filter a list of Scenarios by the value of "tags"

	my @matched = $tagset->filter( @scenarios );

       If "tags" is empty, no filtering is done.

perl v5.14.2							    2012-05-20				  Test::BDD::Cucumber::Model::TagSpec(3pm)

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

NAME

       Test::BDD::Cucumber::Executor - Run through Feature and Harness objects

VERSION

       version 0.11

DESCRIPTION

       The Executor runs through Features, matching up the Step Lines with Step Definitions, and reporting on progress through the passed-in
       harness.

METHODS

   steps
   add_steps
       The attributes "steps" is a hashref of arrayrefs, storing steps by their Verb.  "add_steps()" takes step definitions of the item list form:

	(
	 [ Given => qr//, sub {} ],
	),

       and populates "steps" with them.

   execute
       Execute accepts a feature object, a harness object, and an optional Test::BDD::Cucumber::TagSpec object and for each scenario in the
       feature which meets the tag requirements (or all of them, if you haven't specified one), runs "execute_scenario".

   execute_scenario
       Accepts a hashref of options, and executes each step in a scenario. Options:

       "feature" - A Test::BDD::Cucumber::Model::Feature object

       "feature_stash" - A hashref that should live the lifetime of feature execution

       "harness" - A Test::BDD::Cucumber::Harness subclass object

       "scenario" - A Test::BDD::Cucumber::Model::Scenario object

       "background_obj" - An optional Test::BDD::Cucumber::Model::Scenario object representing the Background

       "scenario_stash" - We'll create a new scenario stash unless you've posted one in. This is used exclusively for giving Background sections
       access to the same stash as the scenario they're running before.

       For each step, a Test::BDD::Cucumber::StepContext object is created, and passed to "dispatch()". Nothing is returned - everything is played
       back through the Harness interface.

   add_placeholders
       Accepts a text string and a hashref, and replaces " <placeholders" > with the values in the hashref, returning a string.

   dispatch
       Accepts a Test::BDD::Cucumber::StepContext object, and searches through the steps that have been added to the executor object, executing
       against the first matching one.

       You can also pass in a boolean 'short-circuit' flag if the Scenario's remaining steps should be skipped.

   skip_step
       Accepts a step-context, a result-type, and a textual reason, exercises the Harness's step start and step_done methods, and returns a
       skipped-test result.

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::Executor(3pm)