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 📣
- Help Test 6.8 will be coming soon!
- Bug Scrub Schedule for WordPress 6.8
Weekly Testing Roundup 🤠
Weekly update: Test Team Update: 13 January 2025
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:
- #62806 Customizer: Respect settings that minimize non-essential motion
- #62819 Twenty Fourteen :- Latest Comment block font-size not working in user side and admin side.
- #62810 Pattern with Query Loop and Cover block renders wrongly in preview
- #62816 Trying to access array offset on false in /{PATH}/wp-includes/class-wp-recovery-mode-email-service.php on line 367
- #62821 Plupload Plugin – Outdated and No Longer Maintained, Request for Replacement or Update
- #62828 Array should not be passed to get_page_by_path()
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:
- #21022 Use bcrypt for password hashing; updating old hashes
- #52592 PHP warning when the label property is missing from register_block_style
- #12056 target=”_blank” being stripped from Profile Bio and Category Description
- #32942 Taxomony term list counts do not respect post_type parameter
- #62812 Make it easier to update bundled certificates
- #37332 Enhancement: Add a wrong password message on password protected posts
- #62215 Remove `role=”presentation” from h4 section headings in customizer nav menus
- #62818 Walker_Nav_Menu duplicated queries introduced by get_privacy_policy_url() call
- #61154 Fix the ‘attributes’ dynamic property in WP_Block
- #61322 HTTPOnly attribute for WP Test Cookies
- #61890 Handle WP_Term dynamic properties for PHP 8.2
- #61959 Enhance Support for `popovertarget` and `popover` Attributes in Native Browser Popover API
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:
- No tickets found
6.8 Related issues need testing
The following 6.8 tickets need testing those are having patches:
- #21022 Use bcrypt for password hashing; updating old hashes
- #52592 PHP warning when the label property is missing from register_block_style
- #12056 target=”_blank” being stripped from Profile Bio and Category Description
- #62812 Make it easier to update bundled certificates
- #37332 Enhancement: Add a wrong password message on password protected posts
- #62215 Remove `role=”presentation” from h4 section headings in customizer nav menus
- #62818 Walker_Nav_Menu duplicated queries introduced by get_privacy_policy_url() call
- #61796 Blank Page When $_GET[‘postId’] Does Not Exist in /wp-admin/site-editor.php
- #61154 Fix the ‘attributes’ dynamic property in WP_Block
- #61322 HTTPOnly attribute for WP Test Cookies
- #61959 Enhance Support for `popovertarget` and `popover` Attributes in Native Browser Popover API
Profile Badge Awards 🎉
Profile badge awarded to Dhrumil Kumbhani
Read/Watch/Listen 🔗
- We are currently in the WordPress 6.8 release cycle. Read more about the release squad, timeline and focus for this release.
- Design plans for WordPress 6.8 is also published.
- Next maintenance release: 6.7.2
- There is currently no release date planned for WordPress 6.7.2
- You can review the next minor release milestone.
- 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 20.1, scheduled for January 22. It will include the following issues.
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2025.
2025 Schedule:
- Wednesday, 22 January 2025 at 21:30 GMT+5:30:
<test-triage>in #core-test. - Wednesday, 29 January 2025 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.