Wordpress

History

Jeremy Felt d277dd8ef1 Multisite: Introduce `WP_Network_Query`. Provides a consistent way to query `$wpdb->site` for `WP_Network` objects based on domain, path, network ID, and (main) site ID. Introduces and uses update_network_cache() and _prime_network_caches() to maintain a cached list of WP_Network objects for use in multiple queries. Props flixos90. See #32504. git-svn-id: https://develop.svn.wordpress.org/trunk@37894 602fd350-edb4-49c9-b593-d223f7449a82		2016-06-28 21:26:48 +00:00
..
data	I18N: Remove the requirement to call `load_plugin_textdomain()` / `load_theme_textdomain()`.	2016-05-10 20:04:52 +00:00
includes	Allow action and filter hooks to be deprecated.	2016-06-25 19:56:19 +00:00
tests	Multisite: Introduce `WP_Network_Query`.	2016-06-28 21:26:48 +00:00
README.txt	…
build.xml	…
multisite.xml	…
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.