WordPress Unit Tests
PHP JavaScript
Latest commit a2820a7 Jul 19, 2013 root Updating from SVN
Permalink
Failed to load latest commit information.
data Updating from SVN Jul 18, 2013
includes Updating from SVN Jul 18, 2013
tests Updating from SVN Jul 18, 2013
wordpress
.travis.yml Updating from SVN Jul 18, 2013
README.md Updating from SVN Jul 18, 2013
README.txt
build.xml
multisite.xml Updating from SVN Jul 18, 2013
phpunit.xml.dist
wp-mail-real-test.php Updating from SVN Jul 18, 2013
wp-tests-config-sample.php Updating from SVN Jul 18, 2013

README.md

The short version:

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

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

  3. $ svn up

  4. Run the tests from the "trunk" directory: 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.

Build Status