Wordpress/tests/phpunit
Ryan McCue 9074e9f93b HTTP API: Replace internals with Requests library.
Requests is a library very similar to WP_HTTP, with a high level of unit test coverage, and has a common lineage and development team. It also supports parallel requests.

See #33055.


git-svn-id: https://develop.svn.wordpress.org/trunk@37428 602fd350-edb4-49c9-b593-d223f7449a82
2016-05-13 04:41:45 +00:00
..
data I18N: Remove the requirement to call load_plugin_textdomain() / load_theme_textdomain(). 2016-05-10 20:04:52 +00:00
includes Tests: Set public to 1 in the default blog factory 2016-05-11 19:21:22 +00:00
tests HTTP API: Replace internals with Requests library. 2016-05-13 04:41:45 +00:00
build.xml
multisite.xml Tests: Add speedTrapListener to multisite's PHPUnit config 2016-04-20 17:01:07 +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

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.