NAME

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

VERSION

version 0.18

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