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
Weekly Testing Roundup 🤠
Weekly update: Test Team Update
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:
- #62391 Category name “preview” breaks admin css
- #62407 PHP Notice: Undefined offset in WordPress core when using template registered in a plugin via register_block_template() in WordPress 6.7
- #62401 WP_Query add extra JOINs after calling get_posts() with category__in in query arguments
- #62403 Unable to add italics to a page/post’s title
- #62400 RSS Block showing date in UTC when pubDate in feed is not
- #62417 Excerpts don’t include content from list-item blocks.
- #62435 Preload script modules and enqueue script modules in wrong order
- #62449 Bypassable Sanitization in the restfulAPI, which lead to the
- #62450 TinyMCE editor doesn’t load properly when initializing on Visual Tab (Firefox) [again]
- #62451 Menu editing broken on mobile
- #62453 Cropping of images in WP 6.7 is broken
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:
- #51019 convert_smilies() fails on large tags
- #34353 redirect_canonical() – Undefined indexes ‘host’ and ‘scheme’
- #62331 Imaged Edit GD Control Flow
- #41155 Theme Details dialog hides admin sidebar sub-menu navigation
- #59329 Firefox gets “ReferenceError: Â is not defined” in unminified moxie.js
- #62440 “Most Used” Category Tabs Not Synced with “All Categories” Tab in Classic 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.8 tickets need PHPUnit tests built to accompany their respective patches:
6.8 Related issues need testing
The following 6.8 tickets need testing those are having patches:
- #60074 Add New Media File > The ”dismiss button ”not showing any response when uploading the unsupported (.jfif) file
- #51019 convert_smilies() fails on large tags
Profile Badge Awards 🎉
Profile badge awarded to mosne, ikamal, sppramodh, tirth and Pavan
Read/Watch/Listen 🔗
- WordPress 6.7, Rollins, is out!
- The Playground team added browser support for cURL, making it easier for WordPress 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. developers to showcase their plugins directly in Playground and use them in
runPHPblueprint steps. - Experimental inline comments : In 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/ 19.6, inline commenting is now available as an experiment. You can follow the ongoing development of this feature in the tracking issue or review the previous work in the original pull request. Testing and feedback are needed. - Introducing the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Experiments plugin: A new plugin called WordPress.org Experiments allows contributors to test experimental features before they’re integrated into WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2024.
2024 Schedule:
- Tuesday, 19 November 2024 at 16:30 GMT+5:30:
<test-triage>in #core-test. - Tuesday, 26 November 2024 at 16:30 GMT+5:30:
<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.