Week in Test: September 23, 2024

Hello and welcome to another edition of Week in Test, the place where contributors of any skill level can find opportunities to contribute to WordPress through testing. You can find the Test Team in #core-test.

Jump to: Calls for Testing | Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings

Calls for Testing 📣

Calls for Testing can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

• Test Scrub Schedule for WordPress 6.7
• Bug Scrub Schedule for WordPress 6.7

Weekly Testing Roundup 🤠

Weekly update: Test Team Update

Here’s a roundup of active tickets that are ready for testing contributions.

Did you know that contributions with the Test Team are also a fantastic way to level up your WordPress knowledge and skill? Dive in to contribute, and gain coveted props 😎 for a coming release.

Reproduction Testing 🔁

Who? Any contributor.
Why? It is helpful to show an issue exists for other users in order to move a ticket forward for patching.

The following new tickets are awaiting review, and need testers to attempt to reproduce the reported issue (aka “repro”), and then provide a reproduction test report with the results:

• #62059 http request failed Error cURL 28
• #62060 Error Message When Using the WordPress Uploader
• #62077 New user registration emails send the default (wrong) “From:” headers
• #62089 site editor, “all template parts” empty list in UI. Requires browser refresh
• #62094 /wp-json/oembed/1.0/embed returns too big thumbnail_url
• #62084 Line Breaks not displayed in emails
• #62096 Twenty Nineteen: adjust avatar dimensions for comment author
• #62090 Add filter for supported block binding attributes

Patch Testing 🩹

Who? All contributors (not just developers) who can set up a local testing environment.
Why? It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

• #41155 Theme Details dialog hides admin sidebar sub-menu navigation
• #59207 Twenty Thirteen: correct styling for Button & File block links in front-end widget areas (Footer & Sidebar)
• #59521 Issue with update_post_thumbnail_cache if using get_posts
• #31240 Combine domain and path UI in Add New Site flow
• #61381 Bulk update plugins no longer working when 1 Plugin failed to update
• #31127 Can’t add a new user to two sites before they’ve accepted their account
• #35379 update_network_option changes stored option value if sanitize_option detects error
• #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
• #32544 No function exposes all supported MIME types
• #61244 The export_wp() function inserts empty <wp:comment> data when get_comment() returns a false or empty value
• #45197 Introduce `user_can_for_blog()`
• #61265 Add class name for block variations
• #62014 Editor: Add a ‘format’ parameter to query to enable filtering post formats in the Query Loop block
• #60835 Fix and improve handling of uploading of font files
• #32597 mediaelement.js high CPU usage triggered by the buffering CSS animation
• #61117 Guard condition in `delete_temp_backup()` shouldn’t return early
• #54213 “Authorize Application” should reject handling an already existing app name
• #56311 Week query variable is not being sanitized correctly
• #61765 Twenty Twelve: The large quote pattern does not use a quote block

PHPUnit Tests 🛟

Who? Any QA or PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. developer contributors who can (or are interested in learning how to) build automated PHPUnit tests.
Why? Automated tests improve the software development feedback loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. for quality and backward compatibility.

The following 6.7 tickets need PHPUnit tests built to accompany their respective patches:

• #44958 &nbsp character in title generates a permalink (and slug) with space
• #57379 A Way to Disable Export Theme
• #54648 Improve filter to enable setting quality for each subsize image
• #61308 Return `post_types` field in templates REST API
• #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
• #62014 Editor: Add a ‘format’ parameter to query to enable filtering post formats in the Query Loop block
• #62069 Block Bindings: block doesn’t receive full __default bindings during render

6.7 Related issues need testing

The following 6.7 tickets need testing those are having patches:

• #41155 Theme Details dialog hides admin sidebar sub-menu navigation
• #59521 Issue with update_post_thumbnail_cache if using get_posts
• #61381 Bulk update plugins no longer working when 1 Plugin failed to update
• #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
• #61244 The export_wp() function inserts empty <wp:comment> data when get_comment() returns a false or empty value
• #45197 Introduce `user_can_for_blog()`
• #61265 Add class name for block variations
• #62014 Editor: Add a ‘format’ parameter to query to enable filtering post formats in the Query Loop block
• #44921 User nicename discovery is slow to return
• #56780 shortcode block in block-based template part in a classic theme does not get expanded
• #60835 Fix and improve handling of uploading of font files
• #54213 “Authorize Application” should reject handling an already existing app name
• #60783 plugins_api() and parameters
• #61765 Twenty Twelve: The large quote pattern does not use a quote block

Profile Badge Awards 🎉

No Badges were awarded this week.

Read/Watch/Listen 🔗

• PDX + WCUS 2024: A Recap
• Core Editor Improvement: Simplified Query Loop block with smarter defaults & intuitive settings
• Next major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality.: 6.7
  • We are currently in the WordPress 6.7 release cycle. WordPress 6.7 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is scheduled for Tuesday, October 1. The Road Map post can be found here.
• Next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: 6.6.3
  • Following the recent WordPress 6.6.2 release, the next maintenance release (if needed) will be WordPress 6.6.3. There were not updates shared in the meeting.
• Next GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ release: 19.2
  • The next Gutenberg release will be 19.2, scheduled for September 11 (this release occurred after the meeting).

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings held for 2024.

2024 Schedule:

• Tuesday, 24 September 2024 at 16:30 GMT+5:30: <test-chat> in #core-test.
• Tuesday, 1 October 2024 at 16:30 GMT+5:30: <test-bug-scrub> in #core-test.

Interested in hosting a <test-scrub>? Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

#core-test