Wordpress

History

Andrew Nacin d5d476974e Test framework: Introduce the annotation @expectedDeprecated, modeled after PHPUnit's @expectedException. It works for both functions and arguments (using the value of the first argument passed to _deprecated_function() or _deprecated_argument(), which is typically the function name). It asserts both ways: * If specified, those deprecated notices must be caught, or the test fails. * If not specified, any other deprecated notices cause the test to fail. Works regardless of WP_DEBUG. see #25282. git-svn-id: https://develop.svn.wordpress.org/trunk@25408 602fd350-edb4-49c9-b593-d223f7449a82		2013-09-12 18:37:00 +00:00
..
data	Fix the PHP 5.4 `Only variables should be passed by reference` notices in `tests/action.php`.	2013-09-12 03:53:56 +00:00
includes	Test framework: Introduce the annotation @expectedDeprecated, modeled after PHPUnit's @expectedException.	2013-09-12 18:37:00 +00:00
tests	Revert [25405] and use a file that does exist. see #25282 .	2013-09-12 17:47:40 +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.