test::bdd::cucumber(3pm) [debian man page]

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

NAME

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

VERSION

       version 0.11

DESCRIPTION

       A sane and complete Cucumber implementation in Perl

QUICK LINKS

       Cucumber on Perl on MetaCPAN <https://metacpan.org/release/Test-BDD-Cucumber>

WARNING

       This is beta software, at best. The interface is unlikely to undergo major incompatible changes, but it's certainly possible. Do have a
       read of the Bugs and Missing section below so you're not surprised when these things don't work.

       In almost all cases, where the behaviour of this module is different from the real Cucumber, the plan is to move it to be more similar to
       that.

       The idea is that the first 1.0 release will be the first production release and before that, you're on your own. There are many things
       still to add, but I'm using it to do Real Things already.

NEXT STEPS

       If you are completely new to Cucumber, you'd get a pretty overview from reading our short and crunchy Tutorial.

       If you already understand Cucumber, and just want to get started then you should read the Step-writing quick-start guide, the documentation
       for our command-line tool App::pherkin, and How to integrate with Test::Builder.

       If you want to extend or integrated Test::BDD::Cucumber then you'd probably be more interested in our Architecture overview.

TEN SECOND GUIDE TO USING THIS IN YOUR CI ENVIRONMENT

       Don't use the command-line tool, App::pherkin. Instead, look at the How to integrate with Test::Builder document.

BUGS, MISSING, AND LIMITATIONS
       The following things do not work in this release, although support is planned in the very near future:

       o   Localization

       o   Step Argument Transforms

       o   Quoting in tables is broken

       o   Placeholders in pystrings is broken

       o   Explicit Step Outline notation doesn't work (although step outlines are explicitly supported)

       o   Unicode support is probably a bit ropey

       o   Pherkin isn't really fit for purpose yet

CODE

       On Github, of course: https://github.com/sheriff/test-bdd-cucumber-perl <https://github.com/sheriff/test-bdd-cucumber-perl>.

AUTHOR

       Peter Sergeant "pete@clueball.com"

LICENSE

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

perl v5.14.2							    2012-05-20						  Test::BDD::Cucumber(3pm)

Test::Builder::Module(3pm)				User Contributed Perl Documentation				Test::Builder::Module(3pm)

NAME

       Test::Builder::Module - Base class for test modules

SYNOPSIS

	 # Emulates Test::Simple
	 package Your::Module;

	 my $CLASS = __PACKAGE__;

	 use base 'Test::Builder::Module';
	 @EXPORT = qw(ok);

	 sub ok ($;$) {
	     my $tb = $CLASS->builder;
	     return $tb->ok(@_);
	 }

	 1;

DESCRIPTION

       This is a superclass for Test::Builder-based modules.  It provides a handful of common functionality and a method of getting at the
       underlying Test::Builder object.

   Importing
       Test::Builder::Module is a subclass of Exporter which means your module is also a subclass of Exporter.	@EXPORT, @EXPORT_OK, etc...  all
       act normally.

       A few methods are provided to do the "use Your::Module tests =" 23> part for you.

       import

       Test::Builder::Module provides an import() method which acts in the same basic way as Test::More's, setting the plan and controlling
       exporting of functions and variables.  This allows your module to set the plan independent of Test::More.

       All arguments passed to import() are passed onto "Your::Module->builder->plan()" with the exception of "import =>[qw(things to import)]".

	   use Your::Module import => [qw(this that)], tests => 23;

       says to import the functions this() and that() as well as set the plan to be 23 tests.

       import() also sets the exported_to() attribute of your builder to be the caller of the import() function.

       Additional behaviors can be added to your import() method by overriding import_extra().

       import_extra

	   Your::Module->import_extra(@import_args);

       import_extra() is called by import().  It provides an opportunity for you to add behaviors to your module based on its import list.

       Any extra arguments which shouldn't be passed on to plan() should be stripped off by this method.

       See Test::More for an example of its use.

       NOTE This mechanism is VERY ALPHA AND LIKELY TO CHANGE as it feels like a bit of an ugly hack in its current form.

   Builder
       Test::Builder::Module provides some methods of getting at the underlying Test::Builder object.

       builder

	 my $builder = Your::Class->builder;

       This method returns the Test::Builder object associated with Your::Class.  It is not a constructor so you can call it as often as you like.

       This is the preferred way to get the Test::Builder object.  You should not get it via "Test::Builder->new" as was previously recommended.

       The object returned by builder() may change at runtime so you should call builder() inside each function rather than store it in a global.

	 sub ok {
	     my $builder = Your::Class->builder;

	     return $builder->ok(@_);
	 }

perl v5.10.1							    2011-02-23						Test::Builder::Module(3pm)