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:
- There are currently 15 open tickets in the 6.5.3 release milestone. There is more information about this release in this post, including the bug scrub schedule and how you can get involved.
- 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/ 18.2 is scheduled for April 24 and will include these issues.
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 to 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:
- #61011 Plugin management: The “Install Now/Activate” button should be a button not a link
- #61012 The mobile layout displays incorrectly when infinite scrolling is activated in the Media Gallery Modal.
- #61015 Having Inline SVG breaks the site
- #61016 Menu Vanishing On Save
- #61017 page_for_posts is automatically reset
- #61018 Block editor color selector displays incorrect color information
- #61022 Twenty Eleven: “Follow Blog” pattern has black text on black background
- #61027 Twenty Twenty-One: Replace front-end JS with Interactivity API
- #61029 Multisite state ‘Delete’ can only have a value of 1or 0. Not 2. So why is 2 mentioned in the code?
- #61030 Reduce font-size of Credits page h1 element for smaller screens
- #61042 Twenty Fifteen Group block color setting not applied to pullquote block.
- #61044 Interactivity API: Debug – Warning about Server Directives Processing errors.
- #61032 List item blocks displays unexpected or invalid content error
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:
- #59493 Bundled themes: remove blank CSS lines
- #49950 Twenty Twenty: with horizontal menu, submenu should be dismissible
- #60435 Twenty Twenty-Four: Footnotes Icon not showing on Mac OS Sonoma 14.3 and Safari 17.3
- #39253 Twenty Seventeen: Head Image Quality Issue
- #56441 Pull quote block border issue in different themes.
- #52294 add_editor_style: Allow replacing a style with an RTL version
- #60645 Add pre-fire hook for cron
- #60479 Remove adminbar skiplink focus fix
- #7813 export function does not preserve encoding
- #60835 Fix and improve handling of uploading of font files
- #60299 Default assignment of `use_ssl` user meta value causes unnecessary DB write.
- #59402 Plugin cannot be uninstalled if uninstall crashes
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
Profile Badge Awards 🎉
No Badges awarded this week.
Read/Watch/Listen 🔗
- Learn more about How WordPress Is Creating a Faster Web
- Episode 77: Let’s Talk About Data Liberation – everything you need to know about
- Merge Proposal: Rollback Auto-Update
- We are currently in the WordPress 6.6 release cycle. The deadline for leaving feedback on this Planning Proposal post has ended, and we expect a release squad to be announced soon. Please leave a comment if you have any updates to share about this.
- WordPress 6.5.3: An upcoming maintenance release
- Hallway Hangout: Let’s chat about what’s next in Gutenberg
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2024.
2024 Schedule:
- Tuesday, 23 April 2024 at 16:30 GMT+5:30:
<test-chat>in #core-test. - Tuesday, 30 April 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.