# Testing

Wolff comes with unit testing in mind, that's why it's extremely easy to test it out of the box.

The tests use PHPUnit, so you must have it installed for running them.

Running tests

Open your terminal, move to your Wolff project folder and run the following command with high privileges:


High privileges is usually refered as sudo in most systems (sudo vendor/bin/phpunit).

Running the command with high privileges is required since some files will be created during the testing process.

Database tests

The database tests are optional, for enabling them just add the -db flag to the phpunit command, it should looks like this:

vendor/bin/phpunit -db

The credentials for the database tests can be defined in the phpunit.xml file, inside the phpunit tags.

Keep in mind that the database used for the tests will be dropped before and after the tests, do NOT use a database with any type of data (sensible or not) for the tests.

This is an example:

    <const name="DBMS" value="mysql"/>
    <const name="SERVER" value="localhost"/>
    <const name="DB" value="wolff_test"/>
    <const name="USERNAME" value="root"/>
    <const name="PASSWORD" value="12345"/>

Test coverage

Yes, assigning a specific number or percentage to a test coverage is quite ambiguous. So take the following number with a grain of salt.

Wolff tests cover more or less the ~85% of all the framework.

Untested elements

The following elements of Wolff are not present in the tests (due to its nature):

  • Authentication

Not fully covered elements

The following elements are available in the tests but are not 100% covered:

  • Database (optional)
  • Session
  • Request
  • Response

Keep in mind that if a element is not present in the lists showed above, it means that it's present and fully covered in the tests.

Documentation made with
Something is wrong in here? Make a issue/pull request on the repo.