Wordpress/tests
Sergey Biryukov ac338fc070 Check if a locale category is an existing constant when restoring locale settings in Tests_DB::test_locale_floats(). props nofearinc. fixes #25118.
git-svn-id: https://develop.svn.wordpress.org/trunk@25084 602fd350-edb4-49c9-b593-d223f7449a82
2013-08-22 15:28:01 +00:00
..
data WP_HTTP: Cookies: When following redirects, include the request cookies in the redirected requests. Fixes #24987 2013-08-17 01:19:04 +00:00
includes Adding some basic Unit Tests for the Filesystem methods, primarily, WP_Filesystem_Base::find_folder() which is used during FTP upgrades. 2013-08-20 05:39:20 +00:00
tests Check if a locale category is an existing constant when restoring locale settings in Tests_DB::test_locale_floats(). props nofearinc. fixes #25118. 2013-08-22 15:28:01 +00:00
README.txt
build.xml
multisite.xml
phpunit.xml.dist
wp-mail-real-test.php
wp-tests-config-sample.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/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.