On Wednesday, May 21, 2025 at 12:00 AM GMT+8, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.
1. Attendance
@krupajnanda @ravigadhiyawp @sirlouen @mosescursor @kausaralm @oglekler @pooja1210 @pavanpatil1 @iamshashank @muddassirnasim (async) @nikunj8866 (async), @lumiblog (async)
2. Volunteer
This week’s Note-taker and facilitator:
- Facilitator – @krupajnanda
- Note-taker – @muddassirnasim
For the next bi-weekly chat –
- June 05:
Test Chat Meeting Facilitator: @krupajnanda - June 05:
Test Chat Meeting Recap Notes: @lumiblog
3. Announcements 📣
- Test team table lead for WCEU Contributor day
- A Month in Core – April 2025 is out.
- Performance Chat Summary: 20 May 2025
- The next major release things are in progress and can be found here.
- WCEU is around the corner. Please check out the schedule.
- Gutenberg 20.8 is now available
- Gutenberg 20.9 is scheduled for release on Wednesday, May 28, 2025.
- Test team table lead for WCEU Contributor day @OGlekler will leading the Table for test team at WCEU. @Puja and @SirLouen will be our online leads. We will soon publish a post mentioning all the information about what and how contributors can help us at WCEU contributor table.
4. Test Team Updates
- Week in Test Post: Wondering where you can contribute and learn? The Test Team’s got you covered.
- Test Team Update: Metrics for overall team progress.
5. Focal Group Updates
- No updates.
6. Questions/Blockers
- No Questions/Blockers were reported in this meeting
7. Call for Testers/Visibility
- #core-editor team has shared this issues that needs testing. Please feel free to pick and contribute to any tickets and make sure to update the same in the #core-editor for the better visibility.
8. Open Floor
The conversation focused on improving the testing workflow and coordination during Contributor Days, especially regarding ticket handling and visibility of test efforts.
- @sirlouen raised concerns about the difficulty of enforcing test tag management purely through control, suggesting that clear contributor instructions might be more effective.
- @krupajnanda supported the idea that contributors should ensure tickets with sufficient test reports no longer carry the “needs-testing” keyword and encouraged proactive keyword checks before picking tickets.
- @oglekler proposed better planning for future Contributors Day, highlighting interesting or challenging tickets to attract attention.
- The team agreed on the need for more strategic planning and gradual improvements. @krupajnanda offered to draft a Contributor Day post, incorporating curated tickets with specific keywords, to guide contributors more effectively.
- The idea of showcasing handpicked tickets was welcomed to engage contributors and highlight meaningful work..
9. Next Meeting 🗓
The next meeting will be on Thursday, June 05, 2025, at 12:00 AM GMT+8 , held on #core-test!
Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!Thank you @krupajnanda, for the peer review and for helping me write this post.