mirror of
https://github.com/gosticks/wordpress-develop.git
synced 2025-10-16 12:05:38 +00:00
3e704473e7
When querying for terms in hierarchical categories using `hide_empty=true`, results have historically included parent terms which are themselves unattached to any objects (are "empty") but which have non-empty descendent terms. Because this process involves walking the descendant tree, we avoid it when we detect that the queried taxonomies are not hierarchical. (This behavior was introduced in [5525].) When the `taxonomy` parameter of `get_terms()` was made optional - see #35495, [36614] - it affected the mechanism for avoiding unneccessary tree walks, since there may not be any explicitly declared taxonomies to run through `is_taxonomy_hierarchical()`. As a result, term queries excluding `taxonomy` did not check descendants, and empty parents with non-empty children were not included in `hide_empty` results. We correct the behavior by crawling term descendants when the `taxonomy` argument is absent, which means that we're querying for terms in all taxonomies. Props smerriman. Fixes #37728. git-svn-id: https://develop.svn.wordpress.org/trunk@45888 602fd350-edb4-49c9-b593-d223f7449a82 |
||
|---|---|---|
| .. | ||
| data | ||
| includes | ||
| tests | ||
| build.xml | ||
| multisite.xml | ||
| README.txt | ||
| wp-mail-real-test.php | ||
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.