Wordpress

History

Boone Gorges f7dbf962d7 Only reset taxonomies and post types between tests when running core tests. A growing number of plugins and other WP-based projects use the core test tools, such as WP_UnitTestCase, as the basis of their own tests and continuous integration setups. At the same time, many of these third-party plugins use custom post types and taxonomies, which are generally registered a single time during a run of the tests: at 'init', before the testcases have run. Wiping out these globals between tests will mess with these third-party builds. Best practice for plugin developers is probably to clean up their own post types and taxonomies and then reinitialize before each test. But, in the interest of not breaking everyone's builds, the core test suite will not enforce this. Fixes #29827. git-svn-id: https://develop.svn.wordpress.org/trunk@29869 602fd350-edb4-49c9-b593-d223f7449a82		2014-10-10 20:25:39 +00:00
..
data	Tests: Add a placeholder file to the broken-theme directory so it isn't removed when synced to git.	2014-01-06 18:26:07 +00:00
includes	Only reset taxonomies and post types between tests when running core tests.	2014-10-10 20:25:39 +00:00
tests	Return an error when adding a term to a non-existent parent.	2014-10-09 18:11:17 +00:00
README.txt	Update tests/README.txt to reflect the new tests directory structure. props jdgrimes. fixes #25133 .	2013-08-31 13:42:56 +00:00
build.xml	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00
multisite.xml	Use correct paths in multisite.xml. see [25165]. see #25088 .	2013-09-07 15:19:56 +00:00
wp-mail-real-test.php	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00

README.txt

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