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
Weekly Testing Roundup 🤠
Weekly update: Test Team Update: 12 August 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:
- #61824 Pages no longer allowed to have same permalink as images
- #61826 Inline Padding Issue with Full-Width (alignfull) child Group in WordPress 6.6
- #61832 Can’t edit reusable blocks – weird interface scroll error
- #61833 Post titles in Bulk Edit should show decoded HTML
- #61828 Global Styles: Refactor wp_add_inline_style() to use HTML API
- #61838 Uncaught TypeError in multiple REST API endpoints from a single bug
- #61843 REST API endpoint /wp-json/wp/v2/categories returns 500 instead of 400
- #61837 Uncaught TypeError in wp/v2/posts/{id} endpoint
- #61850 Link option Window hidden behind editor edge frame
- #61842 Uncaught TypeError in /wp-json/wp/v2/menu-items REST API POST operation
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:
- #59602 Twenty Fifteen: typography issues in the editor with Table and Calendar blocks and captions
- #58905 Ensure locate_template only loads theme files
- #31354 Compound settings confusing with screen readers (checkboxes)
- #61834 class-wp-site-health-auto-updates.php triggers error when basedir restrictions in effect
- #50493 more detailed notice for register_rest_route
- #61835 Update jQuery Color library
- #59919 Twenty Sixteen : PullQuote block Typography option is not working properly
- #55975 Twenty Twenty: Pullquote Block font-size issue
- #50317 Twenty-Twenty: Image Block Caption alignment is not centered on mobile version
- #46080 Twenty Seventeen: Pullquote Block – “Write citation…” Text color not working at frontend
- #61672 Twenty Twelve: navigation block submenus are cut off
- #53681 Twenty Nineteen: reduce bottom margin for Audio block
- #55410 Update spacer block markup in patterns/templates registered by Twenty Twenty-Two and Core
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
- #52592 PHP warning when the label property is missing from register_block_style
- #61181 Implement a filter to customize output on _block_bindings_post_meta_get_value
- #57379 A Way to Disable Export Theme
- #54648 Improve filter to enable setting quality for each subsize image
6.7 Related issues need testing
The following 6.7 tickets need testing those are having patches:
- #59602 Twenty Fifteen: typography issues in the editor with Table and Calendar blocks and captions
- #58905 Ensure locate_template only loads theme files
- #31354 Compound settings confusing with screen readers (checkboxes)
- #61834 class-wp-site-health-auto-updates.php triggers error when basedir restrictions in effect
- #54738 Unable to upload images with URL over API when the image doesn’t have a filetype in the filename
- #61835 Update jQuery Color library
Profile Badge Awards 🎉
No Badges awarded this week.
Read/Watch/Listen 🔗
- 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 next maintenance release will be 6.6.2 and will likely be released at the end of the month, likely August 26 with RC1 the week before.
- 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/ 19.0 is scheduled for August 14. RC1 was released on August 7.
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2024.
2024 Schedule:
- Tuesday, 13 August 2024 at 16:30 GMT+5:30:
<test-chat>in #core-test. - Tuesday, 20 August 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.