DocsWP — WordPress Help

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 plugin, 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 Block: 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 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.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 beta/RC 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