Test2::Plugin - Documentation for plugins
Plugins are packages that cause behavior changes, or other side effects for the
test file that loads them. They should not export any functions, or provide any
tools. Plugins should be distinct units of functionality.
If you wish to combine behavior changes with tools then you should write a
Plugin, a Tools module, and a bundle that loads them both.
- Should I subclass Test2::Plugin?
-
No. Currently this class is empty. Eventually we may want to add behavior, in
which case we do not want anyone to already be subclassing it.
Writing a plugin is not as simple as writing an the Test2::Bundle manpage, or writing
the Test2::Tools manpage. Plugins alter behavior, or cause desirable side-effects. To
accomplish this you typically need a custom import() method that calls one
or more functions provided by the the Test2::API manpage package.
If you want to write a plugin you should look at existing plugins, as well as
the the Test2::API manpage and the Test2::Hub manpage documentation. There is no formula for a
Plugin, they are generally unique, however consistent rules are that they
should not load other plugins, or export any functions.
The source code repository for Test2-Suite can be found at
https://github.com/Test-More/Test2-Suite/.
- Chad Granum
-
- Chad Granum <exodist@cpan.org>Chad Granum
-
Copyright 2018 Chad Granum <exodist@cpan.org>.
This program is free software; you can redistribute it and/or
modify it under the same terms as Perl itself.
See http://dev.perl.org/licenses/
|