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
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:
- #62024 wp_kses_post incorrectly escapes “<” attributes values
- #62028 Paragraph margins not honored (in the backend) when global blockspacing is set to zero (new issue in 6.6.1)
- #62030 Can’t Access Some Block Templates in Classic Themes
- #62044 WP allows to inject random strings into archive page urls, still returning 200
- #62046 `render_block_context` filter works differently on top-level vs. inner blocks
- #62051 Pagination and custom post types that have a hierarchy
- #62052 Suggestions prompt doesn’t always appear after publishing a post
- #62054 Problems on my Genesis Framework after WordPress update 6.62
- #62049 Italics HTML tags in Post Titles are Being Converted to HTML Entities
- #62038 Issue with is_email() and sanitize_email()
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:
- #10275 Filter logic has been put into the template loader while it not belongs there.
- #31354 Compound settings confusing with screen readers (checkboxes)
- #34353 redirect_canonical() – Undefined indexes ‘host’ and ‘scheme’
- #52696 Add a way to determine whether a translation exists
- #44610 Allow Youtube-Player to use youtube-nocookie.com URLS to avoid setting cookies.
- #54516 Full site editing/REST-API: modify permission checks to use post type.
- #44921 User nicename discovery is slow to return
- #52294 add_editor_style: Allow replacing a style with an RTL version
- #54304 Expose menu data public in Menus REST API
- #48693 Silence ini_set caused error or check if function_exists first
- #62014 Editor: Add a ‘format’ parameter to query to enable filtering post formats in the Query Loop block
- #61265 Add class name for block variations
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.7 tickets need PHPUnit tests built to accompany their respective patches:
- #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
- #44958   character in title generates a permalink (and slug) with space
- #57379 A Way to Disable Export Theme
- #54648 Improve filter to enable setting quality for each subsize image
- #61308 Return `post_types` field in templates REST API
6.7 Related issues need testing
The following 6.7 tickets need testing those are having patches:
- #10275 Filter logic has been put into the template loader while it not belongs there.
- #31354 Compound settings confusing with screen readers (checkboxes)
- #44921 User nicename discovery is slow to return
- #52294 add_editor_style: Allow replacing a style with an RTL version
- #54304 Expose menu data public in Menus REST API
- #62014 Editor: Add a ‘format’ parameter to query to enable filtering post formats in the Query Loop block
- #61265 Add class name for block variations
Profile Badge Awards 🎉
No Badges awarded this week.
Read/Watch/Listen 🔗
- WordPress 6.2.2 was released this week.
- Next major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” — for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality.: 6.7 – We are currently in the WordPress 6.7 release cycle. WordPress 6.7 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 is scheduled for Tuesday, October 1. The Road Map post can be found here.
- Next 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.: 6.6.3 – Following the recent WordPress 6.6.2 release, the next maintenance release (if needed) will be WordPress 6.6.3. There were not updates shared in the meeting.
- Next GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc.
https://wordpress.org/gutenberg/ release: 19.2 – The next Gutenberg release will be 19.2, scheduled for September 11 (this release occurred after the meeting). - WordPress Contribution Health Dashboards: An Experiment
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2024.
2024 Schedule:
- Tuesday, 17 September 2024 at 16:30 GMT+5:30:
<test-triage>in #core-test. - Tuesday, 24 September 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.