Wordpress

History

Peter Wilson e73af26e92 Cron API: Return meaningful values from cron functions. Return values added to Cron API functions to indicate outcome: * `wp_schedule_single_event()`, `wp_schedule_event()`, `wp_reschedule_event()` and `wp_unschedule_event()`: boolean indicating success or failure, * `wp_clear_scheduled_hook()`: integer indicating number of jobs cleared (zero or more), `false` if one or more jobs fail to clear, * `wp_unschedule_hook()`: integer indicating number of jobs cleared (zero or more), `false` if the jobs fail to clear, * `spawn_cron()`: boolean indicating whether job spawned, * `wp_cron()`: integer indicating number of jobs spawned (zero or more), `false` if one or more jobs fail to spawned, * `_set_cron_array()`: boolean outcome of `update_option()`. Props evansolomon, jrf, peterwilsoncc, pento for code review. Fixes #21072. git-svn-id: https://develop.svn.wordpress.org/trunk@43050 602fd350-edb4-49c9-b593-d223f7449a82		2018-05-01 02:04:25 +00:00
..
data	Media: Recognize `.ico` files as displayable images on PHP 5.3+ and allow attachment meta data to be generated for them.	2018-03-05 01:02:20 +00:00
includes	Tests: Skip multisite-only or single site-only tests correctly based on test doc annotations.	2018-04-25 22:37:08 +00:00
tests	Cron API: Return meaningful values from cron functions.	2018-05-01 02:04:25 +00:00
build.xml	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00
multisite.xml	Tests: Rename ignored tests in `multisite.xml`.	2017-08-18 10:59:38 +00:00
README.txt	Update tests/README.txt to reflect the new tests directory structure. props jdgrimes. fixes #25133 .	2013-08-31 13:42:56 +00:00
wp-mail-real-test.php	Code is Poetry.	2017-11-30 23:09:33 +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.