2015-09-28 04:36:23 +02:00
|
|
|
<phpunit
|
|
|
|
bootstrap="includes/bootstrap.php"
|
|
|
|
backupGlobals="false"
|
|
|
|
colors="true"
|
2017-04-23 03:24:41 +02:00
|
|
|
beStrictAboutTestsThatDoNotTestAnything="true"
|
2015-09-28 04:36:23 +02:00
|
|
|
>
|
|
|
|
<php>
|
|
|
|
<const name="WP_TESTS_MULTISITE" value="1" />
|
|
|
|
</php>
|
|
|
|
<testsuites>
|
|
|
|
<!-- Default test suite to run all tests -->
|
REST API: Introduce Autosaves controller and endpoint.
- Adds `WP_REST_Autosaves_Controller` which extends `WP_REST_Revisions_Controller`.
- Autosaves endpoint is registered for all post types except attachment because even post types without revisions enabled are expected to autosave.
- Because setting the `DOING_AUTOSAVE` constant pollutes the test suite, autosaves tests are run last. We may want to improve upon this later.
Also, use a truly impossibly high number in User Controller tests. The number `100`, (or `7777` in `trunk`), could be valid in certain test run configurations. The `REST_TESTS_IMPOSSIBLY_HIGH_NUMBER` constant is impossibly high for this very reason.
Finally, Skip Autosaves controller test for multisite. There's a PHP 5.2 edge case where paths calculated differently, possibly caused by differing version of PHPUnit.
Props adamsilverstein, aduth, azaozz, danielbachhuber, rmccue, danielbachhuber.
Merges [43767], [43768], [43769] to trunk.
See #45132, #45131.
Fixes #45128, #43316.
git-svn-id: https://develop.svn.wordpress.org/trunk@44126 602fd350-edb4-49c9-b593-d223f7449a82
2018-12-13 23:41:47 +01:00
|
|
|
<testsuite name="default">
|
2015-09-28 04:36:23 +02:00
|
|
|
<directory suffix=".php">tests</directory>
|
|
|
|
<exclude>tests/phpunit/tests/actions/closures.php</exclude>
|
|
|
|
<exclude>tests/phpunit/tests/image/editor.php</exclude>
|
2017-08-18 12:59:38 +02:00
|
|
|
<exclude>tests/phpunit/tests/image/editorGd.php</exclude>
|
|
|
|
<exclude>tests/phpunit/tests/image/editorImagick.php</exclude>
|
REST API: Introduce Autosaves controller and endpoint.
- Adds `WP_REST_Autosaves_Controller` which extends `WP_REST_Revisions_Controller`.
- Autosaves endpoint is registered for all post types except attachment because even post types without revisions enabled are expected to autosave.
- Because setting the `DOING_AUTOSAVE` constant pollutes the test suite, autosaves tests are run last. We may want to improve upon this later.
Also, use a truly impossibly high number in User Controller tests. The number `100`, (or `7777` in `trunk`), could be valid in certain test run configurations. The `REST_TESTS_IMPOSSIBLY_HIGH_NUMBER` constant is impossibly high for this very reason.
Finally, Skip Autosaves controller test for multisite. There's a PHP 5.2 edge case where paths calculated differently, possibly caused by differing version of PHPUnit.
Props adamsilverstein, aduth, azaozz, danielbachhuber, rmccue, danielbachhuber.
Merges [43767], [43768], [43769] to trunk.
See #45132, #45131.
Fixes #45128, #43316.
git-svn-id: https://develop.svn.wordpress.org/trunk@44126 602fd350-edb4-49c9-b593-d223f7449a82
2018-12-13 23:41:47 +01:00
|
|
|
<!-- DOING_AUTOSAVE constant pollutes test suite -->
|
|
|
|
<!-- and there is a weird 5.2 edge case: https://core.trac.wordpress.org/ticket/45132 -->
|
|
|
|
<exclude>tests/rest-api/rest-autosaves-controller.php</exclude>
|
|
|
|
<exclude>tests/phpunit/tests/rest-api/rest-autosaves-controller.php</exclude>
|
2015-09-28 04:36:23 +02:00
|
|
|
<file phpVersion="5.3.0">tests/phpunit/tests/actions/closures.php</file>
|
|
|
|
<file phpVersion="5.3.0">tests/phpunit/tests/image/editor.php</file>
|
2017-08-18 12:59:38 +02:00
|
|
|
<file phpVersion="5.3.0">tests/phpunit/tests/image/editorGd.php</file>
|
|
|
|
<file phpVersion="5.3.0">tests/phpunit/tests/image/editorImagick.php</file>
|
2015-09-28 04:36:23 +02:00
|
|
|
</testsuite>
|
|
|
|
</testsuites>
|
|
|
|
<groups>
|
|
|
|
<exclude>
|
|
|
|
<group>ajax</group>
|
|
|
|
<group>ms-files</group>
|
2017-04-22 20:58:46 +02:00
|
|
|
<group>ms-excluded</group>
|
2015-09-28 04:36:23 +02:00
|
|
|
<group>external-http</group>
|
Embeds: Add oEmbed provider support.
For the past 6 years, WordPress has operated as an oEmbed consumer, allowing users to easily embed content from other sites. By adding oEmbed provider support, this allows any oEmbed consumer to embed posts from WordPress sites.
In addition to creating an oEmbed provider, WordPress' oEmbed consumer code has been enhanced to work with any site that provides oEmbed data (as long as it matches some strict security rules), and provides a preview from within the post editor.
For security, embeds appear within a sandboxed iframe - the iframe content is a template that can be styled or replaced entirely by the theme on the provider site.
Props swissspidy, pento, melchoyce, netweb, pfefferle, johnbillion, extendwings, davidbinda, danielbachhuber, SergeyBiryukov, afercia
Fixes #32522.
git-svn-id: https://develop.svn.wordpress.org/trunk@34903 602fd350-edb4-49c9-b593-d223f7449a82
2015-10-07 12:35:18 +02:00
|
|
|
<group>oembed-headers</group>
|
2015-09-28 04:36:23 +02:00
|
|
|
</exclude>
|
|
|
|
</groups>
|
|
|
|
<php>
|
|
|
|
<const name="WP_RUN_CORE_TESTS" value="1" />
|
|
|
|
</php>
|
2016-04-20 19:01:07 +02:00
|
|
|
<listeners>
|
|
|
|
<listener class="SpeedTrapListener" file="tests/phpunit/includes/speed-trap-listener.php">
|
|
|
|
<arguments>
|
|
|
|
<array>
|
|
|
|
<element key="slowThreshold">
|
|
|
|
<integer>150</integer>
|
|
|
|
</element>
|
|
|
|
</array>
|
|
|
|
</arguments>
|
|
|
|
</listener>
|
|
|
|
</listeners>
|
2015-09-28 04:36:23 +02:00
|
|
|
</phpunit>
|