Wordpress

History

Boone Gorges 4d17d22a47 Populate term cache with proper clone of term objects. [34999] modified the cache strategy for terms in the context of `wp_get_object_terms()`. As part of these changes, the `object_id` property of term objects had to be unset before being cached. To avoid modifying passed-by- reference terms, `update_term_cache()` attempted to make a copy of the terms passed to the function; however, it failed to use the `clone` keyword, and thus only created a reference instead of a copy. Props berengerzyla. Fixes #35462. git-svn-id: https://develop.svn.wordpress.org/trunk@36323 602fd350-edb4-49c9-b593-d223f7449a82		2016-01-15 19:34:16 +00:00
..
data	Merge the Responsive Images feature plugin into core, initial commit. See: https://github.com/ResponsiveImagesCG/wp-tevko-responsive-images/	2015-10-06 04:58:21 +00:00
includes	Post Types: Introduce `unregister_post_type()`.	2016-01-15 12:19:15 +00:00
tests	Populate term cache with proper clone of term objects.	2016-01-15 19:34:16 +00:00
README.txt	…
build.xml	…
multisite.xml	Embeds: Add oEmbed provider support.	2015-10-07 10:35:18 +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.