ISTQB CT-QDO: Quality in DevOps Certification Guide (2026)

ISTQB CT-QDO (Certified Tester Quality in DevOps) is a Specialist-level ISTQB certification, released on 27 May 2026, that covers how QA and testing work across the whole DevOps value stream: CI/CD pipelines, continuous testing, release strategies and feedback from production. The exam has 40 multiple-choice questions worth 45 points, the pass mark is 30 points (about 67%), it lasts 60 minutes, and CTFL is the prerequisite.

This guide summarizes the official v1.0 syllabus: exam format, the four chapters and their weight, the K3 objectives that carry the hardest questions, and a study plan that fits around a full-time job.

What is the ISTQB CT-QDO certification?

CT-QDO is the first ISTQB certification built entirely around DevOps. The syllabus v1.0 was approved by the ISTQB General Assembly on 17 April 2026 and published on 27 May 2026. Its core idea is that in DevOps, quality engineering happens in every lifecycle phase, and quality is the whole team's responsibility rather than a separate test phase at the end.

ISTQB names a wide audience: testers, test analysts, test automation engineers and test managers, but also developers, DevOps engineers, site reliability engineers (SRE), operations engineers, Scrum Masters and product owners. If you already run tests inside a pipeline, most of the syllabus will describe things you do every week; the certification gives them a shared vocabulary.

CT-QDO exam format at a glance

• Questions: 40 multiple-choice

• Total points: 45 (some questions are worth more than one point)

• Pass mark: 30 points, which is 66.7%

• Duration: 60 minutes, plus 25% (75 minutes) for non-native speakers

• Prerequisite: ISTQB CTFL, v4.0 or any earlier version

• Validity: lifetime, no renewal

Because the exam counts points, not questions, two wrong answers on multi-point items can cost more than three wrong one-pointers. Our article on how ISTQB exam scoring works with points instead of questions explains how to budget your time around that.

What does the CT-QDO syllabus cover?

The syllabus has four chapters with a total minimum training time of 1,210 minutes (20.2 hours). ISTQB does not publish a per-chapter question split, but training time is a reasonable proxy for where the effort goes.

1. Fundamentals of DevOps (140 min, ~12%). Key DevOps concepts, the wall of confusion between development and operations, DORA performance metrics, CALMS, the three ways of DevOps, team roles, SRE, and team patterns and anti-patterns.

2. QA and Testing in DevOps (360 min, ~30%). QA across the value stream, continuous testing, how pull requests support quality, and QA in continuous discovery, continuous integration, continuous delivery, continuous deployment and release on demand. Includes building a CI/CD pipeline step by step.

3. Automated and Manual Tasks in DevOps (510 min, ~42%). The largest chapter: a single source of truth for testware, automated traceability, quality reporting in the pipeline, test data and test environment management, regression testing in CI/CD, API and contract testing, plus manual work such as exploratory testing, crowd testing and quality hunting events.

4. Tools and Practices in DevOps (200 min, ~17%). Tool capabilities and selection, non-testing pipeline activities, release strategies (blue-green, canary), infrastructure as code, feature toggles, branching strategies, chaos engineering, telemetry and observability, SBOM and containerization.

DORA metrics you must know

Learning objective QDO-1.1.3 (K2) asks you to explain the four DORA delivery metrics. Two measure throughput: change lead time (commit to successful production deployment) and deployment frequency. Two measure stability: change fail percentage (deployments that need a hotfix or rollback) and failed deployment recovery time. Reliability (availability, latency, performance efficiency, scalability) is added as an operational indicator. Expect questions that ask which metric a scenario improves.

CALMS in a QA context

CALMS stands for Culture, Automation, Lean, Measurement and Sharing. The syllabus uses it as a framework to assess how ready an organization is for DevOps, and QDO-1.1.4 (K2) asks you to tell the elements apart from a QA point of view. A typical question describes a team habit, for example publishing test dashboards to everyone, and asks which element it represents.

Which CT-QDO objectives are K3?

CT-QDO uses K1 (remember), K2 (understand) and K3 (apply). If the K-levels are new to you, read ISTQB K-levels explained first. The five K3 objectives produce the scenario questions that are most often worth extra points:

• QDO-2.1.1 implement QA activities in a DevOps context

• QDO-2.2.6 apply QA and testing knowledge to implement a CI/CD pipeline

• QDO-3.1.3 implement uniform quality reporting in the CI/CD pipeline

• QDO-3.2.2 prepare API testing

• QDO-3.3.4 apply quality hunting events to support a culture of learning

The pipeline objective follows a concrete sequence from the syllabus: model the value stream from commit to release and create a walking skeleton, automate build and deployment, automate the commit stage (split it into parallel jobs once it runs longer than about five minutes), then automate the acceptance stage. Learn that order; it is easy to test.

Who should take CT-QDO?

CT-QDO fits testers who work in teams that deploy often and want to move from "the person who runs the regression suite" to someone who shapes the pipeline, release strategy and production feedback. It is not a tool certification: you will not be asked about Jenkins or GitHub Actions syntax. If you want hands-on tool skills, a tool-specific exam such as the A4Q Selenium Tester certification complements it well. For where CT-QDO sits among all ISTQB exams, see our ISTQB certification path for 2026.

How to prepare for CT-QDO: a 4-step plan

1. Read the syllabus once, end to end. Download CT-QDO syllabus v1.0 from ISTQB and mark every keyword listed at the start of each chapter. Keywords are examinable at K2 even if no objective mentions them.

2. Spend most of your time on chapters 3 and 2. Together they make up about 72% of training time and contain four of the five K3 objectives.

3. Map the syllabus to your own pipeline. For each stage (commit, acceptance, deployment, release) write down which tests run, who reads the results and how a failure is handled. This turns abstract K3 objectives into answers you can reason about.

4. Do the official sample exam under time pressure. Take it in 60 minutes, then study the rationale for every wrong answer and the learning objective it maps to.

CTFL is the gate to CT-QDO. If you have not passed it yet, start with our free ISTQB CTFL mock exams, each with a rationale for every answer. A dedicated CT-QDO practice test is on the ExamCaliber roadmap.

Is CT-QDO worth it in 2026?

For testers in DevOps teams, yes, with one caveat. The certification is brand new, so recruiters may not recognize it yet, and there are few third-party practice resources. The upside is the same: competition for the credential is low, the syllabus is current (DORA 2024, SBOM, observability, chaos engineering) and the content maps directly to work most teams already do. Take it for the structured knowledge first and the line on your CV second.