The ISTQB Certified Tester Advanced Level Agile Tester (CTAL-AT) v2.0 is the new advanced-level certification for software professionals who test in Agile environments. Released on April 17, 2026, this version replaces the older CTFL-AT (Foundation Level Agile Tester) certification and moves the entire Agile testing curriculum from the Foundation stream into the Advanced Level. If you work on Agile teams and want a certification that goes beyond awareness into applied testing skills, CTAL-AT v2.0 is the current benchmark.
What is the ISTQB CTAL-AT v2.0 Certification?
The ISTQB Certified Tester Advanced Level Agile Tester (CTAL‑AT) v2.0 certification validates that a candidate can apply advanced testing knowledge in Agile software development projects. It is not a general Agile awareness exam. It tests whether you can make real decisions: how to shape a test strategy using testing quadrants, when to shift left and how to do it properly, how to run exploratory testing with discipline, how to use metrics to drive process improvement, and how to contribute meaningfully to test automation in iterative delivery environments.
The syllabus is built around six examinable chapters covering the full scope of an Agile tester’s responsibilities, from defining test strategies and planning iterations to applying exploratory techniques, assisting with user story quality, and supporting automation. The learning objectives span K2 (Understand), K3 (Apply), and K4 (Analyze) levels, meaning the exam expects you to apply judgment to real scenarios, not just recall definitions.
Accredited training courses require a minimum of 13 hours of instruction spread across at least two days.
What Changed from CTFL-AT to CTAL-AT?
This is not an incremental update. The move from CTFL-AT to CTAL-AT represents a structural change in how ISTQB positions Agile testing knowledge:
Level upgrade from Foundation to Advanced. The predecessor CTFL-AT sat at the Foundation level alongside the core CTFL certification. CTAL-AT v2.0 is an Advanced Level credential, carrying higher expectations for applied and analytical thinking. The exam uses K3 and K4 objectives that require candidates to apply techniques and analyze scenarios, not just explain concepts.
New and rewritten content throughout. The v2.0 syllabus introduces topics that did not exist in CTFL-AT, including tissue testers, vibe testing, test smells, testboarding, storyboarding, user story slicing, the Goal-Question-Metric approach to process improvement, dark launch and canary release testing, and a dedicated shift-left chapter that treats requirements engineering as an active testing concern.
Stronger test management coverage. Where the original CTFL-AT touched on Agile test planning lightly, CTAL-AT v2.0 devotes 210 minutes to test management and process improvement. This includes project test strategy design using the testing quadrants model, test monitoring and control in CI/CD environments, coverage-based test reporting, and metrics-driven process improvement with specific guidance on interpreting and acting on testing data.
Exploratory testing elevated and detailed. The v2.0 syllabus treats exploratory testing as a core Agile discipline with its own sub-framework: test heuristics, test mnemonics (FEW HICCUPPS, SFDIPOT, I SLICED UP FUN, RCRCRC, TERMS), test tours, test charters derived from user stories and epics, session-based test management, and practical guidance on performing exploratory sessions. This is significantly more depth than the original certification offered.
Test smells added as a formal topic. Candidates are expected to recognize and act on test smells in test cases, a practical quality concern that the older syllabus never addressed.
Prerequisites remain the same. Like CTFL-AT, the mandatory entry requirement is holding the ISTQB Foundation Level (CTFL) certificate. Candidates are also strongly recommended to have at least six months of practical experience in Agile or testing contexts before attempting the exam.
Who Should Pursue the CTAL-AT v2.0 Certification?
The CTAL-AT v2.0 is suited to a wider range of roles than its name might suggest:
- Software Testers and Test Analysts working in Scrum, Kanban, SAFe, or other Agile frameworks who want structured knowledge of the advanced techniques their work requires.
- Test Leads and Test Managers who need to define test strategies, plan across iterations, and report on quality status in ways that make sense to Agile stakeholders.
- Developers and Scrum Team Members who contribute to testing activities and want to understand how test techniques, shift-left practices, and testability connect to their day-to-day work.
- Business Analysts and Product Owners who collaborate on acceptance criteria, user story definition, and quality decisions and want to understand how testers approach these artefacts.
- Quality Coaches and Consultants advising Agile teams on improving their testing practices, coverage strategies, and test process metrics.
- Holders of the retired CTFL-AT who want to upgrade their credentials to the current standard and demonstrate Advanced Level competence.
This certification also works well as a companion to other ISTQB Advanced certifications. Candidates holding CTAL-TA, CTAL-TM, or CTAL-TAE will find CTAL-AT v2.0 adds the Agile-specific context that those credentials do not fully cover.
CTAL-AT v2.0 Syllabus Structure
The CTAL-AT v2.0 syllabus is organized into six examinable chapters with a total minimum instruction time of 13 hours:
Chapter 1: Test Strategy and Test Approach Challenges (60 minutes)
This chapter covers the strategic decisions Agile testers face when defining what to test and how. Topics include comparing test types across iteration boundaries, deciding when end-to-end testing is appropriate versus wasteful, evaluating the tradeoffs between formal testing and holistic testing approaches, and selecting regression test strategies that fit the pace and risk profile of an Agile project.
Learning Objectives covered: Comparing test types during and after iterations (K2); explaining when to use end-to-end testing (K2); comparing formal and holistic testing tradeoffs (K2); differentiating regression test approaches (K2).
Chapter 2: People and Teams (60 minutes)
This chapter addresses the human and collaborative side of Agile testing. It covers how testers function within cross-functional teams, including the tension between generalist and specialist roles, how to motivate business representatives to participate in testing activities, and how the whole team approach redistributes quality responsibility. It also introduces the concept of tissue testers and explains when bringing in short-term external testers adds genuine value.
Learning Objectives covered: Comparing generalization and specialization in teams (K2); motivating business representatives to test (K2); explaining the whole team approach (K2); using tissue testers effectively (K2).
Chapter 3: Test Management and Test Process Improvement (210 minutes)
The largest management-focused chapter in the syllabus. It covers two levels of test planning (iteration and release), including how testers contribute to risk-storming sessions and Definition of Done agreements. The testing quadrants model is used as a practical framework for defining project test strategies that balance technology-facing and business-facing tests across all four quadrants.
Test monitoring uses lightweight, continuous approaches such as burn-down charts, cumulative flow diagrams, and automated CI/CD dashboards. Test reporting covers multiple coverage types: requirements coverage, code coverage, exploratory testing coverage via session-based test management, and infrastructure coverage in DevOps environments. The chapter closes with test process improvement, including the Goal-Question-Metric approach, how to interpret declining defect detection percentages, high defect cycle times, and environmental instability, and what improvement actions to take.
Learning Objectives covered: Test planning in Agile (K2); project test strategy using testing quadrants (K4); test monitoring and control in Agile (K2); comparing coverage types for test reporting (K2); selecting process improvement measures from metrics (K4); performing test process improvement (K2).
Key domain-specific terms: canary release, community of practice, dark launch, Definition of Done, feature toggle, Goal-Question-Metric.
Chapter 4: Shift Left (135 minutes)
This chapter defines shift left as a practical discipline, not a slogan. It covers how testware (BDD scenarios, acceptance criteria, checklists, automated test scripts, test charters) acts as living requirements rather than static documentation. Techniques covered include storyboarding for visualizing user journeys and detecting flow gaps, testboarding for aligning testers and developers on what needs to be tested before coding starts, and example mapping for refining user stories through structured conversation.
The chapter also addresses cognitive biases that can reduce product quality when testers or developers assume incorrect things about user behavior or requirements. User story slicing is covered as a technique for ensuring stories are small enough to be genuinely testable within an iteration. The chapter closes with how requirements engineering practices such as interviews, workshops, and prototyping support a shift-left mindset.
Learning Objectives covered: Testware as requirements (K2); storyboarding and testboarding for test basis quality (K2); example mapping (K2); cognitive biases and product quality (K2); user story slicing (K3); requirements engineering and shift left (K2).
Chapter 5: Agile Test Approaches and Test Techniques (285 minutes)
The longest chapter in the syllabus. It covers three main areas:
Exploratory Testing is treated as a structured discipline. Test heuristics are explained in depth, including guidelines, generic checklists, rules of thumb, mnemonics, and analogies. Test mnemonics covered include FEW HICCUPPS, SFDIPOT, I SLICED UP FUN, RCRCRC, and TERMS, each applicable in specific Agile testing contexts. Test tours are covered as a structured way to approach exploratory sessions using metaphors such as the guidebook tour, the money tour, or the saboteur tour. The process of deriving test charters from user stories and epics using the 5W1H technique is covered in detail, including how acceptance criteria translate into both positive and negative test conditions. Candidates are expected to apply exploratory testing in practice, not just describe it.
Assisted Testing covers three collaborative approaches: mob testing (the whole team testing together at one workstation), pair testing (two people testing together with shared responsibility), and vibe testing (informal, conversational testing where a developer and tester assess software together as it is built). Each is explained in terms of when it adds value and how it differs from solo testing.
Test Smells covers the concept of test code and test design quality indicators that signal problems in a test suite: tests that are too long, too fragile, too coupled to implementation, or provide misleading pass results. Candidates must be able to use test smells to evaluate and improve test case quality.
Learning Objectives covered: Test heuristics (K2); test mnemonics (K2); test tours (K2); creating test charters from user stories and epics (K4); applying exploratory testing (K3); mob testing (K2); pair testing (K2); vibe testing (K2); test smells (K3).
Chapter 6: Test Automation and Test Tools (30 minutes)
This chapter covers the Agile tester’s role in test automation, focusing on how automation fits into iterative delivery rather than treating it as a separate workstream. Different automation approaches are distinguished: test-code co-evolution, test-first approaches such as ATDD and BDD, and automation as a regression safety net. It also covers the categories of tools that support Agile testing activities, from exploratory testing tools and defect management systems to task boards, CI/CD pipeline integration tools, and production monitoring and analytics tools.
Learning Objectives covered: Distinguishing automation approaches for Agile (K2); tools that support Agile testing (K2).
Business Outcomes of CTAL-AT v2.0
A candidate certified in CTAL-AT v2.0 should be able to demonstrate the following in practice:
| Code | Business Outcome |
|---|---|
| CTAL-AT-BO1 | Collaborate in cross-functional teams with knowledge of Agile principles and basic practices |
| CTAL-AT-BO2 | Adapt existing testing experience and knowledge to Agile values and principles |
| CTAL-AT-BO3 | Support the Agile team in test planning |
| CTAL-AT-BO4 | Apply Agile test techniques to ensure tests provide adequate coverage |
| CTAL-AT-BO5 | Assist business stakeholders in defining testable user stories, scenarios, and acceptance criteria |
| CTAL-AT-BO6 | Create and implement Agile test approaches across the full development lifecycle |
| CTAL-AT-BO7 | Support and contribute to test automation in Agile projects |
| CTAL-AT-BO8 | Communicate and share information effectively with other team members |
CTAL-AT v2.0 Exam Structure
The CTAL-AT v2.0 certification exam is based entirely on the v2.0 syllabus. All six chapters are examinable. Appendices and introductory sections are not. Referenced standards and books are not examinable beyond what the syllabus itself summarizes.
The sample exam contains 40 questions with varying point values (1, 2, or 3 points per question depending on cognitive complexity). Questions at the K4 level carry higher point values. The exam covers both single-answer and multiple-answer question formats, as well as matching and assignment tasks. Refer to the official ISTQB “Exam Structures and Rules” document for CTAL-AT for the definitive question count, time allocation, and passing threshold.
What the exam actually tests: Exam questions are scenario-based. You will be given realistic Agile team contexts and asked to evaluate strategies, identify appropriate techniques, analyze coverage metrics, or assess the quality of test charters and user stories. Memorizing definitions is necessary but not sufficient. The majority of marks come from K3 and K4 questions that require you to make and justify decisions.
Prerequisites and Recommended Experience
Mandatory requirement: Candidates must hold the ISTQB Foundation Level (CTFL) certificate before sitting the CTAL-AT exam.
Strongly recommended:
- At least six months of practical experience as a system tester, user acceptance tester, or active Agile team member.
- Completion of an accredited training course from an ISTQB member board-accredited provider.
Note that the mandatory entry requirement does not include a specific Agile testing experience threshold. However, candidates without any hands-on exposure to Agile teams will find the K3 and K4 level questions significantly harder to answer correctly, since the exam rewards practical familiarity with the scenarios it presents.
CTAL-AT v2.0 Syllabus and Sample Exam Downloads
The following official documents are available from ISTQB:
- CTAL-AT v2.0 Syllabus – Full syllabus, learning objectives, keywords, and appendices.
- CTAL-AT v2.0 Sample Exam Questions – 40 sample questions covering all six chapters.
- CTAL-AT v2.0 Sample Exam Answers – Full answer rationale mapped to learning objectives and K-levels.
Study Tips for the CTAL-AT v2.0 Exam
Understand the testing quadrants, not just the four boxes. The testing quadrants model (Quadrants 1 to 4) appears throughout the syllabus. Exam questions will give you a product scenario and ask you to assign or evaluate test strategies. Know what belongs in each quadrant and why, especially for domain-constrained environments like finance or healthcare where Quadrant 4 carries more weight.
Work through exploratory testing mnemonics with real examples. SFDIPOT, FEW HICCUPPS, I SLICED UP FUN, RCRCRC, and TERMS all appear in the syllabus and exam. Do not just memorize the acronym expansions. The exam tests whether you can match a mnemonic to the right testing context or recognize which heuristic applies to a given scenario.
Practice writing test charters from user story fragments. Several sample exam questions present a user story or epic and ask you to identify the correct test charter or evaluate test charter quality. If you have never written a real test charter, do it before the exam. The 5W1H framework the syllabus describes is the anchor.
Pay attention to test smells. This is a newer topic that many candidates underestimate. Know the difference between a test smell that indicates a design problem (e.g., a test that always passes regardless of system behavior) versus one that indicates a maintenance problem (e.g., a test too tightly coupled to implementation detail).
Do not neglect the metrics and process improvement questions. Chapter 3’s K4 objectives mean you will encounter scenario-based questions where you are given a set of metrics (defect detection rate, automation coverage percentage, defect cycle time, flaky test rate) and must select or justify the correct improvement action. These questions have multiple plausible distractors. Understand the reasoning, not just the answer.
Use the sample exam under timed conditions. The 40-question sample exam published by ISTQB is the closest approximation available of the real exam’s difficulty and question style. Work through it timed, then review every answer using the official rationale document. Pay special attention to questions you answered correctly for the wrong reason.
Recommended Study Materials for ISTQB Certified Tester Advanced Level Agile Tester (CTAL‑AT) v2.0
Coming soon.