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 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:
- Understanding and Testing Font Library Feature with block editor theme
- Gutenberg 18.0 RC 2 is now available for testing
- Help test WordPress 6.5 Beta 3
- Help test WordPress 6.5 Beta 1
- Early Opportunities to Test WordPress 6.5
- Bug scrub schedule for WordPress 6.5
Weekly Testing Roundup 🤠
Weekly update: Test Team Update: 1 April 2024
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:
- #60839 WordPress issue > WordPress 6.5 RC3 and 6.4.3, crop feature not working: Invalid Paramter
- #60855 wp_mkdir_p can error when simultaneous requests attempt to create the same directory
- #60849 Meta is saved twice in auto-draft mode
- #60858 Getting Error While updating page which was implemented by Gutenberg
- #60864 URL sanitizing strips valid characters instead of encoding, documented use is invalid
- #60869 Error processing checkout. Please try again.
- #60868 Persistence layer tries to make a REST API call to ‘/wp/v2/users/me’ when user is not logged in
- #60871 Sign releases (PGP, GPG)
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:
- #60724 TT2: Wrap Navigation block in Row within the header.html template part
- #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
- #50026 Twenty Twenty: Full height with short content
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 6.5 tickets need PHPUnit tests built to accompany their respective patches:
- No 6.5 tickets need PHPUnit testing right now.
Profile Badge Awards 🎉
No Badges awarded this week.
Read/Watch/Listen 🔗
- WordPress 6.6 Planning Proposal & Call for Volunteers – If you are interested in joining the release squad, please leave a comment in the post.
- Recap Hallway Hangout: Using Site editor in production for client sites
- Providing more clarity in the Gutenberg GitHub Repo
- WordPress 6.5 Release Candidate 4
- WordPress 6.5 will be released on April 2, 2024.
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2024.
2024 Schedule:
- Tuesday, 2 April 2024 at 16:30 GMT+5:30:
<test-triage>in #core-test. - Tuesday, 9 April 2024 at 16: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.