Wordpress

History

Ian Dunn fde455a89f External Libraries: Test that MediaElement SWF files remain deleted. The files were removed from Core in r42462 because they're no longer necessary, and have a history of security issues. They remain upstream, though, so this test makes it explicitly clear that they should not be added back in the future without careful consideration and discussion with the Security team. `Tests_Admin_IncludesUpdateCore::test_new_files_are_not_in_old_files_array_compiled()` would already catch files with the exact same name, but this test will also catch files with new names, just to be extra cautious. Props iandunn, ocean90, SergeyBiryukov Fixes 43101 git-svn-id: https://develop.svn.wordpress.org/trunk@42762 602fd350-edb4-49c9-b593-d223f7449a82		2018-02-27 14:37:15 +00:00
..
data	Media: Add `small-audio.flac` for a unit test added in [42451].	2018-01-15 22:32:47 +00:00
includes	Unit Tests: add a DIR_TESTROOT constant to avoid relative paths.	2018-02-25 18:06:49 +00:00
tests	External Libraries: Test that MediaElement SWF files remain deleted.	2018-02-27 14:37:15 +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	Code is Poetry.	2017-11-30 23:09:33 +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.