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:
- Test Scrub Schedule for WordPress 6.7
- Bug Scrub Schedule for WordPress 6.7
- Help Test 6.7 will be coming soon!
- Last day to Nominate for Make WordPress Test team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.!
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:
- #62099 Vimeo Element Alignment not working properly
- #62104 Multisite triggers UPDATE queries on _sitemeta of almost 150k character
- #62111 The cache of the embed seems weird
- #62113 Favicon – Loading speed problem
- #62120 Removing Global Styles
- #62131 WP Intreractivity API calculated classes aren’t added
- #62135 Custom Post Type feed rewrites not generated when has_archive is false
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:
- #57789 Make theme.json related caches persistent
- #58905 Ensure locate_template only loads theme files
- #61154 Fix the ‘attributes’ dynamic property in WP_Block
- #61890 Handle WP_Term dynamic properties for PHP 8.2
- #52592 PHP warning when the label property is missing from register_block_style
- #41155 Theme Details dialog hides admin sidebar sub-menu navigation
- #59329 Firefox gets “ReferenceError: Â is not defined” in unminified moxie.js
- #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
- #61765 Twenty Twelve: The large quote pattern does not use a quote block
- #31354 Compound settings confusing with screen readers (checkboxes)
- #62016 The .json files with theme translations are loaded only if they are present in the plugins path
- #60291 Support Lossless WebP in WP_Image_Editor_GD
- #61366 A password change should not destroy a user’s session data.
- #61265 Add class name for block variations
- #55974 Bundled theme: Add support for border options
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:
- #44958   character in title generates a permalink (and slug) with space
- #57379 A Way to Disable Export Theme
- #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
6.7 Related issues need testing
The following 6.7 tickets need testing those are having patches:
- #43936 Settings: Warn when open registration and new user default is privileged
- #44921 User nicename discovery is slow to return
- #52592 PHP warning when the label property is missing from register_block_style
- #41155 Theme Details dialog hides admin sidebar sub-menu navigation
- #59329 Firefox gets “ReferenceError: Â is not defined” in unminified moxie.js
- #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
- #61765 Twenty Twelve: The large quote pattern does not use a quote block
- #31354 Compound settings confusing with screen readers (checkboxes)
- #62016 The .json files with theme translations are loaded only if they are present in the plugins path
- #60291 Support Lossless WebP in WP_Image_Editor_GD
- #54738 Unable to upload images with URL over API when the image doesn’t have a filetype in the filename
- #55974 Bundled theme: Add support for border options
Profile Badge Awards 🎉
Congratulations to @q0rban, @n8finch, @jessedyck, @yukiukechan. Thanks for helping the Test team at WCUS Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/!
Read/Watch/Listen 🔗
- WordPress 6.7 Release Party Schedule
- 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 one week away. The Road Map post can be found here.
- What’s new in Gutenberg 19.3
- PDX + WCUS 2024: A Recap post
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2024.
2024 Schedule:
- Tuesday, 1 October 2024 at 16:30 GMT+5:30:
<test-triage>in #core-test. - Tuesday, 8 October 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.