Wordpress

History

Boone Gorges 13e28a6d34 Prevent Multisite term tests from hitting database for 'db_version'. [34718] introduced a 'db_version' check to term meta functions, to ensure that they don't run when the term meta schema is not yet in place. This call to `get_option()` causes a database hit during Multisite tests, due to the presence of the `WP_INSTALLING` constant. See #31130. The extra database queries are causing cache tests to fail. In similar cases, we have `markTestSkipped()` when `is_multisite()`. Because the term meta API is so extensive - term meta caches can be primed anywhere a `WP_Query` loop is fired up - we implement a more generous workaround in this case. To prevent `get_option( 'db_version' )` from hitting the database during multisite unit tests, we use a 'pre_option_' filter. Heaven help us. See #34091. git-svn-id: https://develop.svn.wordpress.org/trunk@34719 602fd350-edb4-49c9-b593-d223f7449a82		2015-09-30 13:08:49 +00:00
..
data	Add test image for test_exif_keywords test	2015-09-22 21:42:45 +00:00
includes	Prevent Multisite term tests from hitting database for 'db_version'.	2015-09-30 13:08:49 +00:00
tests	Prevent Multisite term tests from hitting database for 'db_version'.	2015-09-30 13:08:49 +00:00
build.xml
multisite.xml	Exclude external HTTP tests from multisite run	2015-09-28 02:36:23 +00:00
README.txt
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.