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.
Table of Contents
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:
Test Handbook 📘
Merging of 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 number of test contributors embarked on the journey of reviewing our new Test Handbook based on GitHub. The Process has been concluded successfully with the merging.
- We want to inform that the Test Handbook is officially
synced. There might be a couple of bugs and things that are not looking good pending to be fixed. - Feel free to give it a check here, and if you find any bugs, go to the GitHub repository and report them.
- You can send a PR with the fix, or simply send the issue, and we will check it
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 skills? 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 (4) 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:
- #56914 – Better guide users when deleting other users
- #64354 – Outlined buttons now have grey background
- #63697 – Add OPCache to Site Health
- #45035 – allow register_post_type() arg to control whether a CPT’s counts are added to the “At a Glance” Dashboard widget
b. Bug Reproduction
It is necessary to confirm if the bug is happening under multiple conditions and environments, using the bug reproduction report in order to validate the issue.
The following tickets (204) have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, the provide a bug reproduction report:
- #64433 – Bug while upgrading individual plugins
- #56241 – The post category count according post data not showing on admin side.
- #38224 – Not enough results in menu-page-add-search
- #15981 – Quick edit (and other actions) need to cancel AJAX actions
- #44964 – `redirect_guess_404_permalink` doesn’t support array in `post_type` var
c. Handbook Review
Here are the current activities being discussed in the Test Handbook:
- We need to review https://github.com/WordPress/test-handbook/pull/98
- Test Team Discussions
- Time to Review/Update the Get Set Up for Testing Page.
- Time to Comment Back/Update the Test Team Reps Page.
- Update on Test Handbook: New pages for Feature & Enhancement Testing (#90), E2E Testing (#91), and Patch Testing Scrubs (#92) are available; contributors can update content via GitHub issues.
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 (0) 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.
- Nothing this week
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:
- None this week
Profile Badge Awards 🎉
Congratulations to the recipients of the Test Contributor Badge 🎉
- None this week
– Kindly find the Contribution Guidelines here
Read/Watch/Listen 🔗
- Gutenberg 22.3.0 RC1 is now available.
- Test Team Update: 22 December, 2025
- WordPress 6.9 “Gene” is here
- WordPress Importer can now migrate URLs in your content
- WordPress 6.9 Field Guide
- AI Experiments Plugin v0.1.0
- MCP Adapter v0.4.1 is now available.
- Notes feature in WordPress 6.9
- Introducing the WordPress Abilities API
- Snippet: Schema.org microdata for Accordion block FAQs
Upcoming Meetings 🗓
🚨 There will not be any more #core-test meetings held in 2025.
2026 Schedule:
- Wednesday, 7th January 2026 at 16:00 GMT+2 : <Test-Team-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.
Props to @nikunj8866 @sirlouen for helping review this article and offering feedback