Wordpress

History

Boone Gorges 56c82e534f Avoid redundant table joins in WP_Tax_Query. IN clauses that are connected by OR require only a single table join. To avoid extraneous joins, keep track of generated table aliases, and let sibling clauses piggy-back on those aliases when possible. Introduces WP_Tax_Query::sanitize_relation() to reduce some repeated code. Adds unit tests to verify the JOIN consolidation, and integration tests for cases where JOINS are being combined. Props boonebgorges, otto42, jakub.tyrcha. Fixes #18105. git-svn-id: https://develop.svn.wordpress.org/trunk@29902 602fd350-edb4-49c9-b593-d223f7449a82		2014-10-15 16:39:19 +00:00
..
data	Tests: Add a placeholder file to the broken-theme directory so it isn't removed when synced to git.	2014-01-06 18:26:07 +00:00
includes	Only reset taxonomies and post types between tests when running core tests.	2014-10-10 20:25:39 +00:00
tests	Avoid redundant table joins in WP_Tax_Query.	2014-10-15 16:39:19 +00:00
build.xml
multisite.xml	Use correct paths in multisite.xml. see [25165]. see #25088 .	2013-09-07 15:19:56 +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.