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

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

NAME

       Test::BDD::Cucumber::Manual::Architecture - Structural Overview

VERSION

       version 0.11

INTRODUCTION

       This short document exists to give you an idea how the different components of this distribution fit together.

MODELS

       The core of a Cucumber-based test suite are the feature files and the step definitions files. By convention, these are saved under
       "/features/" and "/features/step_definitions/" respectively.

       The feature files are encapsulated by the classes in "Test::BDD::Cucumber::Model".

			 one to one
	TBCM::Feature<----------------->TBCM::Document
	     |				     |
	     +-------------------+	     |
	     | has many 	 | has a     | has many
	     V			 |	     V
	TBCM::Scenario		 +----->TBCM::Line
	     |				  ^  ^
	     +----------------------------+  |
	     | has many 		     |
	     V				     |
	TBCM::Step---------------------------+

EXECUTOR

       We build up a Test::BDD::Executor object, in to which we load the step definitions. We then pass this in a Test::BDD::Model::Feature
       object, along with a Test::BDD::Model::Harness object, which controls interaction with the outside world.

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

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)