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: 06 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:
- #62790 “autoload” index is not used
- #62785 wp_kses_no_null() should be modified to handle $content having a null value
- #62792 Twenty Ten: Editor styles conflicts with the block editor styles
- #62787 Twenty Nineteen: sanitize output of twentynineteen_custom_colors_css()
- #62797 wp_add_inline_script does not properly escape ‘<!– <script>’ in contents
- #62793 Twenty Ten: Link styles breaks the style of the file block
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:
- #58934 Twenty Twelve: Table Block does not align center on front end
- #21022 Use bcrypt for password hashing; updating old hashes
- #12056 target=”_blank” being stripped from Profile Bio and Category Description
- #62499 Number in “Add Themes” screen is misaligned and touches the border
- #62803 Fix update_attached_file return type comment
- #58905 Ensure locate_template only loads theme files
PHPUnit Tests 🛟
Who? Any QA or 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 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:
- #10275 Filter logic has been put into the template loader while it not belongs there.
- #21022 Use bcrypt for password hashing; updating old hashes
- #12056 target=”_blank” being stripped from Profile Bio and Category Description
- #62499 Number in “Add Themes” screen is misaligned and touches the border
- #62803 Fix update_attached_file return type comment
- #58905 Ensure locate_template only loads theme files
Profile Badge Awards 🎉
No Badges awarded this week.
Read/Watch/Listen 🔗
- WordPress 6.8: Release Squad, Timeline, and Focus
- WordPress 6.8 Development Cycle
- This Gutenberg 20.0, it’s the 200th release of the Gutenberg plugin, is release. What is new in Gutenberg 20.0?
- WordPress Themes Need More Weird: A Call for Creative Digital Homes
- Write Books With the Block Editor
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2024.
2025 Schedule:
- January 15, 2025, at 21:30 GMT+5:30: <test-chat> #core-test! in #core-test.
- January 22, 2025, at 21:30 GMT+5:30: <test-triage> #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.