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:
- Help test WordPress 6.6 – We are currently looking for volunteers who can help us in testing the upcoming version.
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:
- #61503 Hook parent_file
- #61513 Attention points in Pentest
- #61515 wp_audio_shortcode() outputs invalid HTML
- #61527 Twenty Sixteen: Verse Block Font family is different in editor & frontend
- #61536 Add opacity as an allowed attribute to safecss_filter_attr()
- #61540 WordPress html block breaks scripts.
- #61525 Plugins page keeps making HTTP requests for plugin dependencies which are not in the WordPress Plugin Directory
- #61517 New swap template feature make website not repond
- #61543 Add a description key to i18n theme.json style schema
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
- #61287 Twenty Sixteen : Code Block Background color is not reflecting in frontend
- #32597 mediaelement.js high CPU usage triggered by the buffering CSS animation
- #58902 add_query_arg() should esc_url_raw() REQUEST_URI
- #59521 Issue with update_post_thumbnail_cache if using get_posts
- #60261 Fatal error with invalid charset specified in Trackback
- #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
- #61117 Guard condition in `delete_temp_backup()` shouldn’t return early
- #61055 wp_update_plugins irregular transient handling.
- #45993 Twenty Nineteen: Image aligncenter inside column is broken
- #60291 Support Lossless WebP in WP_Image_Editor_GD
- #51019 convert_smilies() fails on large tags
- #44958   character in title generates a permalink (and slug) with space
- #61186 Twenty Nineteen: Apply center alignment to Archives and Categories List blocks in the editor
- #53314 Add Themes page in UI issue
- #53158 Twenty Twenty: Pullquote block editor styling does not match front
- #53323 Place Hello Dolly in containing folder
- #60835 Fix and improve handling of uploading of font files
- #31823 Add ESLint integration
- #61507 Twenty Nineteen: Fix font size and citation display for Pullquote block
6.6 Related issues need testing
The following 6.6 tickets need testing those are having patches:
Profile Badge Awards 🎉
No Badges awarded this week.
Read/Watch/Listen 🔗
- WordPress 6.6 RC1 was released on June 25. We are now in a hard string freeze. Note that the
dev-feedbackanddev-reviewedworkflow is required prior to committing to the 6.6 branch (handbook reference). - WordPress 6.5.5, a security release, was shipped on June 24.
- Gutenberg 18.6.1 was released on June 25.
- We are currently in the WordPress 6.6 release cycle. The WordPress 6.6 RC2 release is scheduled for next Tuesday, July 2. Please review this post for an update about the Release CandidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. Phase.
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2024.
July 2024 Schedule:
- Tuesday, 2 July 2024 at 16:30 GMT+5:30:
<test-chat>in #core-test. - Tuesday, 9 July 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.