Wordpress

History

Gary Pendergast 274bb41c04 Texturize: Only convert `&` to `&` within text nodes. Previously, `&` would be converted everywhere, which caused problems when it was converted within a `<script>`, for example. `convert_chars()` is now removed from the `the_content` filter, as it was doing the same job as `wptexturize()`. KSES correctly handles converting `&` within HTML attributes, so there's no need for `wptexturize()` and `convert_chars()` to do the same job. Fixes #34698. git-svn-id: https://develop.svn.wordpress.org/trunk@35709 602fd350-edb4-49c9-b593-d223f7449a82		2015-11-19 23:31:00 +00:00
..
data	Merge the Responsive Images feature plugin into core, initial commit. See: https://github.com/ResponsiveImagesCG/wp-tevko-responsive-images/	2015-10-06 04:58:21 +00:00
includes	XMLRPC: Revert the changes to `WP_XMLRPC_UnitTestCase` in [35366] as they weren't required.	2015-10-23 04:49:08 +00:00
tests	Texturize: Only convert `&` to `&` within text nodes.	2015-11-19 23:31:00 +00:00
build.xml	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00
multisite.xml	Embeds: Add oEmbed provider support.	2015-10-07 10:35:18 +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	Initialise `$_SERVER['SERVER_NAME']` during the test bootstrap to avoid individual tests having to do it.	2015-10-21 23:51:45 +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.