Chad Granum

I do not recommend using detection. As was already stated it is possible, in fact likely, that many people will use both the Test2 specific tools and some tools still...

Correct. Test2 has some extra compatibility layers thrown in whenever Test::Builder is loaded. A pure Test2 process will be more efficient and slightly faster (measurements may vary).

> @elcamlost If Test2::Mojo is to be thought of as a sort-of Test2 tool (as in Test2::Tools...) then maybe we could change the use line from Test2::V0 to use Test2::Tools::Basic...

Releasing the context is super important, an exception prevents that. Usually test2 can detect it and be less verbose, but sometimes the detection fails. You probably want https://metacpan.org/pod/Test2::API#context_do(&;@) in these...

> I'm a little disappointed that `Test2` is not ready for use in Mojolicious. But a 3rd party module on CPAN is better than nothing. I am not sure what...

Well, if anyone who is interested here wants to suggest it go core, please do, and have my blessing. I will also be willing to answer technical questions that may...

If the goal is to keep the Test2::Mojo namespace for Mojo core, why not go ahead and call the thing Test2::Mojo, then when/if Test2::Suite goes into perl-core the Test2::Mojo package...

that also makes it a seamless transition for anyone using it, they will not later have to go s/Test2::MojoX/Test2::Mojo/ everywhere.

Test2::Tools::Mock, also exported by Test2::V0

I will note that many things probably break from this, so it is a low priority. In my case it is a test for Test2/Test::More that verifies the testing stuff...