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: Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings
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:
- #63835 Admin pages listing displays post time instead of modified time for posts with status not equal “published”
- #63830 Event system breaks when an event is scheduled during processing of a queue of more than one events
- #63838 Site logo block should provide a way to specify alt text
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:
- #31992 Unicode Email Addresses
- #63786 KSES: Add new allowed HTML tags
- #63805 Extend the existing conditional loading optimization for block-specific global styles from core blocks to include third-party blocks, improving performance by only loading styles for blocks actually present on the page.
- #63842 Emoji detection inline script introduces needless parser/render blocking
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:
- #40485 Add function for retrieving metadata from registered script
- #63835 Admin pages listing displays post time instead of modified time for posts with status not equal “published”
- #62468 wp_update_post overwrites post_date when updating post_status
Profile Badge Awards 🎉
No Badges awarded this week.
Read/Watch/Listen 🔗
- Test Team Reps: Call for Nominations
- Announcing the WordPress 6.9 Release Squad
- What’s new in Gutenberg 21.4? (13 August)
- Roadmap to 6.9
- Accessibility Team Rep Elections – Voting Now Open
- Portland, Are You Ready? The WCUS 2025 Schedule Has Arrived!
- The First Onboarding Session & Workflow Review
- Introducing the WordPress Test Contributors Group
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2025.
2025 Schedule:
- Wednesday, 20 August 2025 at 21:30 GMT+5:30:
<test-triage>in #core-test. - Wednesday, 27 August 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.