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:
Early Opportunities to Test WordPress 6.5
Ahead of betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 for WordPress 6.5 on February 13th, this is an early opportunity to provide feedback as features are rapidly underway. Of note, this is intentionally just a selection of what’s ready to test and doesn’t include everything mentioned in the roadmap. Expect a broader testing post, like this for 6.4, for the release once beta 1 is out in the world.
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:
- #60218 PHPunit test for wp_parse_id_list
- #60224 Document global variables comment code improvement on WP themes.
- #60225 Directional Keyboard Scrolling Jump Bug
- #60226 Incomplete page list in backend editor window
- #60236 Customizer’s Widget’s component should only be loaded when not using a Block Theme
- #60212 apply_filters_deprecated() should tell the caller location
- #60243 KSES: Allow encoded images
- #60248 Unable to delete theme placed in subdirectory
- #60240 Script Modules API: Move the modules to the footer in classic themes
- #60251 NOT SURE what to do with thie NOTICE MESSAGE SHOWN IN Customize Screen
- #60261 Fatal error with invalid charset specified in Trackback
- #60239 Twenty Sixteen: Quote block border width is relative on front end but 4px in editor
- #60263 Fluid typography: PHP division by zero error when theme.json min and max viewport widths are equal
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:
- #58783 Alternative text entered whilst uploading an image is lost when the image finished uploading
- #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
- #59688 Add descriptions to patterns in bundled themes
- #58827 Publish the Patterns page in the Site Editor to all non-block themes
- #55991 Twenty Twenty One: Unable to change size in Quote block
- #58226 HTML attribute “action” on element “form”: Must be non-empty.
- #59866 Attachment pages are only disabled for users that are logged in
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.4.2 tickets need PHPUnit tests built to accompany their respective patches:
Profile Badge Awards 🎉
No Badges awarded this week.
Read/Watch/Listen 🔗
- WordPress End of Year Celebrations! – Amidst the myriad events and releases that get highlighted during the course of a year in WordPress, countless other projects and contributions quietly move us ever closer to our goals.
- A Look Ahead at WordPress in 2024 – Curious about WordPress’s big-picture items for 2024? Phase 3, Data Liberation, new meetups, and more, get the spotlight in this episode
- Are you interested in helping pilot a new tool to streamline testing and improve developer feedback? Please see Early Opportunities to Test WordPress 6.5
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2024.
2024 Schedule:
- 16 January 2023 at 11:00 UTC :
<test-chat>in #core-test. - 23 January 2023 at 11:00 UTC :
<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.
Thank you @ankit-k-gupta for the peer review.