wordpress-develop

mirror of https://github.com/gosticks/wordpress-develop.git synced 2025-10-16 12:05:38 +00:00

History

Felix Arntz 6560f46a0f Media: Ensure images within shortcodes are correctly considered for loading optimization attributes. Prior to this change, images added in shortcodes would be considered separately from all other images within post content, which led to incorrect application of the loading optimization attributes `loading="lazy"` and `fetchpriority="high"`. This changeset changes the filter priority of `wp_filter_content_tags()` from the default `10` to `12` on the various content filters it is hooked in, in order to run that function after parsing shortcodes. While this may technically be considered a backward compatibility break, substantial research and lack of any relevant usage led to the assessment that the change is acceptable given its benefits. An additional related fix included is that now the duplicate processing of images is prevented not only for post content blobs (`the_content` filter), but also for widget content blobs (`widget_text_content` and `widget_block_content` filters). Props joemcgill, mukesh27, costdev, spacedmonkey, flixos90. Fixes #58853. git-svn-id: https://develop.svn.wordpress.org/trunk@56693 602fd350-edb4-49c9-b593-d223f7449a82		2023-09-26 00:11:06 +00:00
..
data	Filesystem API: Add missing ZIP file for unzip tests.	2023-09-25 23:38:38 +00:00
includes	Code Modernization: Use `dirname()` with the `$levels` parameter.	2023-09-11 04:51:09 +00:00
tests	Media: Ensure images within shortcodes are correctly considered for loading optimization attributes.	2023-09-26 00:11:06 +00:00
multisite.xml	Build/Test Tools: Remove random_compat from PHPCS and PHPUnit configuration files.	2023-09-24 07:43:50 +00:00
README.txt	Docs: Remove double spaces in `tests/phpunit/README.txt`.	2022-04-29 13:31:48 +00:00
wp-mail-real-test.php	Coding Standards: Remove superfluous blank lines at the end of various files.	2023-09-07 14:57:30 +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.