Wordpress

History

Gary Pendergast 94201ff1f5 Tests: Fix a PHP notice introduced in [38907]. `WP_DEFAULT_THEME` was being defined in the wrong location. Also, if WordPress has the original "default" theme installed, ensure that our test theme overrides it. Props swissspidy for daring to dive into Themes of WordPress Past. See #31550, #38457. git-svn-id: https://develop.svn.wordpress.org/trunk@38908 602fd350-edb4-49c9-b593-d223f7449a82		2016-10-25 11:05:17 +00:00
..
data	Tests: Use a minimal theme for tests.	2016-10-21 11:02:37 +00:00
includes	Tests: Fix a PHP notice introduced in [38907].	2016-10-25 11:05:17 +00:00
tests	Tests: Use a minimal theme for tests.	2016-10-25 10:24:57 +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

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.