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:
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:
- #63252 $tax_url with no path not accounted for in /wp-includes/canonical.php
- #63254 Introduce development mode for block editor styles
- #63260 Long user display names overflow in media modal (grid view)
- #63259 Replace zxcvbn with zxcvbn-ts
- #63273 Fatal due to superglobal $_POST modification with invalid int type
- #63276 Twenty Fourteen: Content width in block editor
- #63263 check if exists before accessing object properties of $post->comment_count
- #63271 Multisite (Subdirectory) URL Corruption in Page Content (Language Site)
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:
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 tickets need PHPUnit tests built to accompany their respective patches:
- No tickets found
Profile Badge Awards 🎉
Profile badge assigned to Masud Rana
Read/Watch/Listen 🔗
- WordPress 6.8 RC3 is now available for testing.
- Ahead of it, there will be a Dry Run on Monday, April 14, 2025. A detailed overview of the release schedule for WordPress 6.8 can be found here. The article also includes information about the individuals assigned to each release party.
- The general release of WordPress 6.8 will be available on Tuesday, April 15, 2025.
- The Gutenberg 20.7-RC is ready for testing.
- WordPress 6.8 Field Guide
- What’s new for developers?
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2025.
2025 Schedule:
- Wednesday, 16 April 2025 at 21:30 GMT+5:30:
<test-chat>in #core-test. - Wednesday, 23 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.