Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

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

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)

Check Out this Related Man Page

README(3pm)						User Contributed Perl Documentation					       README(3pm)

NAME

       Test::BDD::Cucumber - Feature-complete Cucumber-style testing in Perl

DESCRIPTION

       A sane and complete Cucumber implementation in Perl

QUICK LINKS

       Cucumber on Perl on MetaCPAN <https://metacpan.org/release/Test-BDD-Cucumber>

WARNING

       This is beta software, at best. The interface is unlikely to undergo major incompatible changes, but it's certainly possible. Do have a
       read of the Bugs and Missing section below so you're not surprised when these things don't work.

       In almost all cases, where the behaviour of this module is different from the real Cucumber, the plan is to move it to be more similar to
       that.

       The idea is that the first 1.0 release will be the first production release and before that, you're on your own. There are many things
       still to add, but I'm using it to do Real Things already.

NEXT STEPS

       If you are completely new to Cucumber, you'd get a pretty overview from reading our short and crunchy Tutorial.

       If you already understand Cucumber, and just want to get started then you should read the Step-writing quick-start guide, the documentation
       for our command-line tool App::pherkin, and How to integrate with Test::Builder.

       If you want to extend or integrated Test::BDD::Cucumber then you'd probably be more interested in our Architecture overview.

TEN SECOND GUIDE TO USING THIS IN YOUR CI ENVIRONMENT

       Don't use the command-line tool, App::pherkin. Instead, look at the How to integrate with Test::Builder document.

BUGS, MISSING, AND LIMITATIONS
       The following things do not work in this release, although support is planned in the very near future:

       o   Localization

       o   Step Argument Transforms

       o   Quoting in tables is broken

       o   Placeholders in pystrings is broken

       o   Explicit Step Outline notation doesn't work (although step outlines are explicitly supported)

       o   Unicode support is probably a bit ropey

       o   Pherkin isn't really fit for purpose yet

CODE

       On Github, of course: https://github.com/sheriff/test-bdd-cucumber-perl <https://github.com/sheriff/test-bdd-cucumber-perl>.

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							       README(3pm)
Man Page