Wordpress

History

Boone Gorges 5bcee9e939 In `get_terms()`, check hierarchy for all `$taxonomies` before bailing early from 'parent' or 'child_of'. There is a pre-check in `get_terms()` that prevents an unnecessary database query if the 'parent' or 'child_of' parameter is not found in the cached term hierarchy (since a term without an index in the hierarchy cache has no descendants). Previously, only the first item in the `$taxonomies` array was being checked, with the result that an empty array was being erroneously returned in cases where the 'parent' or 'child_of' term is in a subsequent taxonomy. See #31118. git-svn-id: https://develop.svn.wordpress.org/trunk@31276 602fd350-edb4-49c9-b593-d223f7449a82		2015-01-25 02:45:11 +00:00
..
data	Repair the `seems_utf8()` tests that use Big5 encoding.	2014-11-22 20:56:23 +00:00
includes	Remove non-built-in post statuses during each unit test teardown.	2015-01-04 20:05:53 +00:00
tests	In `get_terms()`, check hierarchy for all `$taxonomies` before bailing early from 'parent' or 'child_of'.	2015-01-25 02:45:11 +00:00
build.xml
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

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.