As a tester, you might sometimes wonder, what are Community Test Lead's tasks. The list below gives you a bit of an insight on the most common tasks that a cTL carries out when managing test cycles.
1. Communication
- Welcoming the testers at the beginning of new test cycle and thanking them in the end of the cycle in the project chat
- Addressing the issues raised by testers in project chat, mostly within two hours (not during night hours)
- Discussing the issues requiring QA team input with responsible QA Project Manager in a clear and timely manner
- Checking the cycle feedback from testers
2. End Report
- Correct grammar
- Proper structure
- Valuable testing notes
- Choice of highlighted issues
- If there are issues marked as questions, it is clear why they are questions
3. Issue quality
- Making sure that approved issues have clear title and content
- It is clear for the closed issues why they have been closed
- It is clear why the issues marked with a question tag are questions
- Assign issues for retesting
- Triage issues, close WADs, duplicates, and out of scope issues
- Ensure that all required information is added to the issue report
- Have the testers reproduced any of the closed issues? If yes, has the Cycle Test Lead contacted them and if needed is there a new bug logged for this/old one reopened (based on project specifics)?
4. Task list execution review
- Reviewing all task list results and communicating queries to the respective tester and QA Project Manager
5. Feedback to testers
- Giving feedback on issue approval in a way that helps the testers become better at reporting the bugs
- Giving feedback when approving tasks. Problems (e.g plenty of duplicates or out of scope issues) are addressed and great work praised