5fef526cca
Since [37573], `get_object_term_cache()` has expected term IDs to be stored in the taxonomy relationship cache. The function would then reach directly into the 'terms' cache to fetch the data corresponding to a given term, before returning a `WP_Term` object. This caused problems when, for one reason or another, term data was cached inconsistently: * If the 'terms' cache is empty for a given term ID, despite the earlier call to `_prime_term_caches()`, `get_term()` would return an error object. * If the array of cached term IDs contains an invalid ID, `get_term()` would return an error object. We avoid these errors by no longer touching the 'terms' cache directly, but running term IDs through `get_term()` and allowing that function to reference the cache (and database, as needed). If `get_term()` returns an error object for any of the cached term IDs, `get_object_term_cache()` will return that error object alone. This change ensures that upstream functions, like `get_the_terms()`, return `WP_Error` objects in a predictable fashion. Props dd32, michalzuber. Fixes #37291. git-svn-id: https://develop.svn.wordpress.org/trunk@38776 602fd350-edb4-49c9-b593-d223f7449a82 |
||
|---|---|---|
| .. | ||
| data | ||
| includes | ||
| tests | ||
| README.txt | ||
| build.xml | ||
| multisite.xml | ||
| 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.