Wordpress

History

Boone Gorges ed4eee668e Don't cache `WP_Term` objects in `wp_get_object_cache()`. The data stored in the cache should be raw database query results, not `WP_Term` objects (which may be modified by plugins, and may contain additional properties that shouldn't be cached). If term relationships caches were handled in `wp_get_object_terms()` - where a database query takes place - it would be straightforward to cache raw data. See #34239. Since, in fact, `get_the_terms()` caches the value it gets from `wp_get_object_terms()`, we need a technique that allows us to get raw data from a `WP_Term` object. Mirroring `WP_User`, we introduce a `data` property on term objects, which `get_the_terms()` uses to fetch cacheable term info. Fixes #34262. git-svn-id: https://develop.svn.wordpress.org/trunk@35032 602fd350-edb4-49c9-b593-d223f7449a82		2015-10-12 15:12:29 +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	REST API: Introduce baby API to the world.	2015-10-08 02:30:18 +00:00
tests	Don't cache `WP_Term` objects in `wp_get_object_cache()`.	2015-10-12 15:12:29 +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	…

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.