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 | Weekly Testing Roundup | 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:
- Coming soon!
- 6.8 Roadmap
- Help Test 6.8
- Bug Scrub Schedule for WordPress 6.8
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:
- #62871 Font Library Install Fonts not accessible after migrating website
- #62873 unable to install plugins
- #62877 Inconsistent behaviour of redirect guess when page is private
- #62884 Total error otimization in nav-menu.js
- #62895 Bundled Themes: Accessibility additions to the site title link
- #62894 Media Library functionality in the block editor causes CSP ‘unsafe-eval’ error
- #62896 Twenty Nineteen: Limit scope of aria-haspopup and aria-expanded to the primary menu
- #62897 Title attribute of menu item is not correctly displayed in the frontend
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:
- #55358 Passing int term term_exists parent param not respected
- #62238 Update the screen-reader-text CSS class and its local implementations
- #37040 Enhancement: new function to validate a transient exists, and isn’t expired without extra query
- #55974 Bundled theme: Add support for border options
- #58905 Ensure locate_template only loads theme files
- #61154 Fix the ‘attributes’ dynamic property in WP_Block
PHPUnit Tests 🛟
Who? Any QA or PHP developer contributors who can (or are interested in learning how to) build automated PHPUnit tests.
Why? Automated tests improve the software development feedback loop for quality and backward compatibility.
The following tickets need PHPUnit tests built to accompany their respective patches:
- #59440 WP_Comments_List_Table bulk actions do not account for user permissions.
- #38433 Complete test coverage for current_user_can_for_blog()
- #58234 sanitize_title_with_dashes fatal error when query var value is an array in php 8
6.8 Related issues need testing
The following 6.8 tickets need testing those are having patches:
- #62238 Update the screen-reader-text CSS class and its local implementations
- #37040 Enhancement: new function to validate a transient exists, and isn’t expired without extra query
- #58905 Ensure locate_template only loads theme files
- #61154 Fix the ‘attributes’ dynamic property in WP_Block
Profile Badge Awards 🎉
No Badges awarded this week.
Read/Watch/Listen 🔗
- We are currently in the WordPress 6.8 release cycle. Read more about the release squad, timeline, and focus for this release.
- ⚠️ Beta 1 is only five weeks away!
- WordPress 6.7.2 is scheduled for February 11, with an RC planned for February 4. Review the next minor release milestone.
- The next Gutenberg release will be 20.2, tentatively scheduled for February 5. It will include the following issues.
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2025.
2025 Schedule:
- Wednesday, 05 February 2025 at 21:30 GMT+5:30:
<test-triage>in #core-test. - Wednesday, 12 February 2025 at 21:30 GMT+5:30:
<test-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.