Wordpress

History

Boone Gorges 5e7be10860 Reset post types and taxonomies before each unit test. Registering a post type or taxonomy during a unit test causes modifications to global variables. If the test fails to clean up these globals - either by neglecting to call _unregister_post_type()/_unregister_taxonomy() at all or by failing before getting a chance to do so - tests that run later in the suite can fail, leading to much gnashing of teeth. Wiping all taxonomies and restoring to the defaults before each test ensures that we always start with a clean slate. Fixes #29827. git-svn-id: https://develop.svn.wordpress.org/trunk@29860 602fd350-edb4-49c9-b593-d223f7449a82		2014-10-09 00:57:26 +00:00
..
data	Tests: Add a placeholder file to the broken-theme directory so it isn't removed when synced to git.	2014-01-06 18:26:07 +00:00
includes	Reset post types and taxonomies before each unit test.	2014-10-09 00:57:26 +00:00
tests	Change assertEqual to assertEqualSets since the order that travis-ci creates posts isn't consistent	2014-10-08 19:21:30 +00:00
build.xml	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00
multisite.xml	Use correct paths in multisite.xml. see [25165]. see #25088 .	2013-09-07 15:19:56 +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	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +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.