This article presents a requirement for our freelancers. Failure to follow the process might represent a breach of the Freelancer Services Agreement.
As a tester, you might sometimes wonder about a Test Lead's tasks. The list below gives you a bit of an insight on the most common tasks that a TL carries out when managing test runs.
1. Communication
Welcoming the testers at the beginning of new test run and thanking them in the end of the run in the workspace chat
Addressing the issues raised by testers in workspace chat, mostly within two hours (not during night hours)
Discussing the issues requiring Services Team input with responsible Engagement Manager in a clear and timely manner
Checking the run feedback from testers
2. Issue quality
Making sure that approved issues have clear title and content
It is clear why closed issues have been closed
It is clear why the issues marked with a question tag are questions
Allocating 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 Testing Manager of the run contacted them and if needed is there a new issue logged for this/old one reopened (based on workspace specifics)?
3. Task list execution review
Reviewing all task list results and communicating queries to the respective tester and Engagement Manager
4. 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
5. Feedback to testers
Giving feedback on issue approval in a way that helps the testers become better at reporting the issues
Giving feedback when approving tasks. Problems (e.g plenty of duplicates or out of scope issues) are addressed and great work praised
#TestlioBot