Wordpress/tests
2013-08-29 16:23:30 +00:00
..
data WP_HTTP: Cookies: When following redirects, include the request cookies in the redirected requests. Fixes #24987 2013-08-17 01:19:04 +00:00
includes Unit Tests: Make it more compatible with PHPUnit when installed as a Phar, or, Composer package, by removing a duplicate require (Phpunit already includes the file itself). Props scribu Fixes #25065 2013-08-28 01:43:14 +00:00
tests Improve the include / exclude SQL generation in get_terms() by using IN and NOT IN where applicable. Adds unit tests for include / exclude. 2013-08-29 16:23:30 +00:00
build.xml Initial import of unit-tests repository into develop.svn.wordpress.org. 2013-08-07 06:38:38 +00:00
multisite.xml Initial import of unit-tests repository into develop.svn.wordpress.org. 2013-08-07 06:38:38 +00:00
phpunit.xml.dist Initial import of unit-tests repository into develop.svn.wordpress.org. 2013-08-07 06:38:38 +00:00
README.txt Update the directory reference in tests/README.txt. props jdgrimes. fixes #25133. 2013-08-24 14:05:00 +00:00
wp-mail-real-test.php Initial import of unit-tests repository into develop.svn.wordpress.org. 2013-08-07 06:38:38 +00:00
wp-tests-config-sample.php Initial import of unit-tests repository into develop.svn.wordpress.org. 2013-08-07 06:38:38 +00:00

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/tests" 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.