package Test::BDD::Cucumber;

CODE ENDS

=head1 NAME

Test::BDD::Cucumber - Feature-complete Cucumber-style testing in Perl

=head1 SYNOPSIS

Driving tests using the 'pherkin' binary that comes with the distribution

$ pherkin -l -b t/

$ pherkin -l -b --tags @slow t/

$ pherkin -l -b --tags ~@slow

$ pherkin -l -b --strict t/

$ prove --source Feature --ext=.feature examples/

$ prove -r --source Feature -j 9 --ext=.feature t/

=head1 DESCRIPTION

Cucumber for Perl, integrated with L, LTest::More and L.

The implementation supports the following Gherkin keywords in feature files: C, C, C, C, C, C, C, C and C. Additionally, C can be used as a synonym for C (with C). This best maps to L<Gherkin version 6.0.13|https://github.com/cucumber/cucumber/blob/master/gherkin/CHANGELOG.md#6013---2018-09-25>, but without support for its new C and C keywords.

This implementation supports the same languages as Gherkin 15.0.0 - that is, it supports exactly the same translated keywords.

Behaviour of this module is similar to that, but sometimes different from the I Cucumber, the plan is to move use the same parser and behaviour.

=head1 GETTING STARTED

This module comes with a few introductory tutorials.

=over 4

=item * L<A Cucumber feature writing tutorial|Test::BDD::Cucumber::Manual::Tutorial>

for those new to Cucumber and BDD testing

=item * L<A Step writing tutorial|Test::BDD::Cucumber::Manual::Steps>

to get you started writing the code run for each C, C, C step

=item * L<A guide on integrating with your test suite|Test::BDD::Cucumber::Manual::Integration>

=item * L<An architecture overview|Test::BDD::Cucumber::Manual::Architecture>

for those who want to extend or hook into feature file execution

=item * Documentation of the command-line tool LApp::pherkin

=back

=begin html

If you have problems getting started, you can talk to the author(s) here: <img src="https://badges.gitter.im/pjlsergeant/test-bdd-cucumber-perl.svg" alt="Chat on Gitter"

=end html

=head1 BUGS AND LIMITATIONS

One thing need specific mentioning:

=over 4

=item * Due to the use of its own parser, differences probably exist in the interpretation of feature files when comparing to Cucumber.

=back

=head1 PROJECT RESOURCES

=over 4