__  __    __   __  _____      _            _          _____ _          _ _ 
 |  \/  |   \ \ / / |  __ \    (_)          | |        / ____| |        | | |
 | \  / |_ __\ V /  | |__) | __ ___   ____ _| |_ ___  | (___ | |__   ___| | |
 | |\/| | '__|> <   |  ___/ '__| \ \ / / _` | __/ _ \  \___ \| '_ \ / _ \ | |
 | |  | | |_ / . \  | |   | |  | |\ V / (_| | ||  __/  ____) | | | |  __/ | |
 |_|  |_|_(_)_/ \_\ |_|   |_|  |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1
 if you need WebShell for Seo everyday contact me on Telegram
 Telegram Address : @jackleet
        
        
For_More_Tools: Telegram: @jackleet | Bulk Smtp support mail sender | Business Mail Collector | Mail Bouncer All Mail | Bulk Office Mail Validator | Html Letter private



Upload:

Command:

[email protected]: ~ $
package Test2::Plugin;
use strict;
use warnings;

our $VERSION = '0.000162';

1;

__END__

=pod

=encoding UTF-8

=head1 NAME

Test2::Plugin - Documentation for plugins

=head1 DESCRIPTION

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.

=head1 FAQ

=over 4

=item 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.

=back

=head1 HOW DO I WRITE A PLUGIN?

Writing a plugin is not as simple as writing an L<Test2::Bundle>, or writing
L<Test2::Tools>. Plugins alter behavior, or cause desirable side-effects. To
accomplish this you typically need a custom C<import()> method that calls one
or more functions provided by the L<Test2::API> package.

If you want to write a plugin you should look at existing plugins, as well as
the L<Test2::API> and L<Test2::Hub> 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.

=head1 SOURCE

The source code repository for Test2-Suite can be found at
F<https://github.com/Test-More/Test2-Suite/>.

=head1 MAINTAINERS

=over 4

=item Chad Granum E<lt>[email protected]<gt>

=back

=head1 AUTHORS

=over 4

=item Chad Granum E<lt>[email protected]<gt>

=back

=head1 COPYRIGHT

Copyright 2018 Chad Granum E<lt>[email protected]<gt>.

This program is free software; you can redistribute it and/or
modify it under the same terms as Perl itself.

See F<http://dev.perl.org/licenses/>

=cut

Filemanager

Name Type Size Permission Actions
API Folder 0755
AsyncSubtest Folder 0755
Bundle Folder 0755
Compare Folder 0755
Event Folder 0755
EventFacet Folder 0755
Formatter Folder 0755
Hub Folder 0755
IPC Folder 0755
Manual Folder 0755
Plugin Folder 0755
Require Folder 0755
Tools Folder 0755
Util Folder 0755
Workflow Folder 0755
API.pm File 48.43 KB 0644
AsyncSubtest.pm File 19.08 KB 0644
Bundle.pm File 1.52 KB 0644
Compare.pm File 11.53 KB 0644
Event.pm File 22.11 KB 0644
EventFacet.pm File 1.46 KB 0644
Formatter.pm File 3.86 KB 0644
Hub.pm File 22.31 KB 0644
IPC.pm File 3.1 KB 0644
Manual.pm File 1.49 KB 0644
Mock.pm File 22.27 KB 0644
Plugin.pm File 1.83 KB 0644
Require.pm File 2.65 KB 0644
Suite.pm File 9.26 KB 0644
Todo.pm File 3.77 KB 0644
Tools.pm File 2.51 KB 0644
Transition.pod File 13.17 KB 0644
Util.pm File 10.33 KB 0644
V0.pm File 11.56 KB 0644
Workflow.pm File 7.13 KB 0644
Filemanager