Wordpress

History

Weston Ruter e85f291a79 Widgets: Add legacy mode for Text widget and add usage pointers to default visual mode. The Text widget in legacy mode omits TinyMCE and retains old behavior for matching pre-existing Text widgets. Usage pointers added to default visual mode appear when attempting to paste HTML code into the Visual tab and when clicking on the Text tab, informing users of the new Custom HTML widget. Props westonruter, melchoyce, gitlost for testing, obenland for testing, dougal for testing, afercia for testing. See #35243. Fixes #40951. git-svn-id: https://develop.svn.wordpress.org/trunk@41050 602fd350-edb4-49c9-b593-d223f7449a82		2017-07-14 17:08:20 +00:00
..
data	Widgets: Remove image sizes generated during media widget phpunit tests from being version controlled.	2017-05-15 22:58:03 +00:00
includes	Tests: Add `@method` notations to factor class DocBlocks as a way to indicate expected return types from factory methods for the benefit of IDEs.	2017-06-30 04:35:39 +00:00
tests	Widgets: Add legacy mode for Text widget and add usage pointers to default visual mode.	2017-07-14 17:08:20 +00:00
build.xml
multisite.xml	Build/Test Tools: Be strict about tests that do not test anything.	2017-04-23 01:24:41 +00:00
README.txt
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.