wordpress-develop

mirror of https://github.com/gosticks/wordpress-develop.git synced 2026-04-02 03:34:33 +00:00

Files

Boone Gorges 642e826cd9 Don't force child_of=0 for non-hierarchical taxonomies in get_terms().

This forcing appears to have been introduced to save unnecessary queries, but
(a) in some cases it appeared to be causing *more* queries, and (b) it caused
incorrect results when the 'exclude_tree' param of `get_terms()` called
`get_terms()` on each item in the tree using the 'child_of' param.

Fixes #30275.

git-svn-id: https://develop.svn.wordpress.org/trunk@30265 602fd350-edb4-49c9-b593-d223f7449a82

2014-11-06 21:46:18 +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

Set current user to 0 after each unit test.

2014-10-24 00:58:35 +00:00

tests

Don't force child_of=0 for non-hierarchical taxonomies in get_terms().

2014-11-06 21:46:18 +00:00

build.xml

Move PHPUnit tests into a tests/phpunit directory.

2013-08-29 18:39:34 +00:00

multisite.xml

Ensure that post types and taxonomies are reset between multisite tests.

2014-10-18 02:31:46 +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

Move PHPUnit tests into a tests/phpunit directory.

2013-08-29 18:39:34 +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.