REPORT BUGS

The easiest way to help is to report bugs when you find them. Bugs are a fact of life when writing or using software. If you use Test2 long enough you are likely to find a bug. When you find such a bug it would help us out if you would submit a ticket.

BUG TRACKERS

Always try to find the preferred bug tracker for the module that has the bug. Here are the big 3 for the main Test2 project:

Test2/Test-Builder/Test-More

<https://github.com/Test-More/test-more/issues>

Test2-Suite

<https://github.com/Test-More/Test2-Suite/issues>

Test2-Harness

<https://github.com/Test-More/Test2-Harness/issues>

SUBMIT PATCHES

You are welcome to fix bugs you find, or from the tracker. We also often accept patches that add new features or update documentation. The preferred method of submitting patches is a github pull request, that said we also accept patches via email.

ADD/UPDATE DOCUMENTATION

Documentation can be flawed just like code can be. Documentation can also become outdated. If you see some incorrect documentation, or documentation that is missing, we would love to get a patch to fix it!

ANSWER QUESTIONS ON IRC/SLACK

We are always hanging out on <irc://irc.perl.org>, the #perl-qa and #toolchain channels are a good place to find us.

There is also a Test2 slack channel: <https://perl-test2.slack.com>.

WRITE NEW TOOLS USING TEST2

Writing a new tool using Test2 is always a good way to contribute. When you write a tool that you think is useful, it is nice to share it by putting it on CPAN.

PORT OLD TOOLS TO TEST2

The "Test::*" namespace has been around for a long time, and has a LOT of tools. The "Test2::Tools::*" namespace is fairly young, and has less tools. Finding a useful old tool with no modern equivalent, and writing a port is a very good use of your time.