Wordpress

History

Boone Gorges 10d81a3fe5 Introduce 'wp_generate_tag_cloud_data' filter. This filter allows developers to modify the data that is used to create tag clouds, without having to manipulate the tag cloud markup directly. As part of the refactor, this changeset also adds a few unit tests for the way `wp_generate_tag_cloud()` generates the 'title' attribute, as well as improvements to output escaping. Props flixos90, ysalame. Fixes #24656. git-svn-id: https://develop.svn.wordpress.org/trunk@32996 602fd350-edb4-49c9-b593-d223f7449a82		2015-06-29 14:15:59 +00:00
..
data	Add emoji URL support, and Twemoji fallback for displaying slugs in wp-admin, when the browser doesn't natively support emoji.	2015-03-11 22:54:49 +00:00
includes	Deprecate php4 style constructors	2015-06-28 15:26:41 +00:00
tests	Introduce 'wp_generate_tag_cloud_data' filter.	2015-06-29 14:15:59 +00:00
build.xml	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00
multisite.xml	Move tests for ms_files_rewriting to separate group, ms-files	2014-11-08 21:07:05 +00:00
README.txt	Update tests/README.txt to reflect the new tests directory structure. props jdgrimes. fixes #25133 .	2013-08-31 13:42:56 +00:00
wp-mail-real-test.php	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00

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.