Wordpress

History

Felix Arntz 9d2d5b536d Multisite: Adjust site count of the correct network after having created a new site. Prior to this change, after creating a site, the network site count was always refreshed on the current network, regardless of whether the site was created on a different network. With the recent changes, particularly [40591], it is now possible to update the site count for a specific `$network_id`, so this changeset makes use of the new parameter. Fixes #38699. git-svn-id: https://develop.svn.wordpress.org/trunk@40612 602fd350-edb4-49c9-b593-d223f7449a82		2017-05-10 23:21:43 +00:00
..
data	Build/Test Tools: Call `wp_head()` and `wp_footer()` in the theme used during tests.	2017-03-07 01:33:04 +00:00
includes	REST API: Add `author`, `modified`, and `parent` sort order options for posts.	2017-05-10 18:51:28 +00:00
tests	Multisite: Adjust site count of the correct network after having created a new site.	2017-05-10 23:21:43 +00:00
build.xml
multisite.xml	Build/Test Tools: Be strict about tests that do not test anything.	2017-04-23 01:24:41 +00:00
README.txt
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.