Welcome to another exciting installment of Week in Test, where contributors of any skill level can find opportunities to contribute testing to the WordPress project. 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 over the next couple of weeks:
- Testing and Feedback for the Fluid Typography Feature
- Call for Testing: WordPress for iOS 20.7
- Full-Width Blocks and Root Padding in WordPress 6.1
Weekly Testing Roundup 🤠
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:
- #56505: Un-necessary Language Files are Installed.
- #56519: Inner blocks serialization bug in
serialize_blockfunction. - #56490:
wp-cron.phpusingcount()on null.
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:
- #55721: Visually align important data on the add new plugins screen.
- #47513: JavaScript TypeError when Video Playlists use native video elements.
- #56468:
sanitize_option()does not handle deprecated timezones correctly.
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 6.1 tickets need PHPUnit tests built to accompany their respective patches:
- #56325: Some blocks’ RTL stylesheets not loading when RTL language is set.
- #55448:
WP_Widget_Blockoutputs empty container if widget has no output. - #55005: Improve PHP performance for
block.jsonfiles.
Profile Badge Awards 🎉
Thank you to the following contributors who earned the Test Contributor profile badge by participating in the WordPress 6.0.2 release party:
Read/Watch 📖
- WordCamp US starts tomorrow! Not attending in person? Check out the livestream options and full schedule.
- 6.1 Product Walk-Through — Watch it 13 September 2022 at 16:00 UTC . The event will be recorded for async viewing.
- This year’s Test Team Rep nominations are complete. Welcome back, Piotr and Brian 🙌🏻
- Testing. Testing: Calls for Testing Facilitators — Do you have a knack for organizing others? Become a testing facilitator!
Upcoming Meetings 🗓
- 9 September 2022 at 13:15 UTC :
<test-scrub>in #core-test. - 12 September 2022 at 16:00 UTC :
<test-chat>in #core-test . - 16 September 2022 at 13:15 UTC :
<test-scrub>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 @laurlittle and @annezazu for their time to review this post.