Week in Test: October 20, 2025
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 blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.-level comments:
- Help Test WordPress 6.9
- Actively developed for 6.9. See #66377
Test Handbook 📘
It’s Time to Review the Test Handbook in GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/
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. 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 SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/, and we will help you get on the process.
Here are the handbook Pull requests that need reviews before merging and here are the pending Issues of the [MIRROR] Project 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 CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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
- #63486 – Script modules should support being printed in the footer the same as classic scripts
- #64025 – wp_die() status code posts component updates (parent ticket: #64009)
- #63021 – Lazy load user meta
- #48207 – Implement new Comment Date Functions
- #63878 – Backport: add support for text inputs on the elements API
- #38067 – New filter `wp_post_lock_status`
- #63989 – is_user_member_of_blogs fetches all user meta keys
- #63045 – Add caching to `count_many_users_posts()`
b. 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:
c. 6.9 Related issues need testing
The following 6.9 tickets need testing, those are having patches:
- #48207 – Implement new Comment Date Functions
- #63878 – Backport: add support for text inputs on the elements API
- #63697 – Add OPCache to Site Health
- #63045 – Add caching to `count_many_users_posts()`
- #63486 – Script modules should support being printed in the footer the same as classic scripts
2. GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc.
https://wordpress.org/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.
- Widgets screen stops at batch preflight (no POST) and shows “The response is not a valid JSON response”; no fallback when batch is unavailable
- Opening the block inserter popover when the block inserter panel is open completely disables/breaks the inline block inserter button
- 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.
Badge awarding has been paused until the Test Handbook migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. is complete. Keep contributing and we will get to you
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 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 beginning October 21
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2025.
2025 Schedule:
- Wednesday, 22 October 2025 at 17:00 GMT+3 : <Test-Team-Chat> in #core-test.
- Thursday, 23 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