Update other docs

Author: exodist

lib/Test2/API/InterceptResult.pm

@@ -186,7 +186,7 @@ needing a deep understanding of the event/facet model.
 Usually you get an instance of this class when you use C<intercept()> from
 L<Test2::API>.
 
-    use Test2::V0;
+    use Test2::V1 '-iPp';
     use Test2::API qw/intercept/;
 
     my $events = intercept {

lib/Test2/API/InterceptResult/Event.pm

@@ -507,7 +507,7 @@ you to use when testing your test tools.
 
 =head1 SYNOPSIS
 
-    use Test2::V0;
+    use Test2::V1 '-iPp';
     use Test2::API qw/intercept/;
 
     my $events = intercept {

lib/Test2/Bundle/Extended.pm

@@ -33,6 +33,8 @@ Test2::Bundle::Extended - Old name for Test2::V0
 This bundle has been renamed to L<Test2::V0>, in which the C<':v1'> tag has
 been removed as unnecessary.
 
+B<Note:> L<Test2::V1> is the latest bundle, you probably want to look at that.
+
 =head1 DESCRIPTION
 
 This is the big-daddy bundle. This bundle includes nearly every tool, and

lib/Test2/Manual/Testing.pm

@@ -39,7 +39,7 @@ lexically scoped, or they may be global.
 =item Test2::Bundle::*
 
 Bundles combine toolsets and plugins together to reduce your boilerplate. First
-time test writers are encouraged to start with the L<Test2::V0> bundle (which
+time test writers are encouraged to start with the L<Test2::V1> bundle (which
 is an exception to the namespace rule as it does not live under
 C<Test2::Bundle::>). If you find yourself loading several plugins and toolsets
 over and over again you could benefit from writing your own bundle.
@@ -69,47 +69,47 @@ and define new ones, typically with a new bundle. In short, if we feel the need
 to break something we will do so by creating a new bundle, and discouraging the
 old one, but we will not break the old one.
 
-So for example, if you use L<Test2::V0>, and L<Dist::Zilla> you
+So for example, if you use L<Test2::V1>, and L<Dist::Zilla> you
 should have this in your config:
 
     [Prereqs / TestRequires]
-    Test2::V0 = 0.000060
+    Test2::V1 = 0.000060
 
 You B<SHOULD NOT> do this:
 
     [Prereqs / TestRequires]
     Test2::Suite = 0.000060
 
-Because L<Test2::V0> might not always be part of L<Test2::Suite>.
+Because L<Test2::V1> might not always be part of L<Test2::Suite>.
 
 When writing new tests you should often check L<Test2::Suite> to see what the
 current recommended bundle is.
 
 =head3 Dist::Zilla
 
     [Prereqs / TestRequires]
-    Test2::V0 = 0.000060
+    Test2::V1 = 0.000060
 
 =head3 ExtUtils::MakeMaker
 
     my %WriteMakefileArgs = (
       ...,
       "TEST_REQUIRES" => {
-        "Test2::V0" => "0.000060"
+        "Test2::V1" => "0.000060"
       },
       ...
     );
 
 =head3 Module::Install
 
-    test_requires 'Test2::V0' => '0.000060';
+    test_requires 'Test2::V1' => '0.000060';
 
 =head3 Module::Build
 
     my $build = Module::Build->new(
         ...,
         test_requires => {
-            "Test2::V0" => "0.000060",
+            "Test2::V1" => "0.000060",
         },
         ...
     );

lib/Test2/Manual/Testing/Introduction.pm

@@ -26,7 +26,7 @@ C<.t> file extension.
 
 C<t/example.t>:
 
-    use Test2::V0;
+    use Test2::V1 -ipP;
 
     # Assertions will go here
 
@@ -36,10 +36,26 @@ This is all the boilerplate you need.
 
 =over 4
 
-=item use Test2::V0;
+=item use Test2::V1 -ipP;
 
 This loads a collection of testing tools that will be described later in the
-tutorial. This will also turn on C<strict> and C<warnings> for you.
+tutorial. See L<Test2::V1> for more details, but for starters '-ipP' is a good
+set of import flags.
+
+If you do not like importing a ton of symbols or enabling pragmas/plugins all
+in one swoop you can do C<< use Test2::V1; >>. If you do this you will need to
+use the T2() function to access tools, and load any pragmas/plugins manually:
+
+    use Test2::V1;
+    use strict;
+    use warnings;
+    use Test2::Plugin::UTF8;
+    use Test2::Plugin::SRand;
+
+    T2->ok(1, "pass");
+    T2->is(5, 5, "5 is 5");
+
+    T2->done_testing;
 
 =item done_testing;
 
@@ -59,28 +75,28 @@ L<Test2::Suite> to their own dists at any time.
 =head3 Dist::Zilla
 
     [Prereqs / TestRequires]
-    Test2::V0 = 0.000060
+    Test2::V1 = 0.000060
 
 =head3 ExtUtils::MakeMaker
 
     my %WriteMakefileArgs = (
       ...,
       "TEST_REQUIRES" => {
-        "Test2::V0" => "0.000060"
+        "Test2::V1" => "0.000060"
       },
       ...
     );
 
 =head3 Module::Install
 
-    test_requires 'Test2::V0' => '0.000060';
+    test_requires 'Test2::V1' => '0.000060';
 
 =head3 Module::Build
 
     my $build = Module::Build->new(
         ...,
         test_requires => {
-            "Test2::V0" => "0.000060",
+            "Test2::V1" => "0.000060",
         },
         ...
     );
@@ -94,12 +110,20 @@ that a condition is true.
 
 Here is a complete C<t/example.t>:
 
-    use Test2::V0;
+    use Test2::V1 -import;
 
     ok(1, "1 is true, so this will pass");
 
     done_testing;
 
+If you are doing it without imports:
+
+    use Test2::V1;
+
+    T2->ok(1, "1 is true, so this will pass");
+
+    T2->done_testing;
+
 =head1 RUNNING THE TEST
 
 Test files are simply scripts. Just like any other script you can run the test
@@ -204,13 +228,17 @@ There are 2 primary ways to set the plan:
 
 =item done_testing()
 
+=item T2->done_testing()
+
 The most common, and recommended way to set a plan is to add C<done_testing> at
 the end of your test file. This will automatically calculate the plan for you
 at the end of the test. If the test were to exit early then C<done_testing>
 would not run and no plan would be found, forcing a failure.
 
 =item plan($COUNT)
 
+=item T2->plan($COUNT)
+
 The C<plan()> function allows you to specify an exact number of assertions you
 want to run. If you run too many or too few assertions then the plan will not
 match and it will be counted as a failure. The primary problem with this way of
@@ -224,13 +252,15 @@ cannot be done in the middle of making assertions.
 
 =head1 ADDITIONAL ASSERTION TOOLS
 
-The L<Test2::V0> bundle provides a lot more than C<ok()>,
+The L<Test2::V1> bundle provides a lot more than C<ok()>,
 C<plan()>, and C<done_testing()>. The biggest tools to note are:
 
 =over 4
 
 =item is($a, $b, $description)
 
+=item T2->is($a, $b, $description)
+
 C<is()> allows you to compare 2 structures and insure they are identical. You
 can use it for simple string comparisons, or even deep data structure
 comparisons.
@@ -241,6 +271,8 @@ comparisons.
 
 =item like($a, $b, $description)
 
+=item T2->like($a, $b, $description)
+
 C<like()> is similar to C<is()> except that it only checks items listed on the
 right, it ignores any extra values found on the left.