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 block 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 PHP 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 loop 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 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 core 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
