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:
Weekly Testing Roundup 🤠
Weekly update: Test Team Update: 13 May 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:
- #61155 Maximise compatibility with password managers when resetting password
- #61157 Blocks Query pagination NEXT & PREV produce incorrect URLs when queried via REST API
- #61161 current_user_can fatal error
- #61162 Internal WordPress Plug-in Search dont show relevant results
- #61164 Clen installation fails ….
- #61158 Lightbox effect doesn’t work
- #61169 Getting inconsistent error on changing role
- #61168 Bulk select issue with with All select
- #61176 moderate CPU load (lsphp handler) and anomalies invoked in eFroms
- #61179 Deprecated messages about passing null in widgets.php
- #61186 Twenty Nineteen: Archive Block Alignment is not working in backend
- #61187 Bundled Themes: Calendar Block color issue in backend
- #61202 Gallery Block Columns Broken
- #61177 WordPress admin menu cannot cater for hundreds of menu items
- #61204 Issue for long custom template name
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:
- #42598 Twenty Seventeen: Sticky header offset issue
- #57789 Make theme.json related caches persistent
- #49950 Twenty Twenty: with horizontal menu, submenu should be dismissible
- #60835 Fix and improve handling of uploading of font files
- #61154 Fix the ‘attributes’ dynamic property in WP_Block
- #58539 Twenty Seventeen: Image block figcaption text alignment inconsistency
- #58087 Fix the ‘data’ dynamic property in WP_Term
- #56443 Twenty Nineteen: button block font size issue.
- #61180 Twenty Seventeen : Latest Comments Author font weight is different in both side
- #59493 Bundled themes: remove blank CSS lines
- #61199 Make Settings API documentation link clickable in options.php
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.6 tickets need PHPUnit tests built to accompany their respective patches:
- #60291 Support Lossless WebP in WP_Image_Editor_GD
- #52723 Admin options.php default value to NULL for option_value may lead to MySQL Integrity constraint violation error, potential other bugs
- #51019 convert_smilies() fails on large tags
- #60158 The description field for media doesn’t automatically make paragraphs in the generated code
- #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
- #61137 Allow view access of template rest endpoint to anyone with the edit_post capability
- #58905 Ensure locate_template only loads theme files
- #61123 Background block supports: add support for top-level styles in theme.json
- #60698 Token Map: Introduce an efficient lookup and translation class for string mappings.
- #61113 WP_REST_Templates_Revisions_Controller not checking parent ID correctly
6.6 Related issues need testing
The following 6.6 tickets need testing those are having patches:
- #57789 Make theme.json related caches persistent
- #42002 Improve the accordions accessibility
- #49950 Twenty Twenty: with horizontal menu, submenu should be dismissible
- #60835 Fix and improve handling of uploading of font files
- #61154 Fix the ‘attributes’ dynamic property in WP_Block
- #58539 Twenty Seventeen: Image block figcaption text alignment inconsistency
- #58087 Fix the ‘data’ dynamic property in WP_Term
- #56443 Twenty Nineteen: button block font size issue.
- #61180 Twenty Seventeen : Latest Comments Author font weight is different in both side
- #59493 Bundled themes: remove blank CSS lines
- #61199 Make Settings API documentation link clickable in options.php
Profile Badge Awards 🎉
Badges awarded to: Sumit Bagthariya, Ramon Ahnert. Congratulations!
Read/Watch/Listen 🔗
- The WordPress 6.6 roadmap has been published.
- WordPress 6.5.3 was released on Tuesday, May 7. This minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. features 12 bug fixes in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and 9 bug fixes for the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor.
- Gutenberg 18.3 was released on Wednesday, May 8. The release highlights include a full page client-side navigation experiment, negative values for margin controls, and adding a publish flowFlow Flow is the path of screens and interactions taken to accomplish a task. It’s an experience vector. Flow is also a feeling. It’s being unselfconscious and in the zone. Flow is what happens when difficulties are removed and you are freed to pursue an activity without forming intentions. You just do it. to the editor.
- We are currently in the WordPress 6.6 release cycle and 4 weeks away from 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.
- Core Editor Improvement: Upgrade your designs
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2024.
2024 Schedule:
- Tuesday, 14 May 2024 at 16:30 GMT+5:30:
<test-triage>in #core-test. - Tuesday, 21 May 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.