Wordpress

History

Boone Gorges bf62165353 Remove caching for `get_term_by()` calls. The new cache group scheme causes term invalidation to be overly broad, so that busting the cache for one term will bust the cache for all terms in the taxonomy. We'll have another go at more focused use of the 'last_changed' incrementor in a future release. Reverts [29915], [30073], [30080], [30108], [30112]. See #21760. git-svn-id: https://develop.svn.wordpress.org/trunk@30900 602fd350-edb4-49c9-b593-d223f7449a82		2014-12-16 13:26:19 +00:00
..
data	Repair the `seems_utf8()` tests that use Big5 encoding.	2014-11-22 20:56:23 +00:00
includes	Add tests which ensure the `wp_editor_set_quality` and `jpeg_quality` filters only apply if they are added before the corresponding `WP_Image_Editor` is instantiated.	2014-12-15 21:24:21 +00:00
tests	Remove caching for `get_term_by()` calls.	2014-12-16 13:26:19 +00:00
build.xml	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00
multisite.xml	Move tests for ms_files_rewriting to separate group, ms-files	2014-11-08 21:07:05 +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
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.