- CTAL-TM (Certified Tester Advanced Level Test Management) is ISTQB's advanced certification for people who manage testing on a project. The current version is 3.0 (2024).
- Prerequisite: ISTQB Foundation Level (CTFL). At least six months of testing or development experience is recommended.
- The syllabus has 3 chapters: managing the test activities, managing the product and managing the team, with at least 22.75 hours of accredited training.
- The exam has 50 questions worth 88 points, the pass mark is 58 (65%) and it lasts 120 minutes (150 if it is not your native language).
- It includes 14 K4 questions (scenario analysis) worth 3 points each.
- It is valid for life and opens the door to Expert Level.
- Prepare with our ISTQB Test Manager course: 30 live hours on Teams.
At some point in almost every tester's career, designing and running good tests is no longer enough: you have to decide what gets tested, how much, with whom, on what budget and how to explain it to the business. That jump, from tester to lead or test manager, is exactly what the ISTQB Test Management (CTAL-TM) certification covers.
In this guide I explain what version 3.0 is, who it is for, what the syllabus covers chapter by chapter with real project examples, what the exam looks like and how to prepare.
What CTAL-TM is and where it sits in the ISTQB portfolio
CTAL-TM is one of ISTQB's Core Advanced modules, alongside Test Analyst (CTAL-TA), Technical Test Analyst (CTAL-TTA) and Test Automation Engineering (CTAL-TAE). You take it after CTFL, and it is the base for the Expert Level Test Management and Improving the Test Process modules.
Version 3.0 was released in May 2024 and replaced the 2012 version. The main changes:
- It was reorganized into three chapters: managing the test activities, managing the product and managing the team.
- It is aligned with CTFL 4.0 and with agile and hybrid development (for example, V-model planning with sprint-based construction).
- It focuses on test management at project level, not across the whole organization.
- It adds K4 objectives that require analyzing contexts and making decisions.
According to the syllabus, the certificate is valid for life and does not require renewal. For the full map and costs in your currency, see our ISTQB certification guide.
Who it is for and prerequisites
The syllabus says CTAL-TM is aimed at anyone involved in managing testing: testers, test consultants, test managers, user acceptance testers, Scrum Masters, project managers and product owners. It also suits anyone who needs an advanced understanding of testing: quality and development managers, business analysts, IT directors and management consultants.
The profiles we see most often:
- QA leads and senior testers who already coordinate others and need a formal method.
- Test managers without a certification who want international backing for what they already do.
- Project managers, Scrum Masters and product owners who need to understand how to plan, estimate and report on quality.
- Consultants at firms that sell testing services and need credentials in front of clients.
Prerequisites: the ISTQB Foundation Level certification (v4.0 or earlier). The syllabus strongly recommends at least six months of experience as a tester or developer; some member boards or exam providers may apply experience criteria, so check when you book.
What you will be able to do: business outcomes
The syllabus defines 11 business outcomes:
| Code | A certified test manager can... |
|---|---|
| TM_01 | Manage testing in various projects by applying the test management processes established for the team or organization |
| TM_02 | Identify the stakeholders and lifecycle models relevant in a given context |
| TM_03 | Organize risk identification and assessment sessions and use the results to guide testing |
| TM_04 | Define a project test strategy consistent with the organizational test strategy and the project context |
| TM_05 | Continuously monitor and control testing to achieve project goals |
| TM_06 | Assess and report test progress to stakeholders |
| TM_07 | Identify the necessary skills and develop them within the team |
| TM_08 | Prepare and present a business case for testing with costs and expected benefits |
| TM_09 | Lead test process improvement in projects and contribute to organizational initiatives |
| TM_10 | Plan the test activities, including test infrastructure, and estimate the effort |
| TM_11 | Create defect reports and a defect workflow suited to the lifecycle |
All content is examinable at K1 (keywords), and the specific learning objectives are classified as K2 (understand), K3 (apply) and K4 (analyze).
Syllabus content chapter by chapter
| Chapter | Minimum time | Key topics |
|---|---|---|
| 1. Managing the Test Activities | 750 min | Test process, context and stakeholders, hybrid development, risk-based testing, project test strategy, S.M.A.R.T. objectives, process improvement (IDEAL, TMMi, TPI NEXT, retrospectives), tools |
| 2. Managing the Product | 390 min | Test metrics, control through metrics, reporting, estimation, defect management in sequential, agile and hybrid models |
| 3. Managing the Team | 225 min | Four areas of competence, skills assessment and development, motivation, cost of quality, cost-benefit of testing |
That is 1,365 minutes (22.75 hours) of minimum training. Our course runs 30 hours to include case studies and mock exams.
Chapter 1. Managing the Test Activities
This is more than half of the syllabus and the exam (26 of the 50 questions). It has six blocks.
1.1 The test process. It goes deeper into the three management activities from CTFL: planning (understand the context, identify risks and how to treat them, define the approach, estimate and allocate resources, establish the plan), monitoring and control (compare actual progress with the plan and take action) and completion (completion report, archive and hand over testware, restore the environment and capture lessons learned).
1.2 The context of testing. Who the stakeholders are (business, development, operations, users, audit) and why each cares about something different; how to manage testing in a hybrid model, across lifecycles, test levels (component, integration, system, acceptance) and test types (functional, non-functional, black-box, white-box). The K4 objective here asks you to analyze a project and decide which management activities to emphasize.
1.3 Risk-based testing. The heart of test management. It includes:
- Testing as risk mitigation: what to test first, how deeply and with which techniques.
- Identifying quality risks: brainstorming, interviews, risk workshops, checklists, retrospectives, past experience.
- Assessment: factors driving likelihood (complexity, new technology, time pressure) and impact (money, reputation, safety, compliance).
- Mitigation by risk level (K4): choosing the right test activities for each risk in a given context.
- Heavyweight vs. lightweight techniques: heavyweight ones such as hazard analysis, cost of exposure, FMEA and fault tree analysis (typical in safety-critical systems); lightweight ones such as PRAM, PRISMA or Systematic Software Testing.
- Success metrics and difficulties: for example, the percentage of critical defects found before production.
A practical example: in a banking app, "transfers to other banks" has high likelihood (complex integration) and high impact (customer money and regulation): thorough testing with several techniques, requirements reviews and automated regression. "Change profile picture" is low on both: light or exploratory testing.
1.4 The project test strategy. How to choose the approach (levels, types, techniques and practices such as scripted, manual or back-to-back testing), analyze the organizational strategy and project context to select it (K4) and define measurable test objectives and exit criteria with the S.M.A.R.T. method (specific, measurable, achievable, relevant, time-bound) (K3). Example: not "test payments well," but "by June 30, run 100% of high-risk payment tests with zero open critical defects."
1.5 Improving the test process. The IDEAL model (initiating, diagnosing, establishing, acting, learning), model-based approaches such as TMMi and TPI NEXT, analytical approaches based on data and causes, and how to run a project or iteration retrospective to find areas to improve (K3).
1.6 Test tools. Good practices for introducing a tool (pilot, gradual rollout), technical and business aspects of the decision, how to build a tool selection plan covering risks, costs, benefits and return on investment (K4), the stages of a tool's lifecycle and how to use tools to collect metrics.
Chapter 2. Managing the Product
2.1 Test metrics. Why measure, which metrics fit each activity and how to use them to control progress. The syllabus groups them into product risk, defect, progress, coverage, and cost and effort metrics. The K4 objective asks you to analyze results to create reports that let stakeholders make decisions. A good report doesn't say "we ran 340 test cases"; it says "92% of high risks are covered; 3 high-severity defects remain in payments; we recommend releasing without the refunds module."
2.2 Test estimation. Which activities to estimate, factors that influence effort (product, development process, people, test results, context) and how to select the right technique (K4). Techniques are metric-based (ratios, extrapolation) or expert-based (Wideband Delphi, planning poker, three-point estimation). Selection criteria: estimation error, availability of historical data and experts, modeling knowledge and time constraints. For example: low complexity with historical data suits metric-based techniques; an agile team suits planning poker; a complex sequential project suits Wideband Delphi.
2.3 Defect management. Implementing a defect process and workflow (K3) with its states and transitions; cross-functional defect management (a triage board with business, development and testing); specifics in agile (defects fixed within the sprint without a formal report, technical debt) and in hybrid models; which data and classifications to collect (K3); and how to use defect statistics to propose process improvements, for example when most defects originate in requirements.
Chapter 3. Managing the Team
3.1 The test team. Skills are classified into four areas of competence:
- Professional: test techniques, technology, domain knowledge, project management.
- Methodological: analytical, conceptual and judgment skills.
- Social: communication, cooperation, conflict management, teamwork.
- Personal: self-management, responsibility, resilience, openness to change, willingness to learn.
Building on that, the K4 objective asks you to analyze a context to determine the skills the team needs. It also covers skills assessment techniques (skills matrices, interviews, self-assessments), ways to develop skills (training, mentoring, coaching, rotation), the skills needed to manage a test team and motivating and hygiene factors: recognition and growth motivate; a poor environment or pointless rules demotivate even when pay is good.
3.2 Stakeholder relationships. The cost of quality in four categories: prevention (training, early reviews), appraisal (static and dynamic testing), internal failure (fixing defects found in testing) and external failure (defects in production: lost revenue, fines, support). And the K3 part: applying a cost-benefit calculation to show the value of testing. A simplified example: if each production defect costs on average 10 times more than fixing it in testing, and the team prevents 50 defects per release, the savings justify the testing investment. That is the argument you need to defend your budget.
Download the official syllabus
All sections are examinable except the introduction, appendices and references.
The CTAL-TM exam
Verified structure
| Item | Value |
|---|---|
| Questions | 50 multiple-choice |
| Total points | 88 (K2 = 1 point, K3 = 2, K4 = 3) |
| Pass mark | 58 points (65%) |
| Duration | 120 minutes; 150 if you take it in a language that is not your native one (+25%) |
| Cognitive levels | 26 K2, 10 K3 and 14 K4 questions |
| Prerequisite | ISTQB Foundation Level (CTFL) |
| Validity | Lifetime |
Distribution by chapter according to ISTQB's official tables:
| Chapter | Questions | Points |
|---|---|---|
| 1. Managing the test activities | 26 | 46 |
| 2. Managing the product | 15 | 27 |
| 3. Managing the team | 9 | 15 |
Note that the 14 K4 questions contribute 42 of the 88 points. Master scenario analysis and you have half the exam covered.
Exam options
- Online from home with remote proctoring (iSQI FLEX): available 24/7; for Advanced exams, book at least 48 hours ahead. You need a webcam, a microphone, a second camera using your phone and a government-issued ID.
- Pearson VUE: at a test center or online with OnVUE.
- On-site at your company: for groups of 6 or more, Cool Testers brings a proctor.
Paper-based exams are no longer offered.
Where to buy it
The exam is not included in the course. You have two options:
- Directly from iSQI, our partner and official exam provider, with a 20% coupon off the price on their site for your first attempt, which we send when you enroll. Best if you are paying yourself.
- Through Cool Testers: our certification exam with 1 or 2 attempts. A good fit if your company pays or you need an invoice. You have 1 year to take it.
How to prepare
6-week plan
| Week | What to study | Goal |
|---|---|---|
| 1 | Review CTFL 4.0 chapter 5, then sections 1.1 and 1.2 | Explain planning, monitoring, control and completion; map your project's stakeholders |
| 2 | Section 1.3 | Run a risk analysis on a real system and choose mitigations |
| 3 | Sections 1.4 to 1.6 | Write S.M.A.R.T. objectives, a project strategy and a tool selection plan |
| 4 | Chapter 2 | Build a decision-oriented report, choose estimation techniques and design a defect workflow |
| 5 | Chapter 3 | Team skills matrix and a cost-benefit calculation |
| 6 | Mock exams | Official sample exam; practice pacing 50 questions in 120 minutes |
Common mistakes
- Answering the way your company does it. The exam follows the syllabus terminology and approach.
- Skimming K4 scenarios. They often have several generally "correct" options, but only one is best for that context.
- Forgetting CTFL 4.0 basics. Three-point estimation, the pyramid, quadrants and risk all come from Foundation.
- Ignoring chapter 3. Skills, motivation and cost of quality look like common sense, but they have precise definitions.
Our ISTQB Test Manager course
Our ISTQB Test Manager course is an accredited course with 30 live hours on Microsoft Teams on Saturdays, taught by Miguel Hernández, with case studies on risk, strategy, estimation and reporting drawn from real projects. You keep the recordings for 3 years and can retake it for free in any open group within the following 6 months. In open groups you can pay in installments (50% today plus 3 biweekly payments, with a 10% financing fee), and two people enrolling together get 10% off.
If you don't have Foundation yet, ask about the Foundation + Test Manager bundle with 50% off the second course. Questions? Message us on WhatsApp.
Benefits and career paths
- A step into leadership: it shows you can plan, estimate and report on testing, not just run tests.
- Business language: you learn to talk about risk, cost of quality and return, which is what executives listen to.
- Credibility with clients: highly valued at consulting firms and on projects for US and European clients.
- Path to Expert Level: it is a prerequisite for Expert Test Management and Improving the Test Process.
- For companies: leads with a shared test management method. We deliver the course for your company; request a quote.
Typical roles: QA lead, test manager, test coordinator, QA manager, quality consultant and, with experience, head of QA.
How it relates to other certifications and what comes next
- Before: CTFL 4.0, mandatory.
- Core Advanced complements: Test Analyst, Technical Test Analyst and Test Automation Engineering.
- Agile: CTAL-AT v2.0 and CT-ATLaS if you lead quality in agile organizations.
- Automation strategy: CT-TAS.
- Process improvement: TMMi.
- Expert Level: Expert Test Management and Improving the Test Process.
Frequently asked questions
What is the prerequisite for CTAL-TM?
The ISTQB Foundation Level (CTFL) certification, version 4.0 or earlier. At least six months of testing or development experience is recommended.
How many questions does the CTAL-TM v3.0 exam have?
50 multiple-choice questions worth 88 points. You pass with 58 (65%). You have 120 minutes, or 150 if you are not taking it in your native language.
What changed from the 2012 version to 3.0?
It was reorganized into three chapters (activities, product and team), aligned with CTFL 4.0 and with agile and hybrid development, focused on project level and gained K4 objectives.
Does the CTAL-TM certification expire?
No. According to the syllabus, the certificate is valid for life and does not require renewal.
Do I need to be a test manager to get certified?
No. It suits senior testers, QA leads, Scrum Masters, project managers and product owners involved in managing testing.
Can I take the exam in English or Spanish?
Yes. The v3.0 syllabus exists in both languages, and the certification is equally valid in either.
Is the exam included in the course?
No. You can buy it directly from iSQI with the 20% coupon we send when you enroll, or through Cool Testers if your company pays or you need an invoice.