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:
- #63157 wp_list_comments behaves differently when passed string or array
- #63159 load_textdomain tries to load the current working directory as a file
- #63163 WordPress always redirecting secondary domains to main domain set in General settings
- #63162 Sanitizing styles doesn’t work as expected in presence of semi-colon(;) in CSS value
- #63181 Customize Colors and Style Guide Mismatch
- #63179 Dependencies should load in the footer if the script is loaded in the footer
- #63161 Unable to Navigate Autocomplete Suggestions via Keyboard in Theme & Plugin File Editor
- #63195 Unify timestamps of query cache keys
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:
- #63151 [E_WARNING] class-wp-customize-widgets.php:923
- #62839 sync-gutenberg-packages script is not respecting .npmrc file
- #52116 Twenty Twenty: Menu + Search can cause a scroll jump on close
- #18836 ORDER BY RAND() is slow
- #38474 wp_signups.activation_key stores
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:
- No tickets found
Profile Badge Awards 🎉
Read/Watch/Listen 🔗
- WordPress 6.8 RC1 is now available for testing. Please share your feedback and report the issue on trac/github if you find any regression.
- The RC 2 release of WordPress 6.8 will be available on Tuesday, April 1, 2025.. 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!
- WordPress 6.8 Field Guide
- The new version of the Gutenberg plugin is now available in our plugin directory
- Gutenberg 20.6 is scheduled for release on Wednesday, April 2, 2025
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2025.
2025 Schedule:
- Wednesday, 02 April 2025 at 21:30 GMT+5:30:
<test-triage>in #core-test. - Wednesday, 09 April 2025 at 21:30 GMT+5:30:
<test-chat>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.