Wordpress

History

Boone Gorges 4e3e98698f In `Tests_Ajax_ReplytoComment::test_blocked_comment()`, don't stop blocking comments until test is complete. The test uses the `_block_comments()` method to prevent comment inserts from happening. Since [31263], failed comment inserts lead to the comment content's being stripped of invalid characters and inserted again. By immediately unhooking itself after first being run, `_block_comments()` was causing the INSERT block to work only for the first attempt, while the second attempt was going through, causing the test to fail. As a fix, we move the `remove_filter()` call to the class's `tearDown()` method - sufficient for cleanup, but late enough that all comment inserts will be blocked for the test method in question. See #21212. Since [31263], comment INSERT queries that were pseudo-bl git-svn-id: https://develop.svn.wordpress.org/trunk@31277 602fd350-edb4-49c9-b593-d223f7449a82		2015-01-25 03:38:10 +00:00
..
data	Repair the `seems_utf8()` tests that use Big5 encoding.	2014-11-22 20:56:23 +00:00
includes	Remove non-built-in post statuses during each unit test teardown.	2015-01-04 20:05:53 +00:00
tests	In `Tests_Ajax_ReplytoComment::test_blocked_comment()`, don't stop blocking comments until test is complete.	2015-01-25 03:38:10 +00:00
build.xml	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00
multisite.xml	Move tests for ms_files_rewriting to separate group, ms-files	2014-11-08 21:07:05 +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.