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:
- Early Opportunities to Test WordPress 6.5. Please help test!
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:
- #60261 Fatal error with invalid charset specified in Trackback
- #60269 URL parameter filtering with ‘tag’ parameter
- #60274 Query loop showing too many posts
- #60291 Support Lossless WebP in WP_Image_Editor_GD
- #60293 Twenty Fourteen: Table block does not have same design in editor and front.
- #60294 Block custom CSS: Backport updates to PHPUnit tests
- #60297 Editor throws error when wordpress is installed in a subdirectory and permalinks are activated
- #60298 Text embedded in theme template is not translatable
- #60287 HTML API: P end tag does not generate P element
- #60308 Inconsistent return of urls / get_bloginfo() vs get_template_directory_uri()
- #60311 Editing interface prompts error
- #60313 PHP Warning: Cannot modify header information – headers already sent
- #60314 Revisions: PHP Warning: Undefined array key 0 in …/wp-includes/meta.php on line 642
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:
- #55991 Twenty Twenty One: Unable to change size in Quote block
- #58783 Alternative text entered whilst uploading an image is lost when the image finished uploading
- #17379 Filtered exports drop attachments and featured images
- #49931 Twenty Nineteen: Group color styles prevent custom colors
- #59930 Problems pulling relevant MySQL Docker container
- #58827 Publish the Patterns page in the Site Editor to all non-block themes
- #52294 add_editor_style: Allow replacing a style with an RTL version
- #52529 Non-slashed $old_user_data->user_email in wp_insert_user causes user_activation_key to be unset
- #11302 Bulk editing posts should pre-fill fields with the same value / allow for removal
- #58901 Flush ‘user_activation_key’ after successfully login
- #59922 Twenty Nineteen is using CSS selectors that are no longer used in the editor
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. https://www.php.net/manual/en/index.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.5 tickets need PHPUnit tests built to accompany their respective patches:
- #58905 Ensure locate_template only loads theme files
- #54516 Full site editing/REST-API: modify permission checks to use post type.
- #59496 Duotone undefined index/array key warning
- #18408 Can’t wp_reset_postdata after custom WP_Query in an admin edit page
- #17904 Multisite has more restrictions on user login character set
- #59774 Undefined array key when using wp_list_pluck function
- #51019 convert_smilies() fails on large tags
- #58366 Shortcode Support Regained but Content Filters are messing with Shortcode HTML
6.5 Related issues need testing
- Font Library: biggest work for now is the Font Library: refactor REST API which needs feedback. Please help review if you have experience with the 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/. - Pattern overrides: work is ready to test starting with making paragraph blocks overrideable. Up next, headings, buttons and images are expected to be added soon as blocks that can have overrides.
Profile Badge Awards 🎉
No Badges awarded this week.
Read/Watch/Listen 🔗
- WordPress 6.5 release squad formation
- What’s new in Gutenberg 17.5? (17 January 2024)
- Are you interested in helping pilot a new tool to streamline testing and improve developer feedback? Please see Early Opportunities to Test WordPress 6.5
- Recording of hallway hangout: Let’s explore 6.5
- Call for Mentees & Mentors: Contributor Mentorship Program Cohort #2 (2024 Q1)
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2024.
2024 Schedule:
- 23 January 2023 at 11:00 UTC :
<test-triage>in #core-test. - 30 January 2023 at 11:00 UTC :
<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.