Merge pull request #8494 from kenjis/docs-testing/feature.rst

docs: improve testing/feature.rst

Author: kenjis

user_guide_src/source/testing/feature.rst

@@ -29,25 +29,27 @@ Requesting a Page
 Essentially, feature tests simply allows you to call an endpoint on your application and get the results back.
 To do this, you use the ``call()`` method.
 
-1. The first parameter is the HTTP method to use (most frequently either GET or POST).
+1. The first parameter is the HTTP method to use (most frequently either ``GET`` or ``POST``).
 2. The second parameter is the URI path on your site to test.
 3. The third parameter ``$params`` accepts an array that is used to populate the
    superglobal variables for the HTTP verb you are using. So, a method of **GET**
-   would have the **$_GET** variable populated, while a **POST** request would
-   have the **$_POST** array populated. The ``$params`` is also used in
+   would have the ``$_GET`` variable populated, while a **POST** request would
+   have the ``$_POST`` array populated. The ``$params`` is also used in
    :ref:`feature-formatting-the-request`.
 
    .. note:: The ``$params`` array does not make sense for every HTTP verb, but is
       included for consistency.
 
 .. literalinclude:: feature/002.php
+   :lines: 2-
 
 Shorthand Methods
 -----------------
 
 Shorthand methods for each of the HTTP verbs exist to ease typing and make things clearer:
 
 .. literalinclude:: feature/003.php
+   :lines: 2-
 
 Setting Different Routes
 ------------------------
@@ -56,6 +58,7 @@ You can use a custom collection of routes by passing an array of "routes" into t
 override any existing routes in the system:
 
 .. literalinclude:: feature/004.php
+   :lines: 2-
 
 Each of the "routes" is a 3 element array containing the HTTP verb (or "add" for all),
 the URI to match, and the routing destination.
@@ -68,6 +71,7 @@ of key/value pairs that should exist within the ``$_SESSION`` variable when this
 that the current values of ``$_SESSION`` should be used. This is handy for testing authentication and more.
 
 .. literalinclude:: feature/005.php
+   :lines: 2-
 
 Setting Headers
 ---------------
@@ -76,6 +80,7 @@ You can set header values with the ``withHeaders()`` method. This takes an array
 passed as a header into the call:
 
 .. literalinclude:: feature/006.php
+   :lines: 2-
 
 Bypassing Events
 ----------------
@@ -84,6 +89,7 @@ Events are handy to use in your application, but can be problematic during testi
 to send out emails. You can tell the system to skip any event handling with the ``skipEvents()`` method:
 
 .. literalinclude:: feature/007.php
+   :lines: 2-
 
 .. _feature-formatting-the-request:
 
@@ -100,6 +106,7 @@ body of the request in the given format.
 This will also set the `Content-Type` header for your request accordingly.
 
 .. literalinclude:: feature/008.php
+   :lines: 2-
 
 .. _feature-setting-the-body:
 

user_guide_src/source/testing/feature/001.php

@@ -1,11 +1,12 @@
 <?php
 
-namespace App;
+namespace Tests\Feature;
 
+use CodeIgniter\Test\CIUnitTestCase;
 use CodeIgniter\Test\DatabaseTestTrait;
 use CodeIgniter\Test\FeatureTestTrait;
 
-class TestFoo extends CIUnitTestCase
+class FooTest extends CIUnitTestCase
 {
     use DatabaseTestTrait;
     use FeatureTestTrait;