1. Attendance
In attendance was:
@fakhriaz @huzaifaalmesbah @ozgursar @supernovia @mosescursor @sajib1223 @andrewssanya @mohkatz @zuveria @r1k0 @sirlouen
2. Volunteer
3. Test Team Discussions
Switching to Monthly Newsletter
The team discussed changes to the monthly newsletter format. The decision was made to remove the “tests to be done” section and replace it with a new “call for testing” section that aggregates requests from other groups. Additionally, the newsletter will include announcements, news, and ideas from team members. @mosescursor will comment on the related GitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ issue with further details.
New Triage Guide
@sirlouen presented the diagram proposed by @juanmaguitar in the “Add Trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. Keyword Triage Guide for Test Team Members” initiative. During the discussion:
- @ozgursar raised concerns about whether bug reproduction should be included, noting it could be confusing.
- @r1k0 commented that the guidance on what to write for expected results is not clear enough.
@sirlouen requested that team members add more comments to the GitHub issue to help refine the new guide.
Announcements for Test Team Promotions
Promotions were announced for the following team members: @ozgursar, @r1k0, @juanmaguitar, and @huzaifaalmesbah.
4. Open Floor
- @sirlouen expressed hope that the team can move toward an automated testing protocol in the future. Several ideas were discussed around improving the onboarding experience for new contributors:
- @shazzad suggested adding a special keyword to identify easy tickets for new test team members.
- @fakhriaz agreed with the idea.
- @supernovia suggested the name
good-first-test for this keyword.
- @sirlouen had some concerns looking at the triage workflow: when a new test ticket appears in chat, a team member should triage and review it, removing the
needs-testing keyword if the ticket cannot be tested, but leaving it if it can be tested. Placing the good-first-test keyword on tickets doesn’t seem to find a good place in this workflow. Further refinement is required to confirm that this keyword will truly fit.
- @shazzad will open a ticket in the GitHub test-handbook repository to formalize this idea.
- The team also discussed the need for weekly test team updates on current Needs Reproduction and Needs Patch Testing tickets. @mosescursor will handle this responsibility until @nikunj returns.
- @mosescursor asked if @r1k0 would be joining the contribution day in Uganda on March 14. @r1k0 will check his schedule and confirm.
- @sirlouen reminded the team that any AI tools used during testing should be noted in the footnotes of test reports.
- @mosescursor will request huddle permission from the meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team to facilitate future voice chats.
5. Announcements
WordPress Ecosystem Announcements
Test Team Announcements
Call for Testing
6. Other Meetings
Props to @supernovia, @huzaifaalmesbah, @ozgursar, and @r1k0 for helping review this article and offering feedback.
#test-chat-summary
