Wordpress

History

Weston Ruter 84e475dd80 Customizer: Ensure `WP_Customize_Setting::update()` returns boolean value. Adds unit tests for `WP_Customize_Setting::save()` (and `WP_Customize_Setting::update()`), along with the actions `customize_update_{$type}`, and `customize_save_{$id_base}` which they trigger. Fixes #34140. git-svn-id: https://develop.svn.wordpress.org/trunk@34838 602fd350-edb4-49c9-b593-d223f7449a82		2015-10-05 21:57:32 +00:00
..
data	Shortcodes/Formatting: Add PCRE Performance Testing	2015-10-02 04:25:40 +00:00
includes	Use `wp_installing()` instead of `WP_INSTALLING` constant.	2015-10-05 15:05:26 +00:00
tests	Customizer: Ensure `WP_Customize_Setting::update()` returns boolean value.	2015-10-05 21:57:32 +00:00
README.txt	…
build.xml	…
multisite.xml	Exclude external HTTP tests from multisite run	2015-09-28 02:36:23 +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.