wordpress-develop

mirror of https://github.com/gosticks/wordpress-develop.git synced 2025-10-16 12:05:38 +00:00

History

Boone Gorges 81ecd4da98 Taxonomy: Use `WP_Term_Query` when querying for object terms. The new 'object_ids' parameter for `WP_Term_Query` allows queries for terms that "belong to" a given object. This change makes it possible to use `WP_Term_Query` inside of `wp_get_object_terms()`, rather than assembling a SQL query. The refactor has a couple of benefits: * Less redundancy. * Better consistency in accepted arguments between the term query functions. See #31105. * Less redundancy. * Object term queries are now cached. The `get_object_term_cache()` cache remains, and will be a somewhat less fragile secondary cache in front of the query cache (which is subject to frequent invalidation). * Less redundancy. A small breaking change: Previously, if a non-hierarchical taxonomy had terms that had a non-zero 'parent' (perhaps because of a direct SQL query), `wp_get_object_terms()` would respect the 'parent' argument. This is in contrast to `WP_Term_Query` and `get_terms()`, which have always rejected 'parent' queries for non-hierarchical taxonomies. For consistency, the behavior of `get_terms()` is being applied across the board: passing 'parent' for a non-hierarchical taxonomy will result in an empty result set (since the cached taxonomy hierarchy will be empty). Props flixos90, boonebgorges. See #37198. git-svn-id: https://develop.svn.wordpress.org/trunk@38667 602fd350-edb4-49c9-b593-d223f7449a82		2016-09-28 03:54:36 +00:00
..
data	Themes: Improve child theme file inheritance by introducing functions for locating and fetching the URL or path to files within child and parent themes.	2016-09-08 22:53:57 +00:00
includes	Built/Test Tools: Unify the way the permastructure is set when used in conjunction with re-registering the initial taxonomies. This ensure that rewrite rules for taxonomies are consistently available.	2016-09-26 17:01:48 +00:00
tests	Taxonomy: Use `WP_Term_Query` when querying for object terms.	2016-09-28 03:54:36 +00:00
build.xml	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00
multisite.xml	OEmbed: add unit tests. `@group external-oembed` is not run by default.	2016-08-30 18:54:53 +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	Initialise `$_SERVER['SERVER_NAME']` during the test bootstrap to avoid individual tests having to do it.	2015-10-21 23:51:45 +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.