Skip to content

feature.rst

Latest commit

 

History

History
128 lines (88 loc) · 4.56 KB

feature.rst

File metadata and controls

128 lines (88 loc) · 4.56 KB

HTTP Feature Testing

Feature testing allows you to view the results of a single call to your application. This might be returning the results of a single web form, hitting an API endpoint, and more. This is handy because it allows you to test the entire life-cycle of a single request, ensuring that the routing works, the response is the correct format, analyze the results, and more.

The Test Class

Feature testing requires that all of your test classes use the CodeIgniter\Test\DatabaseTestTrait and CodeIgniter\Test\FeatureTestTrait traits. Since these testing tools rely on proper database staging you must always ensure that parent::setUp() and parent::tearDown() are called if you implement your own methods.

.. literalinclude:: feature/001.php

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 uppercase 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 :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

You can use a custom collection of routes by passing an array of "routes" into the withRoutes() method. This will override any existing routes in the system:

.. literalinclude:: feature/004.php
   :lines: 2-

Each of the "routes" is a 3 element array containing the uppercase HTTP verb (or "add" for all), the URI to match, and the routing destination.

Setting Session Values

You can set custom session values to use during a single test with the withSession() method. This takes an array of key/value pairs that should exist within the $_SESSION variable when this request is made, or null to indicate 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

You can set header values with the withHeaders() method. This takes an array of key/value pairs that would be passed as a header into the call:

.. literalinclude:: feature/006.php
   :lines: 2-

Bypassing Events

Events are handy to use in your application, but can be problematic during testing. Especially events that are used to send out emails. You can tell the system to skip any event handling with the skipEvents() method:

.. literalinclude:: feature/007.php
   :lines: 2-

Formatting the Request

You can set the format of your request's body using the withBodyFormat() method. Currently this supports either json or xml. This is useful when testing JSON or XML APIs so that you can set the request in the form that the controller will expect.

This will take the parameters passed into call(), post(), get()... and assign them to the 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-

Setting the Body

You can set the body of your request with the withBody() method. This allows you to format the body how you want to format it. It is recommended that you use this if you have more complicated XMLs to test.

This will not set the Content-Type header for you. If you need that, you can set it with the withHeaders() method.

Checking the Response

FeatureTestTrait::call() returns an instance of a TestResponse. See :doc:`Testing Responses <response>` on how to use this class to perform additional assertions and verification in your test cases.