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 in order to move a ticket forward for patching.
The following new tickets are awaiting review, and need testers to attempt to reproduce the reported issue (aka “repro”), and then provide a reproduction test report with the results:
- #63280 wp-settings- and wp-settings-time- cookies set on every admin request if user settings empty
- #63283 Bug in version check returned values from api.wordpress.org
- #63282 Inconsistent post name processing
- #63292 atom_enclosure doesn’t always get MIME type – inconsistency with rss_enclosure
- #63291 Twenty Twenty-One: fix text color in starter content
- #63290 Cover block overlays didn’t display after 6.8 update—every page had to be resaved
- #63306 There is already 20px padding on the right side, and an additional 2px margin is being applied, making the total spacing 22px..
- #63305 On mobile devices, the left and right padding or margin in the General Settings section of the dashboard are not equal, which doesn’t look good from the user’s perspective.
- #63296 array_intersect_key() fatal error in wp_render_layout_support_flag() due to invalid string parentLayout in core/social-links block
- #63308 tinymce cache key should be updated
- #63312 Application Passwords panel disappears when any plugin is active
- #63309 Twenty Fifteen: Table block border not appear properly.
- #63319 Site no longer finds the home page when opening – My bad I’ve done something
- #63307 REST API: Returns incorrect post when querying by slug if sticky posts exist
- #63316 [E_WARNING] Undefined array key “host” in wp-includes/canonical.php on line 717
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:
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:
- No tickets found
Profile Badge Awards 🎉
Profile badges awarded to Manoj Maharrshi
Read/Watch/Listen 🔗
- WordPress 6.8 “Cecil” is released on 15th April
- WordPress 6.8 Source of Truth
- Call for 6.8.x Release Managers
- WP_Query changes in WordPress 6.8
- WordPress 6.8 performance improvements
- WordCamp Europe 2025: Sali, Basel!
- A New Cadence for WordPress Core
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2025.
2025 Schedule:
- Wednesday, 23 April 2025 at 21:30 GMT+5:30:
<test-chat>in #core-test. - Wednesday, 30 April 2025 at 21:30 GMT+5:30:
<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.