Wordpress

History

Weston Ruter f5534ec8d5 Code Editor: Improve ability to create Customizer `CodeEditorControl` instances in JS, lessening PHP dependencies. Allow `CodeEditorControl` to be instantiated with a `editor_settings` param which is merged with `wp.codeEditor.defaultSettings`. Also: * Turn redundant "CSS Code" control label into screen reader text for Additional CSS. * Remove `code-editor` as script dependency for `custom-html-widgets` since enqueueing is determined by `wp_enqueue_code_editor()`. * Remove useless exporting of `code_type` param to JS in `WP_Customize_Code_Editor_Control`. * Add `disabled` class to Custom HTML widget's Save button when linting errors are present. * Remove redundant `span` inside CodeEditorControl's `label`. See #41897, #12423, #41872. git-svn-id: https://develop.svn.wordpress.org/trunk@41957 602fd350-edb4-49c9-b593-d223f7449a82		2017-10-20 16:38:35 +00:00
..
data	Media: Store video creation date in meta.	2017-10-04 19:31:51 +00:00
includes	Build/Test tools: Document the return value of `WP_UnitTestCase::factory()`.	2017-10-19 15:32:07 +00:00
tests	Code Editor: Improve ability to create Customizer `CodeEditorControl` instances in JS, lessening PHP dependencies.	2017-10-20 16:38:35 +00:00
build.xml
multisite.xml	Tests: Rename ignored tests in `multisite.xml`.	2017-08-18 10:59:38 +00:00
README.txt
wp-mail-real-test.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/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.