pherkin(1p) [debian man page]

PHERKIN(1p)						User Contributed Perl Documentation					       PHERKIN(1p)

NAME

       pherkin - Execute tests written using Test::BDD::Cucumber

VERSION

       version 0.11

SYNOPSIS

	pherkin
	pherkin some/path/features/

DESCRIPTION

       "pherkin" accepts a single argument of a directory name, defaulting to "./features/" if none is specified. This directory is searched for
       feature files (any file matching "*.feature") and step definition files (any file matching "*_steps.pl"). The step definitions are loaded,
       and then the features executed.

       Steps that pass are printed in green, those that fail in red, and those for which there is no step definition - or that are skipped as the
       result of a previous failure - as yellow.

       "pherkin" will exit with a non-zero status if (and only if) the overall result is considered to be failing.

AUTHOR

       Peter Sergeant "pete@clueball.com"

LICENSE

       Copyright 2012, Peter Sergeant; Licensed under the same terms as Perl

perl v5.14.2							    2012-05-20							       PHERKIN(1p)

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)