ISTQB CTAL-ATT case studies
ISTQB CTAL-ATT · Put your knowledge to work in context.
The ISTQB Certified Tester Advanced Level Agile Technical Tester (CTAL-ATT) is an advanced-level, vendor-neutral certification that introduces the technical testing skills needed in organizations using an Agile development approach: Agile testing techniques, test automation approaches, and continuous deployment and delivery. It is aimed at people who want to deepen their expertise in the technical testing aspects of an Agile context. The syllabus content is organized around four areas: Requirements Engineering (requirements engineering techniques), Testing in Agile (Agile software development and test techniques, experience-based testing, aspects of code quality), Test Automation (test automation techniques and levels of automation), and Deployment and Delivery (continuous integration, continuous testing and continuous delivery, and service virtualization). The stated business outcomes include defining testable requirements within an Agile team, selecting Agile test approaches, contributing to test automation, supporting continuous integration and continuous delivery and deployment, and applying service virtualization concepts. The ISTQB CTAL-ATT case studies are 5 cases and about 2,991 words.
1Acceptance Criteria That Cannot Fail
Northwind Insurance is six sprints into rebuilding its claims intake portal. The product owner writes user stories with acceptance criteria such as 'the claim form must be intuitive' and 'the system must respond quickly'.
683 words, about 3 min2The Hardening Sprint and the 2.5-Day Regression Run
Atlas Retail has five developers and three testers working in two-week sprints. Regression testing is a 2.5-day manual run of 240 scripted cases executed at the end of each sprint.
618 words, about 3 min31,200 UI Tests and a Request for More Agents
Vertex Banking has 1,200 Selenium UI regression tests covering its online account application. A full run takes 9 hours on two agents.
581 words, about 3 min4Config Drift and a 45-Minute Checkout Outage
ShopStream deploys to production about 20 times a week through a CI/CD pipeline. There are four environments: dev, test, staging and production.
546 words, about 3 min5Three Teams, One Shared Integration Environment
Three teams - Accounts, Payments and Notifications - build a single customer platform using Scrum on the same two-week cadence but with different start days. All three deploy to one shared integration environment booked through a spreadsheet; Payments holds it for four days each sprint for end-to-end testing.
563 words, about 3 min