NAME

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

VERSION

version 0.18

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.

OPTIONS

 -l, --lib              Add 'lib' to @INC
 -b, --blib             Add 'blib/lib' and 'blib/arch' to @INC
 -I [dir]               Add given directory to @INC
 -o, --output           Output harness to use. Default to 'TermColor'. See 'Outputs'
 -t, --tags @tag        Run scenarios tagged with '@tag'
 -t, --tags @tag1,@tag2 Run scenarios tagged with '@tag1' and '@tag2'
 -t, --tags ~@tag       Run scenarios tagged without '@tag'

OUTPUTS

pherkin can output using any of the Test::BDD::Cucumber::Harness output modules. Test::BDD::Cucumber::TermColor is the default, but Test::BDD::Cucumber::TestBuilder is also a reasonable option:

  pherkin -o TermColor some/path/feature   # The default
  pherkin -o TestBuilder some/path/feature # Test::Builder-type text output

AUTHOR

Peter Sergeant pete@clueball.com

LICENSE

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