What would you say in your experience are the responsibilities of a QA/Test Lead?
Of course, this can vary from company to company but have you seen any common responsibilities? Or ones that weren’t common but that you think should be?
currently I’m experimenting with a new title of Test Advisor – with these tasks:
- Assiting delivery teams on test activities and models of quality
- Assisting delivery managers on test automation strategies
- Advising heads of IT and sales executives on the strategic approaches to test automation
is that similar to QA/test lead - or is that more a principal tester?
5 Likes
Interesting @jesper ! Keep it up 
3 Likes
Greetings!
As a Test Lead, I was assigned to a project for the project’s duration. I was responsible for the Test Strategy (completed before work started, included manual and automated test approaches), work assignments to Testers on the project team, and tester’s work product review.
During any one week during project execution, there were meetings with the Project Manager (Dev Lead, Test Lead, business representation), meetings with Tester’s managers (periodic feedback on Tester’s work and suggestions for opportunities), and reporting.
As a Test Lead, I was in a position to advocate for testability, help support career goals of Tester’s, and help give testing a voice throughout product development.
I think this is similar to @jesper 's first two bullets.
Joe
4 Likes
A colleague of mine had a good talk on the topic where he discussed the four different places where he had the “Test lead” title and discussed the difference between them.
It ranged from “Test Project Manager” to I’m the only tester in the team so I do the testing.
My first question that pops into my head when someone says they are a test lead are: Do you lead the testing or the testers?
As to the responsibilities to me the exists roughly in 3 different categories.
- Tasks related to people and project. Like make sure that there exists the right people with the right knowledge at the right time to perform the testing. Dispatching work etc. (Tactical work)
- Tasks related to the test execution. Like environment, version of the system under test, analyzing changes and figuring out the desired tests, performing the tests and reporting the findings etc. (Tactical work)
- Defining and implementing strategy for 1 and 2. (Strategic work)
When I have had the title most of it have been related to 1 and then the testers have done 2 and a third party have typically done 3. When I did 3 I had the title of Test Coordinator or Test Analyst.
With the cross-functional teams and embedded testers roles like what Jesper talks about have started to pop up. Like Test Coach, Quality Coach, Test Advisor. Which seems to dabble in both the strategic and tactical side, but as a teaching / coaching function rather than executing function. To me this is a good thing. Because what was lost in the autonomous teams world was the strategic part. But since you still want the team to take responsibility and be accountable. You don’t want the original test manager / test lead. Which by nature took a large part of the responsibility too. Instead you have the advisor that help the team with complex strategic and tactical questions, while letting them be responsible for their own work.
Finally to actually answer the question. To me the common responsibilities of a Test Lead is to be responsible for the tactical part of the testing, i.e. dispatching work, planning in time, ensure capacity as well as being the single point of contact or " single wringable neck" as it turns out to be more often than not
3 Likes
turns out there’s a book about it
(not testing roles as such, but I can see the similarities)
2 Likes
At Metaswitch, I’m a Lead Test Engineer - this means I am responsible for both developing test strategy, but also executing on it. I don’t currently have any line management responsibilities, but I am expected to support, coach and mentor other testers. I am also extremely active within the test community in the business, being part of the test leadership group, testing guild, and organising internal events such as our Guild of testing conference.
As we transition to Microsoft, I expect this role to continue and evolve in new and different ways. It should be exciting and challenging.
3 Likes
My preferable choice is agile methodology and there are many firms offering agile testing services.
If you are a QA Team Lead then here are some responsibilities :
- Conduct daily standup.
- Design test strategies and review test plans.
- Maintain project oriented documents .
- Supervise QA team’s day-to-day activities.
- Coordinate with developers.
- Review team member performance and feedback improvements.
2 Likes
As QA Lead, way i have tried to tackle is as such:
- finding easy ways to delegate testing work to QAs under me but still allow proper review. for me this has looked like:
- we have all our qa testing within single repo that I look for members to have PRs for manual tests (where will write at highlevel what did manually (can refer to jira ticket if they happen to describe in ticket) along with automated tests they may have written. I will help be reviewer which will allow me and QA to have discussion and review of testing strategy. I can help give some tips, different ways to look at problem, ideas for testing strategy, potential other risks, etc. this allows for my QAs to have freedom of choosing how’d they like to test but part of process for me to help review
- a lot of my time is now spent mentoring and creating documentation and material for strategies, principals, etc that my team can learn from (allowing for them to learn on their own better as well, which limits the burden of onboarding)
- Can look at more higher level for ways to help reduce risk and friction in team as whole. examples may include:
- how can we allow for more eyes on testing earlier in process and have easier ways to explore? this has lead to ideas like adding dashboarding and libraries that make it easier and more intuitive to interact with our backend platform (especially those who may be more novice to programming)
- how can we document our system better? with our team growing larger and our system growing more complex, it can be come harder to onboard. so coming up with proper documentation.
- likely having a higher level overview of feature design (likely at epic level), to ensure things arent going to much ary. basically the more I can get my other QA/BAs to do 90-95% of work and that can plug in when needed (allows for team to scale better but still maintain good quality work, along with helping others in team grow)
a lot of the spirit is (a) reducing risk (especially can look at more higher level items) (b) reducing friction (seeing ways that can make day to day and overall team as whole function more efficiently) (c) providing overview and input when needed (d) teaching and promoting a qa mindset in team as whole (the all of team including devs, bas, etc can adopt a qa mindset and techniques, just means more eyes and minds thinking in this way, allows for sort of crowd sourcing and development from end to end with QA in mind, not just pinned to the “qa” members).
3 Likes