Wordpress

History

Boone Gorges 7c64b3b3dd Introduced `dayofweek_iso` time param for `WP_Date_Query`. The initial `dayofweek` param sets day 1 to Sunday. This is out of step with ISO standards, which calls Monday day 1. To maintain backward compatibility with the existing parameter, we introduce the new `dayofweek_iso` for the new, more compliant param. Props mboynes. Fixes #28063. git-svn-id: https://develop.svn.wordpress.org/trunk@30142 602fd350-edb4-49c9-b593-d223f7449a82		2014-11-01 03:23:15 +00:00
..
data	…
includes	Set current user to 0 after each unit test.	2014-10-24 00:58:35 +00:00
tests	Introduced `dayofweek_iso` time param for `WP_Date_Query`.	2014-11-01 03:23:15 +00:00
README.txt	…
build.xml	…
multisite.xml	Ensure that post types and taxonomies are reset between multisite tests.	2014-10-18 02:31:46 +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.