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: Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings
Weekly Testing Roundup 🤠
Weekly update: Test Team Update
Here’s a roundup of active tickets that are ready for testing contributions.
Did you know that contributions with 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.
Reproduction Testing 🔁
Who? Any contributor.
Why? It is helpful to show an issue exists for other users to move a ticket forward for patching.
The following new tickets have been reviewed, and need testers to attempt to reproduce the reported issue (aka “repro”), and then provide a reproduction test report with the results:
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 to validate that a patch addresses 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:
- #63700 – Backport Global Styles: Make Button element inherit all typography styles on the frontend
- #63709 – Twenty Twelve: version 4.6 adds CRLF line endings on every file
- #63714 – Missing width/height attributes on SVG file since WP 6.8.2
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:
- #59911 – WordPress 6.4 changes the font-face generation using wrong fontFamily attribute from theme.json preset
- #43502 – `WP_REST_Posts_Controller::prepare_item_for_response()` doesn’t reset postdata after calling setup_postdata()
- #37344 – Side effects on ‘nav_menu_item_args’ filter when appending to arguments
- #63724 – HTML API: Reliably parse HTML attributes in `wp_kses_hair()`
- #38183 – Add hooks to be run before and after each callback
Profile Badge Awards 🎉
No Badges awarded this week.
Read/Watch/Listen 🔗
- The First Onboarding Session & Workflow Review
- Introducing the WordPress Test Contributors Group
- What’s new in Gutenberg 21.3? (30 July)
- Portland, Are You Ready? The WCUS 2025 Schedule Has Arrived!
- Maintenance Releases for WordPress branches 4.7 to 6.7
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2025.
2025 Schedule:
- Wednesday, 13 August 2025 @ 4PM GMT (6PM CET 9.30PM IST):
<test-chat>in #core-test. - Thursday, 14 August 2025 @ 1PM GMT (3PM CET 6.30PM IST): Contributors Onboarding & Coffee Hours in #core-test.
- Wednesday, 20 August 2025 @ 4PM GMT (6PM CET 9.30PM IST):
<test-triage>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 @krupajnanda for helping review this article and offering feedback.