Week in Test: July 8, 2024

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: 08 July 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:

• #6155 Template contents are wiped out on rename
• #61556 Fix error malware
• #61559 Noindex x roboto tags
• #61566 Wrong Dates on Release Archive Page
• #61577 health check count display bug
• #61575 Node Modules in sub-directories not getting ignored while exporting the theme
• #61579 WordPress 6.6 RC2 Issues report – with Customizer Redirect Sections in WordPress RC2
• #61580 WP_REST_Templates_Controller::get_wp_templates_author_text_field() doesn’t always return value
• #61582 Cannot Insert Images in WordPress 6.5.5
• #61558 oEmbed: Support non-dot-com Pinterest URLs

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:

• #55974 Bundled theme: Add support for border options
• #42598 Twenty Seventeen: Sticky header offset issue
• #60374 Twenty Sixteen: Navigation block inherits colors from button styles
• #45714 Allow all valid email formats when editing accounts in the dashboard
• #61571 Twenty Fifteen: Code block font family is different in iframe editor
• #61562 Twenty Twenty-One Theme: Latest post block does not appear selected text color on editor & front end sides.
• #30575 Twenty Fourteen: Submenu items on dropdown menus nearly impossible to select on some Android mobile tablets
• #61140 Multiple themes: Verse block font family is different in front-end

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

• Learning Pathways: Discover how Learning Pathways can guide you through your WordPress journey with clarity and purpose.
• We are currently in the WordPress 6.6 release cycle. See the Roadmap Post for more information about what is planned for this release. The 6.6 RC3 is scheduled for Tuesday, July 9.
  • WordPress 6.6 RC2 was released yesterday, on July 2. We are still in a hard string freeze. Note that the dev-feedback and dev-reviewed workflow is required prior to committing to the 6.6 branch (handbook reference).
• Gutenberg 18.7 was released earlier today.
• What would you like to see in the next default WordPress theme?
• WordPress 6.7 Planning Proposal & Call for Volunteers

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings held for 2024.

2024 Schedule:

• Tuesday, 9 July 2024 at 16:30 GMT+5:30: <test-triage> in #core-test.
• Tuesday, 16 July 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.

#core-test