Wordpress

History

John Blackbourn f257bdfbb2 Pings/Trackbacks: Remove a failing test that won't pass as long as `WP_IMPORTING` gets set during tests. The `_publish_post_hook()` function checks for `WP_IMPORTING` before setting meta fields fir enclosures and pings, which means this test is doomed to fail. The test can be re-implemented if the `WP_IMPORTING` constant gets moved to a function similar to how `wp_installing()` works for the `WP_INSTALLING` constant. See #48014 git-svn-id: https://develop.svn.wordpress.org/trunk@46428 602fd350-edb4-49c9-b593-d223f7449a82		2019-10-07 22:17:22 +00:00
..
data	Themes: Add a test to ensure `get_template_part()` does not return a value.	2019-09-26 20:25:59 +00:00
includes	Coding Standards: Fix WPCS issue in [46262].	2019-09-23 19:28:43 +00:00
tests	Pings/Trackbacks: Remove a failing test that won't pass as long as `WP_IMPORTING` gets set during tests.	2019-10-07 22:17:22 +00:00
build.xml	Coding Standards: Replace spaced indentation sections of `phpunit.xml.dist`, `multisite.xml`, and `build.xml` with tabs.	2019-01-28 17:20:06 +00:00
multisite.xml	Code Modernization: Remove all code using a `version_compare()` with a PHP version older than PHP 5.6.	2019-09-20 22:01:36 +00:00
README.txt
wp-mail-real-test.php	Coding Standards: Fix the remaining issues in `/tests`.	2019-07-08 00:55:20 +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.