Wordpress

History

Pascal Birchler 21e874e00a I18N: Add ability to change user's locale back to site's locale. Previously there was no way to remove the user locale setting again, even though that might be desirable. This adds a new 'Site Default' option to the user-specific language setting by introducing a new `show_site_locale_default` argument to `wp_dropdown_languages()`. Props ocean90. See #29783. Fixes #38632. git-svn-id: https://develop.svn.wordpress.org/trunk@39169 602fd350-edb4-49c9-b593-d223f7449a82		2016-11-08 23:00:38 +00:00
..
data	Posts, Post Types: Fix post type templates with child themes.	2016-11-08 22:40:28 +00:00
includes	Mail: Set a better error code when triggering `wp_mail_failed`.	2016-11-02 04:26:18 +00:00
tests	I18N: Add ability to change user's locale back to site's locale.	2016-11-08 23:00:38 +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.