ISTQB CTAL-ATT study plan

Map the four CTAL-ATT domains to their exam weightings and write a one-page gap analysis of your weakest two domains

Explain how agile requirements engineering differs from plan-driven requirements engineering, using at least three concrete practices as evidence

Practise writing user stories with acceptance criteria in Given/When/Then form for a small feature and mark which criteria are testable as written

List the requirement-quality criteria (unambiguous, complete, consistent, verifiable, traceable) and apply them to critique five sample stories

Analyse how requirements flow from vision to epic to story to acceptance criteria and identify where testers intervene at each level

Distinguish functional from non-functional requirements and describe how each is elicited and verified in agile teams

Explain specification by example and collaborative test design sessions, stating the tester's role and the artefacts produced

Identify requirement risks (ambiguity, missing negative cases, untestable constraints) and propose a mitigation for each

Describe the roles and responsibilities in an agile team and explain how the tester's role shifts across the sprint lifecycle

Explain whole-team quality ownership and how it changes planning, estimation, and definition of done

Compare at least three agile test planning approaches (release planning, sprint planning, just-in-time) and state when each is appropriate

Explain how retrospectives and continuous improvement feed back into test strategy

Apply test pyramid and test quadrant concepts to classify tests by level and by purpose

Design a sprint test approach that balances exploratory, automated, and manual testing for a given risk profile

Explain how to scale agile testing across multiple teams, including coordination of test effort and shared quality standards

Evaluate metrics used in agile testing (escaped defects, cycle time, automation coverage) and identify their misuse

Explain the purpose and design principles of a test automation architecture, including layers and separation of concerns

Compare at least four design patterns for test automation (page object, screenplay, factory, singleton) and state trade-offs

Describe how to select what to automate using risk, frequency, stability, and cost-benefit reasoning

Identify maintainability risks in automation suites and propose concrete refactoring responses

Explain how to design and organise a test automation framework for reuse, reporting, and CI integration

Describe the risks of brittle tests and flaky results, and design strategies to detect and reduce them

Explain how test data and test environment management affect automation reliability

Plan the metrics and reporting needed to judge whether automation delivers value

Explain continuous integration, continuous delivery, and continuous deployment and distinguish their test implications

Describe how deployment pipelines gate releases and where automated and manual checks belong

Explain release and deployment risk assessment, including rollback and feature-flag strategies

Identify the tester's responsibilities in production monitoring and post-release verification

Synthesise the four domains into a single end-to-end quality approach for one sample product

Answer timed practice questions across all domains and analyse errors by domain and by question type

Revisit the week-one gap analysis and close remaining weak areas with targeted review

Build a personal exam-day strategy covering time allocation, question triage, and review of flagged items