WordPress Unit Tests
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
data
includes
tests
wordpress @ a7f7fcd
.gitignore
.gitmodules
README.rst
build.xml
multisite.xml
phpunit.xml
wp-mail-real-test.php
wp-tests-config-sample.php

README.rst

WordPress Unit Tests

The short version:

  1. Initialize the WordPress submodule:

    $ git submodule update --init

  2. Create a clean MySQL database and user. DO NOT USE AN EXISTING DATABASE or you will lose data, guaranteed.

  3. Copy wp-tests-config-sample.php to wp-tests-config.php, edit it and include your database name, user and password.

  4. Run the tests:

    To execute a particular test:

    $ phpunit tests/test_case.php

    To execute all tests:

    $ phpunit

Notes:

Test cases live in the 'tests' subdirectory. All files in that directory will be included by default. Extend the WP_UnitTestCase class to ensure your test is run.

phpunit will initialize and install a (more or less) complete running copy of WordPress each time it is run. This makes it possible to run functional interface and module tests against a fully working database and codebase, as opposed to pure unit tests with mock objects and stubs. Pure unit tests may be used also, of course.

Changes to the test database will be rolled back as tests are finished, to ensure a clean start next time the tests are run.

phpunit is intended to run at the command line, not via a web server.