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:

• Test Scrub Schedule for WordPress 6.7
• Bug Scrub Schedule for WordPress 6.7

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:

• #62024 wp_kses_post incorrectly escapes “<” attributes values
• #62028 Paragraph margins not honored (in the backend) when global blockspacing is set to zero (new issue in 6.6.1)
• #62030 Can’t Access Some Block Templates in Classic Themes
• #62044 WP allows to inject random strings into archive page urls, still returning 200
• #62046 `render_block_context` filter works differently on top-level vs. inner blocks
• #62051 Pagination and custom post types that have a hierarchy
• #62052 Suggestions prompt doesn’t always appear after publishing a post
• #62054 Problems on my Genesis Framework after WordPress update 6.62
• #62049 Italics HTML tags in Post Titles are Being Converted to HTML Entities
• #62038 Issue with is_email() and sanitize_email()

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:

• #10275 Filter logic has been put into the template loader while it not belongs there.
• #31354 Compound settings confusing with screen readers (checkboxes)
• #34353 redirect_canonical() – Undefined indexes ‘host’ and ‘scheme’
• #52696 Add a way to determine whether a translation exists
• #44610 Allow Youtube-Player to use youtube-nocookie.com URLS to avoid setting cookies.
• #54516 Full site editing/REST-API: modify permission checks to use post type.
• #44921 User nicename discovery is slow to return
• #52294 add_editor_style: Allow replacing a style with an RTL version
• #54304 Expose menu data public in Menus REST API
• #48693 Silence ini_set caused error or check if function_exists first
• #62014 Editor: Add a ‘format’ parameter to query to enable filtering post formats in the Query Loop block
• #61265 Add class name for block variations

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. http://php.net/manual/en/intro-whatis.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:

• #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
• #44958 &nbsp character in title generates a permalink (and slug) with space
• #57379 A Way to Disable Export Theme
• #54648 Improve filter to enable setting quality for each subsize image
• #61308 Return `post_types` field in templates REST API

6.7 Related issues need testing

The following 6.7 tickets need testing those are having patches:

• #10275 Filter logic has been put into the template loader while it not belongs there.
• #31354 Compound settings confusing with screen readers (checkboxes)
• #44921 User nicename discovery is slow to return
• #52294 add_editor_style: Allow replacing a style with an RTL version
• #54304 Expose menu data public in Menus REST API
• #62014 Editor: Add a ‘format’ parameter to query to enable filtering post formats in the Query Loop block
• #61265 Add class name for block variations

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

• WordPress 6.2.2 was released this week.
• 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.: 6.7 – 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 Road Map post can be found here.
• Next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: 6.6.3 – Following the recent WordPress 6.6.2 release, the next maintenance release (if needed) will be WordPress 6.6.3. There were not updates shared in the meeting.
• Next 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/ release: 19.2 – The next Gutenberg release will be 19.2, scheduled for September 11 (this release occurred after the meeting).
• WordPress Contribution Health Dashboards: An Experiment

Upcoming Meetings 🗓

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

2024 Schedule:

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

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:

• Test Scrub Schedule for WordPress 6.7
• Bug Scrub Schedule for WordPress 6.7

Weekly Testing Roundup 🤠

Weekly update: Test Team Update: 9 September 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:

• #61969 Post guid for custom post type being modified
• #61970 Fatal error: Attempt to read property “ID” on null in /src/wp-includes/rest-api/endpoints/class-wp-rest-autosaves-controller.php
• #61978 Managing Dynamic Search, Category Filtering, and Pagination for Bulk Patterns
• #61984 Favicon • multiple of 48×48 and not 512×512 as WP suggests
• #61991 Inconsistent file name after cropping from Site Icon
• #61996 Slug Conflict When a Published and Draft Page Share post_name
• #62003 User_Query cache triggers fatal error by ignoring ‘fields’ query var
• #61983 Part of `wp_generate_attachment_metadata` missing `avif` extension
• #61997 Undefined array key “height” and “width” in wp-includes/media.php on line 1241 and 1242
• #62007 PHP warning in wp-includes/canonical.php when accessing custom feed with specific permalink structure
• #62009 use strict comparison in wp-admin/includes/media.php
• #62013 the post_name field is not taken into account
• #62010 Twenty Twelve: Add title size is very low.

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:

• #54304 Expose menu data public in Menus REST API
• #61264 Move default rendering mode setting to block_editor_settings_all hook in PHP to allow customizing it
• #60495 Following “plugins_list”: Add a filter in get_views() in class-wp-plugins-list-table
• #31354 Compound settings confusing with screen readers (checkboxes)
• #61244 The export_wp() function inserts empty <wp:comment> data when get_comment() returns a false or empty value
• #44921 User nicename discovery is slow to return
• #58905 Ensure locate_template only loads theme files
• #61890 Handle WP_Term dynamic properties for PHP 8.2
• #61708 Remove the social links pattern
• #52592 PHP warning when the label property is missing from register_block_style
• #52696 Add a way to determine whether a translation exists

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. http://php.net/manual/en/intro-whatis.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 &nbsp character in title generates a permalink (and slug) with space
• #54648 Improve filter to enable setting quality for each subsize image
• #57379 A Way to Disable Export Theme

6.7 Related issues need testing

The following 6.7 tickets need testing those are having patches:

• #61264 Move default rendering mode setting to block_editor_settings_all hook in PHP to allow customizing it
• #60495 Following “plugins_list”: Add a filter in get_views() in class-wp-plugins-list-table
• #31354 Compound settings confusing with screen readers (checkboxes)
• #61244 The export_wp() function inserts empty <wp:comment> data when get_comment() returns a false or empty value
• #44921 User nicename discovery is slow to return
• #54738 Unable to upload images with URL over API when the image doesn’t have a filetype in the filename
• #58905 Ensure locate_template only loads theme files
• #61890 Handle WP_Term dynamic properties for PHP 8.2
• #61708 Remove the social links pattern
• #52592 PHP warning when the label property is missing from register_block_style

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

• Test Team Reps: Call for Nominations.
• A Brand-New Way to Learn WordPress
• WordCamp US 2024: Oregon-a See You There?
• The Road Map post to 6.7 was recently published.
• 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
• The next maintenance release will be WordPress 6.6.2. RC1 is scheduled for Sept 4, and the full release is planned for Sept 10. See the Trac milestone for the release.
• The next 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/ release will be 19.2, scheduled for September 11.

Upcoming Meetings 🗓

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

2024 Schedule:

• Tuesday, 10 February 2024 at 16:30 GMT+5:30: <test-chat> in #core-test.
• Tuesday, 17 February 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.

#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:

• Test Scrub Schedule for WordPress 6.7
• Bug Scrub Schedule for WordPress 6.7

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:

• #61930 size_format(): Inconsistent behaviour when zero bytes are passed
• #61934 ctrl+shift+v – does not work in the editor
• #61928 Metaboxes overlap block editor’s edit link popup
• #61949 Do not call getimagesize() against non-existent files
• #61940 `upgrader_process_complete` runs when no plugins selected to upgrade
• #61953 aspect-ratio setting for image in overwritten pattern not working
• #61960 Heartbeat API: consider changing the min allowed time
• #61937 WP_Theme_JSON_Schema::migrate removes data when version is missing
• #61962 error.log – cant figure out issue with Google Search..

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:

• #61919 Ctrl + Enter with focus on “Edit your profile” within the comment form tries to submit form
• #60835 Fix and improve handling of uploading of font files
• #32597 mediaelement.js high CPU usage triggered by the buffering CSS animation
• #61117 Guard condition in `delete_temp_backup()` shouldn’t return early
• #61890 Handle WP_Term dynamic properties for PHP 8.2
• #60892 About Page: `text-wrap: balance;`adds unintended new lines in Japaneese
• #55974 Bundled theme: Add support for border options
• #55410 Update spacer block markup in patterns/templates registered by Twenty Twenty-Two and Core
• #61951 TT3 and TT4: make template heading text translatable
• #60184 Publication date 01/01/1970 is refused
• #53323 Place Hello Dolly in containing folder

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. http://php.net/manual/en/intro-whatis.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 &nbsp 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
• #54648 Improve filter to enable setting quality for each subsize image
• #57379 A Way to Disable Export Theme

6.7 Related issues need testing

The following 6.7 tickets need testing those are having patches:

• #61919 Ctrl + Enter with focus on “Edit your profile” within the comment form tries to submit form
• #43936 Settings: Warn when open registration and new user default is privileged
• #56780 shortcode block in block-based template part in a classic theme does not get expanded
• #60835 Fix and improve handling of uploading of font files
• #32597 mediaelement.js high CPU usage triggered by the buffering CSS animation
• #61117 Guard condition in `delete_temp_backup()` shouldn’t return early
• #61890 Handle WP_Term dynamic properties for PHP 8.2
• #55974 Bundled theme: Add support for border options
• #61951 TT3 and TT4: make template heading text translatable
• #60184 Publication date 01/01/1970 is refused
• #53323 Place Hello Dolly in containing folder

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

• Test Team Reps: Call for Nominations
• WordPress Contributor Mentorship Program Cohort #3 (2024 Q4): Call for Mentees & Mentors
• 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 WordPress 6.6.2. RC1 is scheduled for Sept 4, and the full release is planned for Sept 10. See the Trac milestone for the release.
• The last 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/ release was 19.1, which was released on August 28.

Upcoming Meetings 🗓

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

2024 Schedule:

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

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