debian man page for test::bdd::cucumber::manual::integration

Query: test::bdd::cucumber::manual::integration

OS: debian

Section: 3pm

Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar

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

NAME
Test::BDD::Cucumber::Manual::Integration - Integrating with Test::Builder
VERSION
version 0.11
DESCRIPTION
How to use Test::BDD::Cucumber in your test suite
OVERVIEW
You may well want your Cucumber tests to be executed as part of your standard test-suite. Luckily, this is SUPER easy. WELL-COMMENTED EXAMPLE #!perl use strict; use warnings; use FindBin::libs; # This will find step definitions and feature files in the directory you point # it at below use Test::BDD::Cucumber::Loader; # This harness prints out nice TAP use Test::BDD::Cucumber::Harness::TestBuilder; # Load a directory with Cucumber files in it. It will recursively execute any # file matching .*_steps.pl as a Step file, and .*.feature as a feature file. # The features are returned in @features, and the executor is created with the # step definitions loaded. my ( $executor, @features ) = Test::BDD::Cucumber::Loader->load( 't/cucumber_core_features/' ); # Create a Harness to execute against. TestBuilder harness prints TAP my $harness = Test::BDD::Cucumber::Harness::TestBuilder->new({}); # For each feature found, execute it, using the Harness to print results $executor->execute( $_, $harness ) for @features; done_testing; perl v5.14.2 2012-05-20 Test::BDD::Cucumber::Manual::Integration(3pm)
Related Man Pages
test::bdd::cucumber::executor(3pm) - debian
test::bdd::cucumber::manual::steps(3pm) - debian
test::bdd::cucumber::model::line(3pm) - debian
test::bdd::cucumber::model::tagspec(3pm) - debian
test::bdd::cucumber::stepfile(3pm) - debian
Similar Topics in the Unix Linux Community
Why cd ./ instead cd only?
Want to show data in tabel format
execute a .jil file
Test existance of a file
Test