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:
- Help test WordPress 6.6 – We are currently looking for volunteers who can help us in testing the upcoming version.
- Let’s start testing Learn.WordPress.org
Weekly Testing Roundup 🤠
Weekly update: Test Team Update: 15 July 2024
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:
- #61600 Import of scheduled posts
- #61602 site health – disk_free_space return error
- #61620 Edited Images don’t include un-edited versions in WXR file, even if used in a Post
- #61621 WP_Query get_posts should be call its property not again execute all caculations
- #61597 Resized images larger in filesize than original, when setting jpeg_quality to 100
- #61631 sanitize_option_{$option} inconsistencies
- #61625 Styles enqueued from block.json are not correctly configured for RTL
- #61634 Bugged Editing Pages
- #61642 Block Bindings: Add context needed by sources during its processing
- #61640 Issues in edit_link Function: Inconsistent Return Values, Insufficient Permission Error Handling, and Data Sanitization
- #61638 Site Health Tool – Directory sizes stuck in loading state in WordPress v6.6 RC3
- #61592 6.6-RC2 Editing/Inserting Synced pattern (reusable block) with server side rendering broken.
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:
- #60374 Twenty Sixteen: Navigation block inherits colors from button styles
- #57789 Make theme.json related caches persistent
- #45197 Introduce `user_can_for_blog()`
- #51019 convert_smilies() fails on large tags
- #60669 Twenty Twenty-Two: Search block does not show selected border on button
- #61614 Media: Ensure Imagick quality is set correctly
- #52592 PHP warning when the label property is missing from register_block_style
- #61633 Twenty Twenty-One: alignment of site title and navigation links
- #60835 Fix and improve handling of uploading of font files
- #45924 Twenty Nineteen: Consider making the “—” divider in the header translatable.
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. https://www.php.net/manual/en/index.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:
- #37454 get_avatar_data() delivers different url for scheme=https and is_ssl()
- #61308 Return `post_types` field in templates REST API
- #58905 Ensure locate_template only loads theme files
- #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
- #44958   character in title generates a permalink (and slug) with space
- #57379 A Way to Disable Export Theme
- #52592 PHP warning when the label property is missing from register_block_style
6.7 Related issues need testing
The following 6.7 tickets need testing those are having patches:
- #57789 Make theme.json related caches persistent
- #45197 Introduce `user_can_for_blog()`
- #51019 convert_smilies() fails on large tags
- #61614 Media: Ensure Imagick quality is set correctly
- #52592 PHP warning when the label property is missing from register_block_style
- #60835 Fix and improve handling of uploading of font files
Profile Badge Awards 🎉
No Badges awarded this week.
Read/Watch/Listen 🔗
- 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.6
- WordPress 6.6 RC3 was released on July 9. We are in a hard string freeze. Note that the
dev-feedbackanddev-reviewedworkflow is required prior to committing to the 6.6 branch (handbook reference). - WordPress 6.6 Release Day Process, We are currently in the WordPress 6.6 release cycle. WordPress 6.6 is scheduled for Tuesday, July 16. There will be a dry run of the release on Monday, July 15 which starts a 24-hour code freeze of the 6.6 branch.
- WordPress 6.6 RC3 was released on July 9. We are in a hard string freeze. Note that the
- Gutenberg 18.8 is scheduled for July 17 and will include these issues. This version will NOT be included in the WordPress 6.6 release and will be included with 6.7.
- Hallway Hangout: Let’s chat about what’s next in Gutenberg (August 2024)
- What would you like to see in the next default WordPress theme?
- WordPress 6.7 Planning Proposal & Call for Volunteers
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2024.
2024 Schedule:
- Tuesday, 16 July 2024 at 16:30 GMT+5:30:
<test-chat>in #core-test. - Tuesday, 23 July 2024 at 16:30 GMT+5:30:
<test-triage>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.