DocsWP — WordPress Help

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 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 block site editing by working with navigation, header and footer patterns, category 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 JSON 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 type. 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 PHP developer contributors who can (or are interested in learning how to) build automated PHPUnit tests.
Why? Automated tests improve the software development feedback 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 widget 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