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: 9 September 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:
- #61969 Post guid for custom post type being modified
- #61970 Fatal error: Attempt to read property “ID” on null in /src/wp-includes/rest-api/endpoints/class-wp-rest-autosaves-controller.php
- #61978 Managing Dynamic Search, Category Filtering, and Pagination for Bulk Patterns
- #61984 Favicon • multiple of 48×48 and not 512×512 as WP suggests
- #61991 Inconsistent file name after cropping from Site Icon
- #61996 Slug Conflict When a Published and Draft Page Share post_name
- #62003 User_Query cache triggers fatal error by ignoring ‘fields’ query var
- #61983 Part of `wp_generate_attachment_metadata` missing `avif` extension
- #61997 Undefined array key “height” and “width” in wp-includes/media.php on line 1241 and 1242
- #62007 PHP warning in wp-includes/canonical.php when accessing custom feed with specific permalink structure
- #62009 use strict comparison in wp-admin/includes/media.php
- #62013 the post_name field is not taken into account
- #62010 Twenty Twelve: Add title size is very low.
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:
- #54304 Expose menu data public in Menus REST API
- #61264 Move default rendering mode setting to block_editor_settings_all hook in PHP to allow customizing it
- #60495 Following “plugins_list”: Add a filter in get_views() in class-wp-plugins-list-table
- #31354 Compound settings confusing with screen readers (checkboxes)
- #61244 The export_wp() function inserts empty <wp:comment> data when get_comment() returns a false or empty value
- #44921 User nicename discovery is slow to return
- #58905 Ensure locate_template only loads theme files
- #61890 Handle WP_Term dynamic properties for PHP 8.2
- #61708 Remove the social links pattern
- #52592 PHP warning when the label property is missing from register_block_style
- #52696 Add a way to determine whether a translation exists
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:
- #61308 Return `post_types` field in templates REST API
- #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
- #44958   character in title generates a permalink (and slug) with space
- #54648 Improve filter to enable setting quality for each subsize image
- #57379 A Way to Disable Export Theme
6.7 Related issues need testing
The following 6.7 tickets need testing those are having patches:
- #61264 Move default rendering mode setting to block_editor_settings_all hook in PHP to allow customizing it
- #60495 Following “plugins_list”: Add a filter in get_views() in class-wp-plugins-list-table
- #31354 Compound settings confusing with screen readers (checkboxes)
- #61244 The export_wp() function inserts empty <wp:comment> data when get_comment() returns a false or empty value
- #44921 User nicename discovery is slow to return
- #54738 Unable to upload images with URL over API when the image doesn’t have a filetype in the filename
- #58905 Ensure locate_template only loads theme files
- #61890 Handle WP_Term dynamic properties for PHP 8.2
- #61708 Remove the social links pattern
- #52592 PHP warning when the label property is missing from register_block_style
Profile Badge Awards 🎉
No Badges awarded this week.
Read/Watch/Listen 🔗
- Test Team Reps: Call for Nominations.
- A Brand-New Way to Learn WordPress
- WordCamp US 2024: Oregon-a See You There?
- The Road Map post to 6.7 was recently published.
- 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
- The next maintenance release will be WordPress 6.6.2. RC1 is scheduled for Sept 4, and the full release is planned for Sept 10. See the Trac milestone for the release.
- The 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 will be 19.2, scheduled for September 11.
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2024.
2024 Schedule:
- Tuesday, 10 February 2024 at 16:30 GMT+5:30:
<test-chat>in #core-test. - Tuesday, 17 February 2024 at 16:30 GMT+5:30:
<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.