wordpress-develop

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

History

Boone Gorges 408fb37f2b Allow `get_terms()` to fetch terms regardless of taxonomy. `get_terms()` has historically required that a taxonomy be specified when querying terms. This requirement is related to the fact that terms could formerly be shared between taxonomies, making `$taxonomies` critical for disambiguation. Since terms can no longer be shared as of 4.4, it' s desirable to be able to query for terms regardless of what taxonomy they're in. Because it's now optional to pass taxonomies, it's no longer necessary to have `$taxonomies` as the first (and required) parameter for `get_terms()`. The new function signature is `get_terms( $args )`, where 'taxonomy' can (optionally) be passed as part of the `$args` array. This syntax is more consistent with functions like `get_users()` and `get_posts()`. We've maintained backward compatibility by always giving precedence to the old argument format. If a second parameter is detected, or if it's detected that the first parameter is a list of taxonomy names rather than an `$args` array, `get_terms()` will parse the function arguments in the legacy fashion. Props flixos90, swissspidy, DrewAPicture, boonebgorges. Fixes #35495. git-svn-id: https://develop.svn.wordpress.org/trunk@36614 602fd350-edb4-49c9-b593-d223f7449a82		2016-02-22 22:16:37 +00:00
..
data	Tests: Add test for `wp_get_installed_translations()`.	2016-02-17 22:01:11 +00:00
includes	Tests: Add decorators to PHPMailer mock object.	2016-02-20 03:40:49 +00:00
tests	Allow `get_terms()` to fetch terms regardless of taxonomy.	2016-02-22 22:16:37 +00:00
build.xml	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00
multisite.xml	Embeds: Add oEmbed provider support.	2015-10-07 10:35:18 +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.