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:

• 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/ 21.0 RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. is released and ready for testing. Please check this changelog for more information.

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:

• #63513 Twenty Twenty-Five: Copy for query loop results is confusing on the home page
• #63522 Warnings related to get_queried_object returning null
• #63531 Category dropdown does not meet WCAG 2.2 A on windows and some linux systems
• #63528 Mouse scroll wheel scrolls whole Post while editing when attempting to scroll through autocomplete pop-up of internal Posts
• #63518 get_blog_details( get_all: false ) not working as expected
• #63540 Dashboard has accessibility issue regarding insufficient contrast ratio.
• #63541 TinyMCE scripts not loaded when WYSIWYG fields are present in metaboxes with Gutenberg enabled

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:

• #41978 `_delete_all_data()` does not delete attachment files
• #60495 Following “plugins_list”: Add a filter in get_views() in class-wp-plugins-list-table
• #17904 Multisite has more restrictions on user login character set
• #56153 Query loop block with full width and having template of image, title and date has full width issue in editor side in twenty twenty theme.
• #42910 Default Post Format doesn’t apply on post created from Quick Draft

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/preface.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 tickets need PHPUnit tests built to accompany their respective patches:

• Same as above

Profile Badge Awards 🎉

We are processing the badges to all the eligible contributors who participated and contributed on WCEU Contributors day. Thank you for your patience! 🙇‍♀️

Read/Watch/Listen 🔗

• WCEU 2025 : Test Team Contributor Day Recap
• WCEU 2025: A Community Celebration in the Swiss Sun
• What’s new in Gutenberg 20.4 and 20.5?
• AI Team has their first meeting and here here is the recap
• The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is working on a squad for future minor releases. A release squad for 6.8.2 should be announced soon. Follow #6-8-release-leads for updates.
• A Criteria for Creating or Migrating Repositories under the WordPress GitHub Organization was published. Please check it out for guidelines and more.
• Automattic: Open Horizons Scholarship
• Gutenberg 21.0 RC is released.

Upcoming Meetings 🗓

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

2025 Schedule:

• Wednesday, 11 June 2025 at 21:30 GMT+5:30:  <test-triage> in #core-test.
• Wednesday, 18 June 2025 at 21: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

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: Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings

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:

• #63438 Admin: Standardize accordions UI on Menus screen and in Customizer
• #63437 [v6.8.1] Unsupported operand types: bool & string in wp_privacy_anonymize_ip on line 8234
• #63447 Low Contrast Ratio in Footer Separator of “WordPress Events and News” Widget
• #63450 Race condition for transient with no expiration and object cache active
• #63451 Flag emoji rendering issue on Windows environment
• #63449 Low color contrast for <code> elements in description text on Settings > General page
• #63455 Twenty Sixteen: Quote block negative margin
• #63453 Inconsistent confirmation for deleting taxonomy term (Single vs Bulk Action)

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:

• #63135 Testing and Debugging WP_Mail related topics
• #63448 Image quality significantly degrades for resized PNGs with transparency in WordPress 6.8.

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/preface.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 tickets need PHPUnit tests built to accompany their respective patches:

• #61890 Handle WP_Term dynamic properties for PHP 8.2
• #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
• #44958 &nbsp character in title generates a permalink (and slug) with space
• #39540 NOT EXISTS meta condition doesn’t work if meta has NULL value.
• #36428 Weird default value of option ‘default_link_category’
• #56311 Week query variable is not being sanitized correctly
• #45140 REST API: Increase upper bound allowed on per_page argument

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

• Gutenberg 20.8 is now available
• The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is planning to set up a release squad, a plan/scope and a schedule for 6.8.2 (and beyond)
• In case you if you are interested, A Month in Core – April 2025 is out.
• The next major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality. things are in progress and can be found here.
• WCEU is around the corner. Please check out the schedule.

Upcoming Meetings 🗓

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

2025 Schedule:

• Wednesday, 21 Mayy 2025 at 21:30 GMT+5:30: <test-chat> in #core-test.
• Wednesday, 28 May 2025 at 21: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.

#core-test

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: Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings

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:

• #63406 Lack of mutex for query object values like is_category and is_author can result in warnings
• #63426 wptexturize breaks markup
• #63429 URL transliteration functionality to Latin

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:

• #17019 add hooks for Media Library attachment counts
• #29849 Better human_time_diff()
• #34986 Add Upgrade Notice for Themes
• #36710 Symlinked directories should not be deleted recursively
• #39827 notice in wp-includes/canonical.php:392
• #44958 &nbsp character in title generates a permalink (and slug) with space
• #50683 Parse content for shortcodes instead of using regex
• #52939 Frontend toolbar CSS conflict with some themes
• #53816 Overview: Refactor the widgets read/write logic
• #58183 PHP notice when accessing Customizer with a classic theme without widgets
• #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
• #58722 Fix RTL display in Optional grouping on Permalinks Settings page
• #58763 Inconsistent add/get/update/delete_post_meta() functions leads to deleting post metadata.
• #58902 add_query_arg() should esc_url_raw() REQUEST_URI
• #61890 Handle WP_Term dynamic properties for PHP 8.2
• #63135 Testing and Debugging WP_Mail related topics
• #32597 mediaelement.js high CPU usage triggered by the buffering CSS animation

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/preface.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 tickets need PHPUnit tests built to accompany their respective patches:

• #51006 Add a mechanism for accessible tooltips in core
• #55358 Passing int term term_exists parent param not respected
• #33821 redirect_canonical does not consider port in $compare_original
• #17904 Multisite has more restrictions on user login character set
• #39827 notice in wp-includes/canonical.php:392
• #41445 post_parent can prevent media from embedding correctly
• #44958 &nbsp character in title generates a permalink (and slug) with space
• #48689 PHP warnings after updating to WP 5.3: ftp_nlist() and ftp_pwd() expect missing parameters
• #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
• #61100 Fix capability error in bulk role removal when editing site users in network admin
• #61330 Plugin Dependencies: Refresh plugin-install.php instead of redirecting on activation

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

• WordPress 6.8.1 Maintenance Release
• WordPress Campus Connect Expands
• The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is planning to set up a release squad, a plan/scope and a schedule for 6.8.2 (and beyond)
• Call for 6.8.x Release Managers is still open. Anyone interested to lead a 6.8.x release can drop a comment in this P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. post.

Upcoming Meetings 🗓

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

2025 Schedule:

• Wednesday, 14 May 2025 at 21:30 GMT+5:30:  <test-triage> in #core-test.
• Wednesday, 21 May 2025 at 21: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

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: Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings

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:

• #63365 Sticky Posts Appear at the Top of Every Page in the Query Loop Block
• #63372 Tags page UI inconsistencies when adding or deleting tags
• #63384 Content-Disposition ‘inline’ filenames not respected by download_url()
• #63386 Twenty Seventeen – Lastes post block having issue in alignnment.
• #63392 Anteprima da editor articolo

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:

• #61941 Adding app.screencast.com as an oEmbed provider
• #48345 Add Caps lock message to login screen

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/preface.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 tickets from 6.8.2 need PHPUnit tests built to accompany their respective patches:

• No tickets found

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

• For now, 6.8 is identified as the last major release of the year
• WordPress 6.8.1 Maintenance Release was released on April 30, 2025 
• At the moment while writing this post, there are 9 tickets in the 6.8.2 milestone on Trac. Bug fixes currently located in milestone 6.9 can probably start to be moved to 6.8.x milestones, but 6.8.2 will most probably still be focused on remaining issues/regressions found on 6.8.

Upcoming Meetings 🗓

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

2025 Schedule:

• Wednesday, 07 May 2025 at 21:30 GMT+5:30: <test-chat> in #core-test.
• Wednesday, 14 May 2025 at 21: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.

#core-test

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:

• WordPress 6.8.1 RC1 is now available

Weekly Testing Roundup 🤠

Weekly update: Test Team Update: 28 April 2025

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:

• #63332 wp_editor_settings filter hook not working as expected in WordPress Admin
• #63334 `switch_to_locale()` overwrites custom object types for core taxonomies
• #63338 Image distortion since WordPress 6.8, previously correct image now blurry
• #63330 PHP deprecated error in meta.php on line 1298
• #63342 wp-admin/options.php page crashes when options or cache data are too large
• #63341 siteurl and home fields not disabled in wp-admin/options.php when defined in wp-config.php
• #63344 Twenty Seventeen: Inconsistent Search Block Input Padding
• #63350 Twenty Fourteen :- The Search block design appears misaligned when the button inside is enabled.
• #63348 Missing “Create Date” on Draft Products
• #63347 Twenty Fourteen: Table and Calendar blocks do not apply font size from user settings
• #63351 Incorrect usage of esc_attr() for URL escaping
• #63353 Invalid type false for permalink_structure property
• #63365 Sticky Posts Appear at the Top of Every Page in the Query Loop Block
• #63361 Remove unnecessary semicolon form switch case in atomlib.php file
  

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:

• #60770 TimeZone select box compatibility with RTL directions
• #63135 Testing and Debugging WP_Mail related topics
• #58836 Remove IE specific checks from more default themes
• #54346 Slow SQL queries fetching posts from specific categories
• #51006 Add a mechanism for accessible tooltips in 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/preface.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 tickets need PHPUnit tests built to accompany their respective patches:

• Same as above

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

• WordPress 6.8.1 Release Schedule
• WordPress 6.8.1 RC1 is now available
• Call for 6.8.x Release Managers
• WordPress 6.9 Development Cycle

Upcoming Meetings 🗓

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

2025 Schedule:

• Wednesday, 30 April 2025 at 21:30 GMT+5:30: <test-triage> in #core-test.
• Wednesday, 07 May 2025 at 21: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

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:  Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings

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:

• #63280 wp-settings- and wp-settings-time- cookies set on every admin request if user settings empty
• #63283 Bug in version check returned values from api.wordpress.org
• #63282 Inconsistent post name processing
• #63292 atom_enclosure doesn’t always get MIME type – inconsistency with rss_enclosure
• #63291 Twenty Twenty-One: fix text color in starter content
• #63290 Cover block overlays didn’t display after 6.8 update—every page had to be resaved
• #63306 There is already 20px padding on the right side, and an additional 2px margin is being applied, making the total spacing 22px..
• #63305 On mobile devices, the left and right padding or margin in the General Settings section of the dashboard are not equal, which doesn’t look good from the user’s perspective.
• #63296 array_intersect_key() fatal error in wp_render_layout_support_flag() due to invalid string parentLayout in core/social-links block
• #63308 tinymce cache key should be updated
• #63312 Application Passwords panel disappears when any plugin is active
• #63309 Twenty Fifteen: Table block border not appear properly.
• #63319 Site no longer finds the home page when opening – My bad I’ve done something
• #63307 REST API: Returns incorrect post when querying by slug if sticky posts exist
• #63316 [E_WARNING] Undefined array key “host” in wp-includes/canonical.php on line 717
  

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:

• #63275 Twenty Fourteen: Sticky menu problem

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/preface.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 tickets need PHPUnit tests built to accompany their respective patches:

• No tickets found

Profile Badge Awards 🎉

Profile badges awarded to Manoj Maharrshi

Read/Watch/Listen 🔗

• WordPress 6.8 “Cecil” is released on 15th April
• WordPress 6.8 Source of Truth
• Call for 6.8.x Release Managers
• WP_Query changes in WordPress 6.8
• WordPress 6.8 performance improvements
• WordCamp Europe 2025: Sali, Basel!
• A New Cadence for WordPress Core

Upcoming Meetings 🗓

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

2025 Schedule:

• Wednesday, 23 April 2025 at 21:30 GMT+5:30: <test-chat> in #core-test.
• Wednesday, 30 April 2025 at 21: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.

#core-test

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:

• Roadmap to 6.8
• Help Test WordPress 6.8
• How to Contribute to WP 6.8 Release Party

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:

• #63252 $tax_url with no path not accounted for in /wp-includes/canonical.php
• #63254 Introduce development mode for block editor styles
• #63260 Long user display names overflow in media modal (grid view)
• #63259 Replace zxcvbn with zxcvbn-ts
• #63273 Fatal due to superglobal $_POST modification with invalid int type
• #63276 Twenty Fourteen: Content width in block editor
• #63263 check if exists before accessing object properties of $post->comment_count
• #63271 Multisite (Subdirectory) URL Corruption in Page Content (Language Site)

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:

• #60770 TimeZone select box compatibility with RTL directions

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/preface.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 tickets need PHPUnit tests built to accompany their respective patches:

• No tickets found

Profile Badge Awards 🎉

Profile badge assigned to Masud Rana

Read/Watch/Listen 🔗

• WordPress 6.8 RC3 is now available for testing.
• Ahead of it, there will be a Dry Run on Monday, April 14, 2025. A detailed overview of the release schedule for WordPress 6.8 can be found here. The article also includes information about the individuals assigned to each release party.
• The general release of WordPress 6.8 will be available on Tuesday, April 15, 2025.
• The Gutenberg 20.7-RC is ready for testing.
• WordPress 6.8 Field Guide
• What’s new for developers? 

Upcoming Meetings 🗓

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

2025 Schedule:

• Wednesday, 16 April 2025 at 21:30 GMT+5:30: <test-chat> in #core-test.
• Wednesday, 23 April 2025 at 21: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.

#core-test