Week in Test: November 3, 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.

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 📘

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 be 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 syncing. 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 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:

• #19826 – Error behavior for deleting trashed posts is different for Bulk Delete versus Empty Trash
• #63987 – wp_get_scheduled_event() incorrectly returns false for cron events scheduled with a timestamp of 0.
• #60362 – Emojis cause “Updating failed. Could not update post in the database.” error
• #63568 – WP_Font_Face: Font names that contain single quotes are not wrapped in double quotes
• #31992 – Unicode Email Addresses
• #61393 – Trailing Slash Issue in Category Pagination URLs with the_posts_pagination()
• #63256 – Unnecessary array_map() call in get_terms() when object_ids is not set

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/preface.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:

• #64065 – Dragging theme/plugin ZIP outside file input, downloads file instead of uploading

c. 6.9 Related issues need testing

The following 6.9 tickets need testing, those are having patches:

• #60362 – Emojis cause “Updating failed. Could not update post in the database.” error
• #31992 – Unicode Email Addresses
• #61393 – Trailing Slash Issue in Category Pagination URLs with the_posts_pagination()
• #63256 – Unnecessary array_map() call in get_terms() when object_ids is not set

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.

• Previous Notes Box Reappears When Clicking on Another Block
• When linkcontrol popover in the blockcontrols is open, the entire page scrolls
• “Warning: Undefined array key” message appears after updating to 21.8.2 (conflict between Gutenberg and WooCommerce)
• Notes: when using the pinned sidebar, ensures selecting notes properly shows them
• File Block: Embed Permission Issue With unfiltered_html capability
• Widgets screen stops at batch preflight (no POST) and shows “The response is not a valid JSON response”; no fallback when batch is unavailable

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 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉
@passoniate @jdahir0789 @gulamdastgir04

Read/Watch/Listen 🔗

• 22.0.0 RC1 is now available.
• WordPress 6.9 Release Party Schedule
• Bug Scrub Schedule for WordPress 6.9
• The New WordPress Playground File Browser and UI Enhancements!
• WordPress 6.8 Beta 3 is now ready for testing!
• WordPress 6.9 is planned for December 2, 2025, with RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 1 beginning November 11, 2025

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings held in 2025.

2025 Schedule:

• Wednesday, 5th November 2025 at 16:00 GMT+2 :  <Test-Team-Chat> in #core-test.
• Thursday, 6th November 2025 at 18:00 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.

#core-test, #gutenberg, #core

Props to @sirlouen @nikunj8866 for helping review this article and offering feedback

#core-test, #full-site-editing, #gutenberg, #make-wordpress-org-mobile, #make-wordpress-orgupdates