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 |Test Handbook | Weekly Testing Roundup | WordPress Core Testing | Gutenberg Testing | 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:
- Collaboration: add block-level comments:
- Help Test WordPress 6.9
- Actively developed for 6.9. See #66377
Call for test table lead for WC Islamabad
- WordCamp Islamabad is happening on 18–19 October 2025, with Contributor Day on the 18th. They’re looking for an online table lead for Testing to guide their local community and they’re open to connecting over Zoom/Google Meet. If anyone from the team is interested, please comment on this post or reply in the channel.
Test Handbook 📘
It’s Time to Review the Test Handbook in Github
For the last week, a good amount of test contributors have embarked on the journey of reviewing our new Test Handbook based on Github. We still need more members to join, because we must make sure, that every single page is reviewed at least 2 or 3 times to avoid missing anything. If you want to join us, please write in the #core-test chat in Slack, and we will help you get on the process.
Here are the handbook Pull requests and here are the pending tasks for review.
Weekly Testing Roundup 🤠
Bi-Weekly update: Test Team Update
Here’s a roundup of active tickets that are ready for testing contributions. Did you know that contributions to 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.
1. WordPress Core Testing
a. 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:
- #63697 – Add OPCache to Site Health
- #63987 – wp_get_scheduled_event() incorrectly returns false for cron events scheduled with a timestamp of 0.
- #63486 – Script modules should support being printed in the footer the same as classic scripts
- #63531 – Category dropdown does not meet WCAG 2.2 A on windows and some linux systems
- #64025 – wp_die() status code posts component updates (parent ticket: #64009)
- #63021 – Lazy load user meta
- #41471 – Page dropdown walker must check selected against value field
- #63858 – Trigger the wp_cron action from the shutdown hook instead of the init hook to reduce TTFB (⏱️ Time To First Byte) and improve performance 📈
- #63676 – Blocks without rendered content (including blocks via block visibility) still enqueue scripts and styles
- #60770 – TimeZone select box compatibility with RTL directions
b. 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:
- We had no Unit tests this week
c. 6.9 Related issues need testing
The following 6.9 tickets need testing, those are having patches:
- #63697 – Add OPCache to Site Health
- #63486 – Script modules should support being printed in the footer the same as classic scripts
- #63531 – Category dropdown does not meet WCAG 2.2 A on windows and some linux systems
- #63858 – Trigger the wp_cron action from the shutdown hook instead of the init hook to reduce TTFB (⏱️ Time To First Byte) and improve performance 📈
2. Gutenberg Testing
👋 Want to contribute to WordPress/gutenberg? If you have a bug or an idea, read the contributing guidelines before opening an issue. If you’re ready to tackle some open issues, we’ve collected some good first issues for you.
a. Gutenberg Bug Reproduction Testing
The following tickets have been filed reporting a known bug and needs testers to manually test, then provide feedback through a bug reproduction report that the issue can be reproduced.
- Custom font upload not working
- FontSizePicker incorrectly measures units for selecting elements
- Core Button “Outline” Style Bug
- ColorPalette: deselecting color should respect the clearable property
- Navigation Block Accessibility: Mobile menu items cannot be navigated with TalkBack swipe gestures on Android
b. Gutenberg Patch Testing
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:
- Nothing to test yet this week
Profile Badge Awards 🎉
No Badges Issues this Week
Read/Watch/Listen 🔗
- Gutenberg 21.8RC is now available.
- The Test Handbook Overhaul
- Notes from the Core Committer meeting at WCUS 2025 are now available.
- WordPress 6.9 Release Party Schedule
- Bug Scrub Schedule for WordPress 6.9
- WordPress 6.9 is planned for December 2, 2025, with Beta 1 beginning October 21
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2025.
2025 Schedule:
- Wednesday, 15 October 2025 at 17:00 GMT+3 : <patch-testing-session> in #core-test.
- Thursday, 16 October 2025 at 18:00 GMT+3 : <patch-testing-session> 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.
Props to @sirlouen @nikunj8866 for helping review this article and offering feedback