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: Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings
Weekly Testing Roundup 🤠
Weekly update: Test Team Update: 2 December, 2024
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:
- #62579 iFrame plugins must have an accessible name
- #62570 Fatal error: call to undefined function wp_cache_get() (in option.php)
- #62593 Condition for doing_it_wrong for conditional tags is too generic
- #62600 fatal error on capabilities.
- #62602 Table directory not available for the wp editor
- #62577 WordPress Rest API broken in 6.7.1
- #62597 WordPress 6.7 sizes=”auto” is messing featured image on chrome mobile.
- #62588 fetch_feed caching broken in WP 6.7
- #62610 Twenty Seventeen – Image block having unnecessary border if duotone and link is applied.
- #62617 Infinitive loop on API req in Block editor after wordpress_logged_in cookie is removed
- #62628 Server and client directive negation logic should align
- #62630 Site Health plugin information display html tags in plugin name
- #62627 PHP warning or fatal error if user supplies array instead of string
- #62592 Header informationa are modiefied
- #62633 Is writable check for fonts folder is misleading/wrong
- #62591 No changes being saved on blog issue
- #62634 Bug Report: Error in mediaelement-and-player.js
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:
- #62319 There is a flash when clicking the template name in the editor if a plugin registered template matches a default WP theme template
- #61711 Password-protected pages lacking appropriate ‘Cache-Control’ request header
- #52592 PHP warning when the label property is missing from register_block_style
- #62326 Add title and description to post format archive block templates
- #21022 Use bcrypt for password hashing; updating old hashes
- #61765 Twenty Twelve: The large quote pattern does not use a quote block
- #58183 PHP notice when accessing Customizer with a classic theme without widgets
- #62491 Customizer accordion height fills screen
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 tickets need PHPUnit tests built to accompany their respective patches:
- #62319 There is a flash when clicking the template name in the editor if a plugin registered template matches a default WP theme template
- #61711 Password-protected pages lacking appropriate ‘Cache-Control’ request header
- #52592 PHP warning when the label property is missing from register_block_style
- #62326 Add title and description to post format archive block templates
- #21022 Use bcrypt for password hashing; updating old hashes
- #61765 Twenty Twelve: The large quote pattern does not use a quote block
- #58183 PHP notice when accessing Customizer with a classic theme without widgets
- #62491 Customizer accordion height fills screen
Profile Badge Awards 🎉
No Badges awarded this week.
Read/Watch/Listen 🔗
- How to disable the Font Library
- There is currently no release date planned for WordPress 6.7.2. Review the next minor release milestone for 6.7.2
- We are currently in the WordPress 6.8 release cycle.
- Proposal: Major releases for 2025
- A call for volunteers for the release squad has been published here.
- What’s new in Gutenberg 19.7? (20 November)
- The next 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/ release will be 19.8, scheduled for December 4. It will include the following issues.
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2024.
2024 Schedule:
- Wednesday, 4 December 2024 at 21:30 GMT+5:30:
<test-chat>in #core-test. - Wednesday, 11 December 2024 at 21: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.