Wordpress

History

Dion Hulse af53eecf76 Feeds: Prevent empty feeds from returning 404 errors. Partial revert of [38929]. This reverts the source code from the commit for #30210 to prevent valid but empty feeds from returning 404 file not found errors for the home and custom feeds. The tests in the commit that remain applicable are retained. Props pavelevap for reporting, stevenkword for initial patch, peterwilsoncc. See #30210. Merges [40030] to the 4.7 branch. Fixes #39157. git-svn-id: https://develop.svn.wordpress.org/branches/4.7@40085 602fd350-edb4-49c9-b593-d223f7449a82		2017-02-20 06:37:22 +00:00
..
data	Tests: Replace broken codeispoetry.png file.	2017-01-11 16:27:17 +00:00
includes	REST API: Include the `status` property in `view` context responses from the Posts endpoints.	2017-02-19 04:35:28 +00:00
tests	Feeds: Prevent empty feeds from returning 404 errors.	2017-02-20 06:37:22 +00:00
build.xml
multisite.xml	oEmbed: Remove the oEmbed provider unit tests.	2016-10-20 09:15:10 +00:00
README.txt
wp-mail-real-test.php	Initialise `$_SERVER['SERVER_NAME']` during the test bootstrap to avoid individual tests having to do it.	2015-10-21 23:51:45 +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.