In attendance was: @sirlouen @fakhriaz @huzaifaalmesbah @ozgursar @supernovia @mosescursor @sajib1223 @andrewssanya @mohkatz
- This week's facilitator was @sirlouen
- This week's note-taker was @ozgursar
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 issue with further details.
@sirlouen presented the diagram proposed by @juanmaguitar in the "Add Trac 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.
Promotions were announced for the following team members: @ozgursar, @r1k0, @juanmaguitar, and @huzaifaalmesbah.
- @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 proposed adding a special keyword to identify easy tickets for new test team members.
- @fakhriaz agreed with the idea.
- @supernovia suggested the name
good-first-testfor this keyword. @shazzad will open a ticket in the GitHub testbook repository to formalize this idea. - @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-testingkeyword if the ticket cannot be tested, but leaving it if it can be tested. Placing thegood-first-testkeyword 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.
- 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 team to facilitate future voice chats.