Wordpress

History

Peter Wilson 733a81d74d Comments: Check if `wp_new_comment()` returns an error. Adds checks throughout to allow for `wp_new_comment()` returning a `WP_Error` instance. Updates the docs for the `pre_comment_approved` filter to include that it can be passed an error. Props enrico.sorcinelli, ryotsun. Fixes #39730. git-svn-id: https://develop.svn.wordpress.org/trunk@41980 602fd350-edb4-49c9-b593-d223f7449a82		2017-10-23 22:11:11 +00:00
..
data	Themes: Add files missed in [41975].	2017-10-23 20:22:44 +00:00
includes	Build/Test tools: Move `wp_doing_ajax` defintion from class setup to test setup.	2017-10-23 05:10:25 +00:00
tests	Comments: Check if `wp_new_comment()` returns an error.	2017-10-23 22:11:11 +00:00
README.txt	…
build.xml	…
multisite.xml	Tests: Rename ignored tests in `multisite.xml`.	2017-08-18 10:59:38 +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.