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:
- Roadmap to 6.8
- Bug Scrub Schedule for WordPress 6.8
- Help Test WordPress 6.8
- How to Contribute to WP 6.8 Release Party
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:
- #63127 wp_mail resets custom headers when headers array is set to empty, causing loss of custom header data (e.g., boundary)
- #63131 Possible bug (not strict) use of preg_split in formatting.php
- #63140 Unicode Chars (Icons) in the URL are possible, but break WordPress
- #63143 Twenty Nineteen: Inconsistent spacing between Table Caption and Table in Table Block
- #63133 Latest Comments block having issue with alignment
- #63148 wpautop() formatting function generate invalid HTML if the text end with an empty <p> tag
- #63153 Onscreen keyboard obscures Custom Fields input on mobile
- #63154\ Fatal error when moderation hash is given as array
- #63157 wp_list_comments behaves differently when passed string or array
- #63159 load_textdomain tries to load the current working directory as a file
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:
- #61244 The export_wp() function inserts empty <wp:comment> data when get_comment() returns a false or empty value
- #61381 Bulk update plugins no longer working when 1 Plugin failed to update
- #33600 Add `theme_mods_{$stylesheet}` option during `populate_options()`
- #63114 No screen reader announcements for upload image errors
- #14060 Misleading “You do not have sufficient permissions to access this page.”
- #39242 Add caching to count_user_posts()
- #62718 Automatic updater of WordPress always fails if FS_METHOD is ftpext since 6.6 with PHP 8.0+
PHPUnit Tests 🛟
Who? Any QA or PHP developer contributors who can (or are interested in learning how to) build automated PHPUnit tests.
Why? Automated tests improve the software development feedback loop for quality and backward compatibility.
The following tickets need PHPUnit tests built to accompany their respective patches:
- Same as above tickets
Profile Badge Awards 🎉
No Badges awarded this week.
Read/Watch/Listen 🔗
- WordPress 6.8 Beta 3 is now available for testing. Please share your feedback and report the issue on trac/github if you find any regression.
- The RC1 release of WordPress 6.8 is scheduled for Tuesday, March 25th. Please check the detailed overview of the release schedule for WordPress 6.8. Join the Release Party in #core to test and provide the feedback!
- What’s new for developers? is live now!
- Gutenberg 20.5 was released on Wednesday, March 19th. This is the first version of Gutenberg to be merged into WordPress 6.9 next major release of the this year. Checkout this milestone for Gutenberg 20.5 release related updates.
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2025.
2025 Schedule:
- Wednesday, 26 March 2025 at 21:30 GMT+5:30:
<test-chat>in #core-test. - Wednesday, 02 April 2025 at 21: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.