Wordpress

History

Boone Gorges a82fe2b598 Restore support for taxonomy 'args' override when querying object terms. [7520] introduced an undocumented feature whereby developers could register a custom taxonomy with an 'args' parameter, consisting of an array of config params that, when present, override corresponding params in the `$args` array passed to `wp_get_object_terms()` when using that function to query for terms in the specified taxonomy. The `wp_get_object_terms()` refactor in [38667] failed to respect this secret covenant, and the current changeset atones for the transgression. Ports [40513] to the 4.7 branch. Props danielbachhuber. Fixes #40496. git-svn-id: https://develop.svn.wordpress.org/branches/4.7@40514 602fd350-edb4-49c9-b593-d223f7449a82		2017-04-21 19:18:00 +00:00
..
data	Build/Test Tools: Call `wp_head()` and `wp_footer()` in the theme used during tests.	2017-03-07 01:34:43 +00:00
includes	Build/Test Tools: Add assertNotFalse() method to WP_UnitTestCase and use it where appropriate.	2017-04-06 18:19:02 +00:00
tests	Restore support for taxonomy 'args' override when querying object terms.	2017-04-21 19:18:00 +00:00
README.txt	…
build.xml	…
multisite.xml	oEmbed: Remove the oEmbed provider unit tests.	2016-10-20 09:15:10 +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.