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
Test Handbook 📘
We are in the Final Review of the Test Handbook in Github
For the last few weeks, a good amount of test contributors have embarked on the journey of reviewing our new Test Handbook based on Github. Reviews are underway and the final process set to start. The handbook is awaiting one meeting and will be fully replaced with the new GitHub based content.
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:
- #62715 – Block Hooks: Apply to content-like Custom Post Types
- #48207 – Implement new Comment Date Functions
- #63697 – Add OPCache to Site Health
- #63021 – Lazy load user meta
- #60770 – TimeZone select box compatibility with RTL directions
- #64145 – Notes should not appear in the context of comments
- #63256 – Unnecessary array_map() call in get_terms() when object_ids is not set
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:
- #64065 – Dragging theme/plugin ZIP outside file input downloads file instead of uploading
- #60362 – Emojis cause “Updating failed. Could not update post in the database.” error
c. 6.9 Related issues need testing
The following 6.9 tickets need testing, those are having patches:
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.
- Accordion block breaks the Query Loop with interactivity API
- The accordion panel won’t collapse
- When linkcontrol popover in the blockcontrols is open, the entire page scrolls
- Template activation bugs with plugin-registered templates
- “Warning: Undefined array key” message appears after updating to 21.8.2 (conflict between Gutenberg and WooCommerce)
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.
Badge awarding has been paused until the Test Handbook migration is complete. Keep contributing and we will get to you
Read/Watch/Listen 🔗
- Test Team Update: 27 October, 2025
- Test Scrub Schedule for WordPress 6.9
- Gutenberg 21.9.0 is now available.
- The Test Handbook Overhaul
- 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, October 29, 2025 at 04:00 PM GMT+2:
<patch-testing-session>in #core-test. - Thursday, October 30, 2025 at 06:00 PM GMT+2:
<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