pherkin - Execute tests written using Test::BDD::Cucumber
version 0.34
pherkin pherkin some/path/features/
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.
pherkin
./features/
*.feature
*_steps.pl
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.
Controlling @INC
-l, --lib Add 'lib' to @INC -b, --blib Add 'blib/lib' and 'blib/arch' to @INC -I [dir] Add given directory to @INC
Output formatting
-o, --output Output harness to use. Default to 'TermColor'. See 'Outputs' -c, --theme Colour theme for 'TermColor'. `light` or `dark`. Defaults to `dark`
Tag specifications
-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'
Help
-h, --help Print usage information. --i18n LANG List keywords for a particular language. '--i18n help' lists all languages available.
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:
Test::BDD::Cucumber::Harness
pherkin -o TermColor some/path/feature # The default pherkin -o TestBuilder some/path/feature # Test::Builder-type text output
Peter Sergeant pete@clueball.com
pete@clueball.com
Copyright 2012-2014, Peter Sergeant; Licensed under the same terms as Perl
To install Test::BDD::Cucumber, copy and paste the appropriate command in to your terminal.
cpanm
cpanm Test::BDD::Cucumber
CPAN shell
perl -MCPAN -e shell install Test::BDD::Cucumber
For more information on module installation, please visit the detailed CPAN module installation guide.