Wordpress/tests
Ryan Boren 17267dd999 wp_get_shortlink() improvements.
* Return shortlinks for pages and public CPTs.
* Return shortlinks even when cruft-free links are not enabled.
* Unit tests

Props sillybean, layotte, cais
fixes #18632
see #14760



git-svn-id: https://develop.svn.wordpress.org/trunk@25030 602fd350-edb4-49c9-b593-d223f7449a82
2013-08-15 20:08:06 +00:00
..
data Tests: Remove the transitory ticket cache files that shouldn't be under version control. 2013-08-07 10:08:15 +00:00
includes Tests: Avoid PHP Deprecated and Strict Standards warnings from Object references and incompatible method declarations when running under WP_DEBUG 2013-08-08 02:55:44 +00:00
tests wp_get_shortlink() improvements. 2013-08-15 20:08:06 +00:00
build.xml Initial import of unit-tests repository into develop.svn.wordpress.org. 2013-08-07 06:38:38 +00:00
multisite.xml Initial import of unit-tests repository into develop.svn.wordpress.org. 2013-08-07 06:38:38 +00:00
phpunit.xml.dist Initial import of unit-tests repository into develop.svn.wordpress.org. 2013-08-07 06:38:38 +00:00
README.txt Initial import of unit-tests repository into develop.svn.wordpress.org. 2013-08-07 06:38:38 +00:00
wp-mail-real-test.php Initial import of unit-tests repository into develop.svn.wordpress.org. 2013-08-07 06:38:38 +00:00
wp-tests-config-sample.php Initial import of unit-tests repository into develop.svn.wordpress.org. 2013-08-07 06:38:38 +00:00

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.