Wordpress

History

Joe McGill 9848a4a466 Media: Keep PDF previews from overwriting files. Since support for PDF previews were added in [38949], it's possible that the generated image file could overwrite an existing image file with the same name. This uses `wp_unique_filename()` to avoid this issue and adds a '-pdf' identifier on the end of filenames. Props gitlost, derosj, mikeschroder, joemcgill. Fixes #39875. See #31050. git-svn-id: https://develop.svn.wordpress.org/trunk@40130 602fd350-edb4-49c9-b593-d223f7449a82		2017-02-27 15:38:30 +00:00
..
data	Media: Reduce failing uploads following 4.7.1.	2017-02-25 16:07:25 +00:00
includes	REST API: Shim `post_date_gmt` for drafts / empty dates in the REST API.	2017-02-24 18:14:21 +00:00
tests	Media: Keep PDF previews from overwriting files.	2017-02-27 15:38:30 +00:00
build.xml
multisite.xml	oEmbed: Remove the oEmbed provider unit tests.	2016-10-20 09:15:10 +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.