Wordpress

History

John Blackbourn 3e5005c30c Media: Move the `Tests_Media::test_video_shortcode_body()` method so it runs before other tests in the class that depend on it. The following tests were never executed as they have `@depends` annotations which means they get skipped because the `test_video_shortcode_body()` test has not run by the time they run. Re-ordering the test methods fixes this. * `test_wp_video_shortcode_with_empty_params()` * `test_wp_video_shortcode_with_bad_attr()` * `test_wp_video_shortcode_attributes()` * `test_wp_video_shortcode_youtube_remove_feature()` * `test_wp_video_shortcode_youtube_force_ssl()` * `test_wp_video_shortcode_vimeo_force_ssl_remove_query_args()` * `test_wp_video_shortcode_vimeo_adds_loop()` * `test_wp_video_shortcode_vimeo_force_adds_loop_true()` See #35367 git-svn-id: https://develop.svn.wordpress.org/trunk@41229 602fd350-edb4-49c9-b593-d223f7449a82		2017-08-04 14:05:27 +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: Fully reset MockPHPMailer between tests.	2017-07-29 20:52:45 +00:00
tests	Media: Move the `Tests_Media::test_video_shortcode_body()` method so it runs before other tests in the class that depend on it.	2017-08-04 14:05:27 +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.