Wordpress

History

Boone Gorges 36af857315 Don't require explicit taxonomy when getting terms by term_taxonomy_id. Props wonderboymusic. Fixes #30620. git-svn-id: https://develop.svn.wordpress.org/trunk@34679 602fd350-edb4-49c9-b593-d223f7449a82		2015-09-29 03:51:11 +00:00
..
data	Add test image for test_exif_keywords test	2015-09-22 21:42:45 +00:00
includes	WPDB: Make sure we don't run sanity checks on DB dropins.	2015-09-28 01:16:29 +00:00
tests	Don't require explicit taxonomy when getting terms by term_taxonomy_id.	2015-09-29 03:51:11 +00:00
build.xml
multisite.xml	Exclude external HTTP tests from multisite run	2015-09-28 02:36:23 +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

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.