In software testing, saying “I’m a tester” is just the beginning. Testing is a structured process that involves clear roles and responsibilities. According to ISTQB, defining these roles is key to ensuring quality, speed, and strategic alignment in every testing effort.Knowing who does what boosts team collaboration and drives better outcomes.
The ISTQB CTFL v4.0 syllabus identifies two core roles in the test process:
Depending on the team size and context, one person may hold both roles or they may be distributed across multiple people.
This role leads the overall test process, often assumed by a test manager, test lead, or even a scrum master in Agile settings.🔹 Main responsibilities:
📌 Example: A test lead organizes regression activities, allocates resources, tracks progress, and communicates risks to stakeholders.
This is the hands-on role for designing and executing tests. It’s typically carried out by testers, QA engineers, test analysts, or automation engineers.🔹 Main responsibilities:
📌 Example: A tester writes test cases for an invoicing module and automates regression checks using Cypress.
In larger or more complex projects, other roles come into play:
In testing, roles are not always tied to job titles. For example:
What matters is clear role assignment, not labels.
Knowing who does what in testing is essential for smooth execution, predictable results, and continuous improvement. Clear roles prevent bottlenecks, clarify responsibilities, and make the whole process more efficient.It's not about hierarchy — it's about ownership.