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:
FSE Program Testing Call #19: Running Through Refinements
Help efforts to wrap up Phase 2 of the WordPress Roadmap by putting the editor’s latest updates to the test (😉) in a simulation of making a few improvements a client’s website. Please leave feedback by 6 January 2023 🗓 #fse-outreach-program
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:
- #57322: Twenty Twenty-Three: Gradients clear on save with KSES filters active.
- #57329: Cannot save new custom template when name has non-Latin characters.
- #57339: Twenty Twenty theme pull quote border color issue.
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:
- #57320: Revisions: add filter before deleting revisions.
- #56412: Twenty Sixteen: gallery block produces shifted or scrambled output.
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.2 tickets need PHPUnit tests built to accompany their respective patches:
- #55290: Not all image edits are applied to all subsizes.
- #56340: PHP8.1
E_DEPRECATEDinPasswordHash::gensalt_blowfish.
Profile Badge Awards 🎉
And a huge belated Thank You to the following contributors who earned the Test Contributor profile badge by participating in the WordPress 6.1 and 6.1.1 releases:
Read/Watch/Listen 🔗
- State of the Word 2022: A Celebration of the Four Freedoms of Open Source — Wrap up the year reflecting on the progress of WordPress in 2022, and learn what’s in store for an exciting 2023!
- What time is it? 🕰 It’s the time of year to Share Your Experience: The 2022 WordPress Survey is Open. Help shape the future of WordPress!
- Are you interested in helping pilot a new tool to streamline testing and improve developer feedback? Please see FSE Program: Seeking volunteers to use Replay.io for capturing bugs. The program is accepting applications through 28 December 2022.
Upcoming Meetings 🗓
🚨 There will be no more regular #core-test meetings held for the remainder of 2022. Weekly meetings will resume on 3 January 2023. See you then!
2023 Schedule:
- 3 January 2023 at 16:00 UTC :
<test-chat>in #core-test. - 6 January 2023 at 15:00 UTC :
<test-scrub>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.