Wordpress

History

boonebgorges 805021f406 Don't split shared terms on term update. Splitting shared terms means assigning a new term_id to a given term_taxonomy_id. It was uncovered that this change could cause problems for sites that have cached the original term_id somehow - say, in postmeta - since future lookups using that term_id will now fail. Removing for 4.1-beta1. We'll look at improvements to backward compatibility to try to get this back into a later beta. Props mboynes. See #30335. git-svn-id: https://develop.svn.wordpress.org/trunk@30336 602fd350-edb4-49c9-b593-d223f7449a82		2014-11-13 20:04:02 +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	Exclude external-http tests when running `phpunit`.	2014-11-10 14:48:28 +00:00
tests	Don't split shared terms on term update.	2014-11-13 20:04:02 +00:00
build.xml
multisite.xml	Move tests for ms_files_rewriting to separate group, ms-files	2014-11-08 21:07:05 +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.