ISTQB® Acceptance Testing (CT-AcT)

The CT-AcT syllabus spends more time on Gherkin and ATDD/BDD scenario writing than on any other single skill, and it shows in the exam: candidates who can recite the definitions but haven't actually written a Given-When-Then scenario against a business rule tend to lose marks on the K3 "apply" questions. This is a specialist-level exam that sits on top of the ISTQB Foundation Level, not a beginner test, and it rewards people who've sat in refinement sessions arguing over what "done" means for a user story.

What  CT-AcT Exam Actually Tests

CT-AcT isn't a general testing exam wearing an "acceptance testing" label. It's built around five syllabus areas, and the exam questions track them closely:

• Introduction and Foundations — the different flavors of acceptance testing (user acceptance testing, contractual/regulatory acceptance testing, alpha and beta testing), and how acceptance testing differs from other test levels. Note that operational acceptance testing (OAT) is deliberately excluded from this syllabus, since ISTQB treats that as an ops-team responsibility rather than a tester/BA one — a distinction the exam likes to probe.

• Acceptance Criteria, Acceptance Tests, and Experience-Based Practices — the largest chunk of the syllabus. This covers writing and reviewing acceptance criteria collaboratively with business analysts, Acceptance Test-Driven Development (ATDD), Behavior-Driven Development (BDD), the Gherkin language (Given/When/Then, backgrounds, scenario outlines), and experience-based approaches like exploratory testing and beta testing sessions.

• Business Process and Business Rules Modeling — reading and reviewing BPMN process diagrams and DMN decision tables, and using them to derive acceptance test cases and achieve decision coverage. If you've never worked with BPMN notation before, this is the section that will feel least familiar.

• Acceptance Testing for Non-Functional Requirements — quality-in-use characteristics from ISO 25010, usability and UX testing, and how performance efficiency and security get folded into acceptance criteria rather than treated as separate test phases.

• Collaborative Acceptance Testing — reviews, workshops, and the practical mechanics of getting testers, business analysts, and stakeholders aligned on what "accepted" means.

Who Takes  CT-AcT Exam

CT-AcT draws a specific crowd: testers who already hold ISTQB Foundation Level (CTFL) and now sit closer to the business side — working directly with product owners and business analysts rather than purely in a QA silo. Business analysts and product owners who want formal grounding in acceptance criteria and ATDD also show up in the candidate pool, since the syllabus is explicitly written for collaboration between these roles, not just for testers working alone. It's common in organizations running Agile teams where "who writes the acceptance criteria" is a live question rather than a solved one.

CT-AcT Exam Format Details

The  official ISTQB (CT-AcT) exam is 40 multiple-choice questions in 60 minutes (75 minutes if you're sitting it in a non-native language). The pass mark is 65%, meaning you need at least 26 correct answers. Questions are pitched across three cognitive levels — K1 (recall), K2 (understand), and K3 (apply) — and the K3 questions are where most people lose time. These typically hand you a short scenario (a user story, a BPMN fragment, a partial Gherkin scenario) and ask you to identify the correct next step or spot the flaw, rather than just define a term. Foundation Level (CTFL) certification is a prerequisite to sit CT-AcT, so if you haven't passed that yet, this isn't your starting point.

How to Use  CT-AcT  Practice Test Effectively

Don't just drill definitions — the exam is heavier on application than recall for a specialist paper. When you hit a practice question built around a BPMN diagram or a Gherkin snippet, actually trace through it rather than pattern-matching to the answer that "sounds right." If you get a question on writing acceptance criteria for a user story, try rewriting it yourself before checking the given answer; the exam frequently tests whether you can spot criteria that are too vague, too implementation-specific, or missing a testable condition. Time yourself in blocks that mimic the 60-minute window so you get a feel for how long the scenario-based questions actually take versus the straight recall ones.

Common Mistakes Candidates Make

The most frequent error is treating ATDD and BDD as interchangeable in every context. They're closely related, but the syllabus draws a specific distinction: BDD is associated with using Gherkin to write acceptance tests, while ATDD covers a broader range of textual or graphical acceptance test design approaches, including business process models. Exam questions sometimes hinge on exactly this line.

A second common trap is misreading BPMN gateways when a question asks about decision coverage — candidates count "paths through the diagram" using intuition rather than systematically tracing each gateway branch, and end up with the wrong number of required test cases. Third, on non-functional questions, candidates often try to slot ISO 25010 quality-in-use characteristics (effectiveness, efficiency, satisfaction, freedom from risk, context coverage) into the same bucket as product quality characteristics (like usability or performance efficiency), when the exam expects you to know these are two separate models.

Study Tips Specific to CT-AcT

Since the Acceptance Criteria/ATDD/BDD chapter accounts for the largest share of syllabus content, don't spread your revision time evenly across all five chapters — weight it toward Gherkin syntax and ATDD/BDD comparison questions first. Get comfortable reading a DMN decision table cold; the exam won't teach you the notation in the question, it assumes you can already interpret rows, columns, and hit policies. If BPMN is new to you, spend time specifically on gateway types (exclusive, parallel, inclusive) since that's where decision-coverage questions live. Finally, keep the ISO 25010 quality-in-use model and the broader product quality model on two separate mental shelves — the exam tests the boundary between them more than either model in isolation.

Next Step

Run through the free questions below in exam conditions — 40 questions, one sitting, no pausing to look things up. Then go back through anything you missed and trace it against the specific syllabus section it came from (the topic breakdown below will point you to the right chapter) rather than just re-reading the explanation once and moving on.