Wordpress

History

Boone Gorges b9e222fd6a Allow `$autoload` setting to be changed for existing options using `update_option()`. [31628] made it possible to pass an `$autoload` param to `update_option()` that applies when the option does not yet exist in the database. The current changeset introduces parity for existing options: the `$autoload` setting for existing options can be changed via the `$autoload` parameter. For internal simplicity, `$autoload` is ignored for existing options when `$value` is not also changed. This changeset also moves `update_option()` tests into their own class. Props dd32. Fixes #26394. git-svn-id: https://develop.svn.wordpress.org/trunk@31640 602fd350-edb4-49c9-b593-d223f7449a82		2015-03-06 13:56:44 +00:00
..
data	Repair the `seems_utf8()` tests that use Big5 encoding.	2014-11-22 20:56:23 +00:00
includes	Ensure that a request URL is always set in `WP_UnitTestCase::go_to()`.	2015-02-23 01:07:18 +00:00
tests	Allow `$autoload` setting to be changed for existing options using `update_option()`.	2015-03-06 13:56:44 +00:00
build.xml
multisite.xml	Move tests for ms_files_rewriting to separate group, ms-files	2014-11-08 21:07:05 +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.