Week in Test: 15 October 2022

Hello and welcome to 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 | 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.1 🌟

6.1 RC1 was released on Tuesday, and is available for testing. See the 6.1 Call for Testing post for a rundown of major new features and tips for testing. Prereleases of 6.1 will be available until its official release the first week of November, so please test and provide feedback before 1 November 2022.

Call for Testing: Plugin Dependencies

Have you ever gotten stuck installing a fancy new pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party, and then spent two days in support forums just to find out that you needed to install another required plugin to get it working? Or are you a plugin author who would like to bundle plugins for a smoother setup experience for your users? Plugin Dependencies is here to help! See the Plugin Dependencies call for testing, and provide feedback before 1 December 2022. #feature-project

Weekly Testing Roundup 🤠

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:

  • #56768: Base64-encoded images render in editor, but not frontend.
  • #56789: Toolbar: .screen-reader-shortcut does not have background color until focused.

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:

  • #55990: Twenty Twenty: Pullquote BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.: Add Citation Text Color Issue.
  • #48244: script-loader.php: Use _n() when multiple results found.
  • #56388: Remove unnecessary comments from compiled block styles.
  • #56802: Query: Post IDs cached for search and other ‘LIKE’ queries are unreachable.

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

  • #47164: map_deep in formatting.php does not handle null-byte.
  • #55290: Not all image edits are applied to all subsizes.
  • #56340: Resolve PHP 8.1 E_DEPRECATED in PasswordHash::gensalt_blowfish.

Profile Badge Awards 🎉

Thank you to the following contributors who have earned the Test Contributor profile badge. These users have participated in WordPress 6.1 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./RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. release parties, as well as performed general testing over the past few weeks:

Read/Watch 📖

Upcoming Meetings 🗓

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.

#build-test-tools, #core-test, #feature-plugin, #feature-project

Week in Test: 23 September 2022

Hello and welcome to Week in Test, the place where contributors of any skill level can find opportunities to contribute to WordPress through testing. For even more talk about testing, join the Test Team over in #core-test.

Jump to: Calls for Testing | Weekly Testing Roundup | Profile Badge Awards | Read/Watch | 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 Help Test WordPress 6.1 (get involved)

You’ve heard all the “cool kids” 😎 talking about it: 6.1 Beta 1 was released on Wednesday, and is available for testing. See the 6.1 Call for Testing post for a rundown of major new features and tips for testing. Prereleases of 6.1 will be available until its official release the first week of November, so 🗓please provide feedback before 1 November 2022.

FSE Program Testing Call #17:
Guiding the 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/ Gallery (get involved)

Take on the roll of an intrepid website owner who makes the switch from Twenty Twenty to Twenty Twenty-Two. Discover blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. site editing by working with navigation, headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. and footer patterns, categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. templates, and more! Includes a testing option for users without a dev environment. 🗓Please leave feedback by 6 October 2022. #fse-outreach-program

Would you like to help organize calls for testing? Help work toward a bug-free WordPress and become a testing facilitator.

Weekly Testing Roundup 🤠

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:

  • #56591: Error decoding JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. with TT2 theme on ddev installation.
  • #56600: Twenty Ten: Pullquote block text is not reflected in editor.

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:

  • #56599: “All” view not selected for views of custom post typeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept.. More testing needed for plugins that extend the WP_Posts_List_Table class.
  • #48244: Expand translation options between singular and plural results (_n).
  • #55290: Not all image edits are applied to all subsizes.

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

  • #21650: Replace serialize() with print_r() in stats() function in wp-includes/cache.php.
  • #55448: WP_Widget_Block outputs empty container if widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. has no output.
  • #56340: PHP 8.1 E_DEPRECATED in PasswordHash::gensalt_blowfish.

Profile Badge Awards 🎉

Congrats and thank you to the following contributors who have earned the Test Contributor profile badge:

Read/Watch 📖

Upcoming Meetings 🗓

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.

Special thanks to @annezazu and @laurlittle for review of this post.

#build-test-tools, #core-test

Week in Test: 8 September 2022

Welcome to another exciting installment of Week in Test, where contributors of any skill level can find opportunities to contribute testing to the WordPress project. You can find the Test Team in #core-test.

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 over the next couple of weeks:

Weekly Testing Roundup 🤠

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:

  • #56505: Un-necessary Language Files are Installed.
  • #56519: Inner blocks serialization bug in serialize_block function.
  • #56490: wp-cron.php using count() on null.

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:

  • #55721: Visually align important data on the add new plugins screen.
  • #47513: JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. TypeError when Video Playlists use native video elements.
  • #56468: sanitize_option() does not handle deprecated timezones correctly.

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

  • #56325: Some blocks’ RTL stylesheets not loading when RTL language is set.
  • #55448: WP_Widget_Block outputs empty container if widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. has no output.
  • #55005: Improve PHP performance for block.json files.

Profile Badge Awards 🎉

Thank you to the following contributors who earned the Test Contributor profile badge by participating in the WordPress 6.0.2 release party:

Read/Watch 📖

Upcoming Meetings 🗓

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.

Props @laurlittle and @annezazu for their time to review this post.

#build-test-tools, #core-test

Week in Test: 16 August 2022

Welcome back to Week in Test, where contributors of any skill level can find a handy list of links and opportunities to test WordPress. Join the Test Team in #core-test for questions and thoughtful discussion.

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:

  • #56367: Twenty Seventeen: List blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. padding in Editor does not match the correct frontend style.
  • #56363: “Generate password” button on Add New User screen does not regenerate password on first click.

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:

  • #52584: Metaboxes fail to save after heartbeat/login timeout and subseqent reauthentication. This ticket is planned for 6.1.
  • #54546: Fatal error during update from 5.8.2 to 5.9. Relates to Requests 2.0, slated for 6.1 release.
  • #42619: Check open_basedir setting before parsing directories during autoupdate.
  • #56194: Twenty Twenty: text-transform setting on H6 heading doesn’t match between Editor and frontend.

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

  • #56350: Allow exact text searches in REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/..
  • #56340: PHP 8.1: E_DEPRECATED from PasswordHash::gensalt_blowfish.
  • #56389: Make wp_required_field_indicator and wp_required_field_message filterable. Includes test suggestions to get started.
  • #56349: Update WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. functions to support multiple MIME types (such as WebP). Dev code review is still in progress, so suggest unit tests be submitted to current PR’s branch, rather than through a new PR.

Read/Watch 📖

Upcoming Meetings 🗓

Interested in hosting a <test-scrub>? Check out Leading Bug Scrubs for details.

#build-test-tools, #core-test

Week in Test: 11 July 2022

Welcome back to Week in Test, where contributors of any skill level can find a handy list of links and opportunities to start testing WordPress. Join the Test Team in #core-test for questions and thoughtful discussion.

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:

  • #56169: HeaderHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. menu navigation in FSE visibility issue.
  • #56178: Mobile menu link in FSE visibility issue.
  • #56184: register_block_type does not recognize ancestor blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. setting in block.json.

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:

  • #56167: Post title block alignment with RTL languages in Twenty Twenty theme.
  • #54677: Alternate option names for default widgets cause unnecessary DB queries.
  • #51812: Third (and final) step in removing jQuery Migrate 3.3.x from coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

And as this week’s bonus 🌟, here are some tickets that are almost there and need a little more exposure to testers:

  • #54394: Add functions for form required field indicators and messages.
  • #51170: Update FTPFTP FTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. https://codex.wordpress.org/FTP_Clients. updates to be RFC 959 compliant. Needs thorough testing across a variety of server environments.
  • #53816: Refactor widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. read/write logic.

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

  • #56068: Send HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. headers after querying posts in WP::main().
  • #21650: Replace serialize() with print_r() in stats() function.
  • #56180: Add header_image filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to header_image() function.

Read/Watch 📖

Meetings This Week 🗓

#build-test-tools, #core-test

Week in Test – 27 June 2022

Welcome back to Week in Test, where contributors of any skill level can find a handy list of links and opportunities to start testing WordPress. Join the Test Team in #core-test for questions and thoughtful discussion.

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:

  • #56024: Removing an image caption removes its alignment.
  • #56038 and #55581: Aligned image width not consistent between editor and frontend.
  • #56052: WP_List_Table extended class causes 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. notice.

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:

  • #52294: Twenty Twenty-One: Editor style fix for RTL languages.
  • #55606: Add wp_after_tag_search filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.. Ready for testing.
  • #28620: wp_nav_menu last level items have .menu-item-has-children even when child menus are not displayed.

And back for an encore performance:

PHPUnit Tests 🛟

Who? Any QA or 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:

  • #10249 (related: #17450 and #45897: Page slugs with non-ASCII characters result in 404 error.
  • #17851: Add abiltity to wrap sections created with add_settings_section(). Also needs patch testing.
  • #55877: Have wp_insert_post() check if post type exists. Also has patch feedback.

Read/Watch 📖

Meetings This Week 🗓

#build-test-tools, #core-test

Week in Test – 22 June 2022

Welcome back to Week in Test, where contributors of any skill level can find a handy list of links and opportunities to start testing WordPress. Join the Test Team in #core-test for questions and thoughtful discussion.

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.

Contributors are who make WordPress as great as it is! Are you ready to get started?

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:

  • #56005: Can’t adjust Pullquote blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. font size in TT1 theme.
  • #55986: Can’t add more than 2 tags to post using screen reader.
  • #55993: Incorrect canonical redirect for paginated posts.

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:

  • #24661: Update remove_accents to support non-NFC encoded characters.
  • #55005: Improve 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. performance for block.json files. Needs thorough testing across different environments.
  • #51857: Test Rollback Update Failure feature. Available as a plugin or patch. Also needs unit tests. This is marked as early.

PHPUnit Tests 🛟

Who? Any QA or 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:

  • #55448: WP_Widget_Block outputs empty container if widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. has no output.
  • #54736: Prevent get_sample_permalink() from unsetting $post->filter.
  • #51986: Fix array_intersect_key error when first argument is a string.

Read/Watch 📖

Meetings This Week 🗓

#build-test-tools, #core-test

Week in Test – 24 May 2022

Hello again! Welcome to a new edition of Week in Test, where contributors of any skill level can find a handy list of links and opportunities to start testing WordPress. Join the Test Team in #core-test for thoughtful discussion, and occassional 🥛 & 🍪.

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.

🙋‍♀️ 🙋 Hi, Contributors! Let’s get rolling…

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:

  • #55783: Word break/wrap in button text does not work as expected on frontend (Twenty Seventeen theme).
  • #55751: Filters for next_posts_link_attributes and previous_posts_link_attributes are applying to the opposite links than the filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. names suggest.
  • #55755: Enabling REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. on custom post typeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept. disables Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. (thumbnail) support.

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:

  • #52992: Avoid unnecessary overhead when preparing REST API links.
  • #55691: Editor unable to find homepage template when WP_HOME differs from WP_SITEURL (Bedrock and Docker).
  • #17025: Make wp_list_authors() filterable.

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

  • #27048: Allow selection of post types during export.
  • #51986: Resolve PHP warning when not registering endpoint args as array of arrays. Also see unit test suggestion hints in this comment.
  • #54488:  wp_filter_nohtml_kses() does not remove HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. comments.

Read/Watch 📖

Meetings This Week 🗓

  • 24 May 2022 @ 13:00 UTC: <test-chat> in #core-test .
  • 27 May 2022 @ 13:15 UTC: <test-scrub> in #core-test.
  • And don’t forget to provide feedback on the proposal to move weekly <test-chat>/<test-triage> sessions from 13:00 to 16:00 or 17:00 UTC. Join the discussion.

Props to @hellofromtonya and @boniu91 for peer review of this post.

#build-test-tools, #core-test

Week in Test – 17 May 2022

Welcome to a new edition of Week in Test! This post features a curated list of where and how testers can get involved, regardless of skill level. You can find the Test Team in #core-test.

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.

Ready to pitch in? 🙋‍♀️ 🙋 Okay, let’s get started!

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:

  • #55671: A TikTok embed that contains </3 in the description appears to cause a broken anchor tag. This needs testing with additional variations, such as embeds from other sources.
  • #55684: High CPU when publishing a post under 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. 8.1.
  • #55698: Reported that “x” in post content is converted to a double-quote. Refer to the reporter’s notes to attempt to reproduce.
  • #39827: Fix redirect when permalink does not contain trailing slash. This is an old ticket that needs verification that it is still an issue.

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:

  • #55721: Use Flexbox to improve Add Plugins screen card alignment.
  • #55448: Prevent empty WP_Widget_Block container when widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. has no output (use 55448.diff).
  • #55290: Apply image edits to all subsizes.

PHPUnit Tests 🛟

Who? Any QA or 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:

  • #55606: Add wp_after_tag_search filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.. Needs additional feedback for proposed unit test.
  • #54541: Add actions to template loading.
  • #34353: Address missing URI scheme for redirect_canonical().

Read/Watch 📖

Meetings This Week 🗓

  • Proposal for new <test-triage>/<test-chat> time: Join the discussion.
  • 20 May 2022: <test-scrub> starting at 13:15 UTC.

Props to @hellofromtonya for peer review of this post.

#build-test-tools, #core-test

Week in Test – 1 Nov 2021

Welcome to this week’s edition of Week in Test! This post is a curated list of where you can get involved (i.e. where testers of all skill levels and expertise are needed), learning opportunities, and some reading to keep you informed.

This week focuses on helping with 5.9 new features and enhancements. Remember, feature freeze is 9 Nov.

🙋‍♀️ 🙋 Contributing: Tester Help Needed

Looking for ways to contribute? The following tickets and patches need contributors.

Manual testing help needed

Who? All contributors (not just developers) who can set up a local testing environment, apply patches, and test per the testing instructions.

The following tickets need testers to manual test and provide feedback (test report):

PHPUnit tests help needed

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 is interested in learning how to) build automated PHPUnit tests.

The following tickets need PHPUnit tests build:

  • #15145: Add a wp_list_users() template tag
  • #54331: Add a hook in wp_http_validate_url to control which ports are allowed for remote requests

Reproducing reported issue help needed:

Who? Any contributor.

The following new tickets need testers to attempt reproducing the reported issue and then providing a test report with the results:

  • #54320: There are no more thumbnails for updated PDFs
  • #54430: Twenty Twenty-One: Menu item focus background only works on Chrome (ignored on Safari)
  • #54354: open_basedir warnings on classic post edit screens with TinyMCE plugins present

Reading / Watching

Meetings This Week

  • 2 Nov 2021: Test Triage session starting at 13:00 UTC
  • 5 Nov 2021: Test Scrub starting at 13:15 UTC

Props to @boniu91 for peer review.

#build-test-tools, #core-test