The ISTQB Certified Tester Quality in DevOps (CT-QDO) is a brand new Specialist certification released on May 27, 2026. It is the first ISTQB certification built specifically around quality assurance and testing within DevOps environments. If your team delivers software through CI/CD pipelines, automates deployments, and operates under a DevOps culture, this certification validates your ability to embed quality into every stage of that process.
DevOps has become the dominant way organizations build and ship software. But most testing certifications still treat quality as something that happens in a separate phase, usually after development, usually by a separate team. CT-QDO breaks that model. It recognizes that in DevOps, quality engineering happens continuously across the entire value stream, from planning through coding, building, testing, releasing, deploying, operating, and monitoring. The certification teaches you how to make that work in practice, not just in theory.
CT-QDO joins a batch of new ISTQB certifications released in May 2026, alongside CT-FT (Finance Testing) and CTAL-AT v2.0 (Advanced Agile Tester). Together, they represent ISTQB’s push to stay relevant to how software is actually built and tested today.
What is the ISTQB CT-QDO Certification?
The CT-QDO certification supports professionals involved in software development based on DevOps by teaching them how to apply proper quality and testing activities to achieve the right quality level for their solutions. It extends the ISTQB Foundation Level (CTFL) with DevOps-specific knowledge that goes deeper than what CTFL covers in its Agile and DevOps sections.
Where CTFL introduces the concept of testing in DevOps at a high level, and the Agile Tester certification focuses on testing inside Agile teams, CT-QDO takes a different angle entirely. It treats quality as a cross-cutting concern across the full DevOps value stream. It covers how CI/CD pipelines support quality, how automated and manual testing fit together in DevOps teams, what tools and practices enable quality engineering at speed, and how organizations actually implement DevOps in a way that does not sacrifice quality for velocity.
The syllabus introduces key DevOps metrics like deployment frequency, change lead time, change fail percentage, and failed deployment recovery time. These are not just theory. They are the DORA metrics that modern engineering organizations use to measure their delivery performance, and the syllabus connects them directly to quality assurance activities.
Who Should Take the CT-QDO Certification?
CT-QDO is designed for professionals engaged in quality and testing within a DevOps environment. The target audience is deliberately broad, because the whole point of DevOps is that quality is everyone’s responsibility.
Testers, Test Analysts, and Test Engineers who work in DevOps teams and want to understand how their role fits into the broader value stream, and how to contribute to quality beyond writing and running test cases.
Test Automation Engineers who build and maintain CI/CD test pipelines and want to formalize their understanding of how automated testing supports quality in DevOps.
Software Developers and DevOps Engineers who want to understand testing and quality engineering from a structured perspective, rather than learning it piecemeal on the job.
Site Reliability Engineers (SREs) and Operations Engineers who maintain production systems and want to understand how quality engineering in earlier value stream stages reduces incidents and improves service reliability.
Test Managers and Quality Leads responsible for defining quality strategies in DevOps organizations, especially those transitioning from traditional waterfall or siloed testing approaches.
Scrum Masters and Product Owners who need to understand how quality engineering integrates into DevOps workflows so they can support their teams effectively.
This aligns with the DevOps principle that quality is a shared responsibility across the entire team, not a gate owned by a separate QA department. The certification establishes a common language and methodology for quality engineering that all these roles can share.
CT-QDO Syllabus Structure
The CT-QDO v1.0 syllabus is organized into four examinable chapters with a minimum of 20.2 hours of instruction time, divided over at least three days. This makes it one of the larger Specialist certifications in terms of training time, reflecting the breadth of material it covers.
The syllabus includes both learning objectives (K1 Remember, K2 Understand, K3 Apply) and hands-on objectives (H0 demo, H1 guided exercise, H2 exercise with hints). The hands-on component is a notable feature. Many ISTQB syllabi are purely knowledge-based, but CT-QDO builds in practical exercises like designing CI/CD pipelines, which makes accredited training courses especially valuable for this certification.
Chapter 1: Fundamentals of DevOps
This chapter establishes the foundational concepts that the rest of the syllabus builds on. You will learn what DevOps is, where it came from, and how it relates to Agile software development. The chapter covers the CALMS framework (Culture, Automation, Lean, Measurement, Sharing), which provides a structured way to understand the pillars of DevOps culture.
Key topics include the definition of DevOps, cross-functional DevOps teams, feedback loops, flow, and the four key DORA metrics: deployment frequency, change lead time, change fail percentage, and failed deployment recovery time. These metrics appear throughout the syllabus because they are the primary way organizations measure whether their DevOps adoption is actually improving delivery performance and quality.
The chapter also covers service level agreements (SLAs) and how they connect to quality expectations in DevOps environments. Understanding SLAs is important because they define the quality thresholds that DevOps teams must meet in production.
Chapter 2: Quality Assurance within DevOps
This is the core chapter of the syllabus, covering how quality assurance is practiced within DevOps organizations. It addresses multiple interconnected topics.
Implementing DevOps in an Organization covers the practical aspects of DevOps adoption, including organizational change, team structures, and how to transition from traditional development models to DevOps ways of working. This is not just theory. Many organizations struggle with DevOps adoption because they focus on tools while ignoring the cultural and organizational changes needed.
QA and Testing in DevOps covers how testing integrates into DevOps workflows. In a traditional model, testing happens after development in a separate phase. In DevOps, testing is continuous and embedded into the delivery pipeline. This section explains how that works in practice.
Contribution in the Value Stream to Assist in Quality Engineering teaches you how to contribute to quality at every stage of the DevOps value stream. This goes beyond testing. It includes activities like participating in planning, reviewing code, defining acceptance criteria, monitoring production, and using feedback loops to drive improvements.
DevOps Loop Implementation covers the practical design and implementation of CI/CD pipelines, including what stages to include, what capabilities the tooling needs, and how the pipeline supports the DevOps feedback loop. This section includes a hands-on exercise (H2 level) where you design and implement a CI/CD pipeline.
Chapter 3: Automated and Manual Tasks in DevOps
This chapter addresses one of the most practical questions in DevOps quality engineering: what should be automated, what should remain manual, and how do you make the right decision?
Automation’s Support for QA in DevOps covers how automation enables continuous quality assurance across the DevOps pipeline. This goes beyond test automation to include infrastructure automation, deployment automation, and monitoring automation.
Automated Testing in DevOps Teams covers specific approaches to automated testing within DevOps, including how automated tests are integrated into CI/CD pipelines, how to design test suites that run fast enough for continuous delivery, and how to maintain automated tests at scale. If you have explored the Test Automation Engineer (CTAL-TAE) certification, this section connects those concepts to the DevOps context.
Manual Testing in DevOps Teams covers the role that manual testing still plays in DevOps environments. Contrary to what some DevOps evangelists claim, manual testing does not disappear in DevOps. Exploratory testing, usability testing, and certain types of acceptance testing remain valuable. This section explains where manual testing fits and how to integrate it into rapid delivery cycles without creating bottlenecks.
Chapter 4: Tools and Practices in DevOps
This chapter covers the tooling ecosystem and engineering practices that enable quality in DevOps.
Tools Supporting DevOps within the Organization covers the categories of tools that DevOps teams use, from CI/CD servers and version control to monitoring, logging, and alerting platforms. The syllabus does not prescribe specific tools, but it teaches you how to evaluate and select tools based on your organization’s needs.
Technologies and Practices to Support Quality in DevOps covers engineering practices like infrastructure as code, containerization, feature toggles, blue-green deployments, canary releases, and other deployment strategies that affect quality. These practices are how modern teams manage the risk of frequent deployments while maintaining quality.
CT-QDO Exam Structure and Details
Here are the verified exam figures from the official ISTQB CT-QDO certification page:
Number of questions: 40 multiple-choice questions
Total points: 45
Pass score: 30 points (66.7% of total points)
Exam duration: 60 minutes (75 minutes for non-native language speakers, with the standard 25% extension)
Prerequisite: ISTQB Certified Tester Foundation Level (CTFL) certification
No negative marking: Wrong answers do not reduce your score, so you should answer every question
The exam includes a mix of 1-point and 2-point questions. K3 (Apply) level questions carry more weight and require you to apply DevOps quality engineering concepts to given scenarios. Familiarity with how K-level questions work is essential for effective preparation.
A notable difference from some other ISTQB exams: keywords in the CT-QDO syllabus are tested at K2 (Understand) level, not K1. This means you need to understand and explain the concepts behind terms like CALMS, deployment frequency, and change lead time, not just recall their definitions.
Business Outcomes of CT-QDO
A certified professional holding the CT-QDO credential should be able to:
BO1: Explain how quality assurance is supported by and contributes to the DevOps concepts.
BO2: Understand the concepts of implementing DevOps in an organization.
BO3: Contribute to all value stream stages to assist in quality engineering.
These three business outcomes are deliberately concise but broad. They reflect the certification’s focus on embedding quality across the entire DevOps lifecycle, not just in the testing phase.
How CT-QDO Fits into the ISTQB Certification Scheme
CT-QDO sits in the Specialist stream of the ISTQB certification scheme, alongside other domain-specific and technique-specific certifications. The only prerequisite is CTFL. No Advanced Level certification is required. The certification is valid for life.
Here is how CT-QDO relates to other ISTQB certifications you may be considering:
CT-QDO vs. Agile Tester (CTFL-AT / CTAL-AT): The Agile Tester certifications focus on testing within Agile teams. CT-QDO goes further by covering the entire DevOps value stream, including deployment, operations, and monitoring. Agile Tester is about being an effective tester in an Agile team. CT-QDO is about being an effective quality engineer in a DevOps organization. The recently released CTAL-AT v2.0 takes Agile testing to the Advanced Level, but CT-QDO addresses a different (and complementary) dimension.
CT-QDO vs. Test Automation Engineer (CTAL-TAE): The CTAL-TAE certification teaches you how to build and maintain test automation solutions. CT-QDO teaches you how test automation fits into DevOps pipelines and supports continuous quality. CTAL-TAE goes deep on automation architecture. CT-QDO goes broad on the DevOps quality context around it.
CT-QDO vs. CT-AI and CT-GenAI: The CT-AI and CT-GenAI certifications focus on AI-specific testing concerns. CT-QDO focuses on DevOps-specific quality concerns. These are complementary certifications for different aspects of modern software delivery.
CT-QDO vs. Test Automation Strategy (CT-TAS): The CT-TAS certification covers strategic planning for test automation programs. CT-QDO covers quality strategy in DevOps more broadly, with automation being one component alongside practices, tools, and organizational factors.
For professionals building a modern testing career, a strong combination would be CTFL for the foundation, CT-QDO for DevOps quality engineering, and either CTAL-TAE or CT-TAS for automation depth.
How to Prepare for the CT-QDO Exam
Read the official syllabus. The CT-QDO v1.0 syllabus is available as a free download from istqb.org. With 20.2 hours of minimum instruction time, this is a substantial syllabus. The exam is derived entirely from the syllabus content, so thorough reading is essential.
Download and work through the sample exam. ISTQB has released sample exam questions and answers for CT-QDO. Use these to calibrate your understanding of how the syllabus translates into exam questions, especially for K3 (Apply) questions where you need to apply concepts to scenarios.
Prioritize hands-on understanding. The CT-QDO syllabus includes hands-on objectives that involve designing CI/CD pipelines and working with DevOps tools. Even if you are self-studying, set up a basic pipeline (using free tools like Jenkins, GitLab CI, or GitHub Actions) and practice the concepts from the syllabus.
Learn the DORA metrics. Deployment frequency, change lead time, change fail percentage, and failed deployment recovery time are central concepts. Understand what each metric measures, how it connects to quality, and how testing activities influence each one.
Consider accredited training. Given the hands-on objectives in the syllabus, accredited training courses are especially valuable for CT-QDO. The practical exercises make the concepts concrete in a way that pure self-study cannot replicate.
Leverage existing DevOps experience. If you already work in a DevOps environment, connect the syllabus concepts to your daily work. The CALMS framework, value stream mapping, and CI/CD pipeline design will map directly to what you see in your organization.
For study materials and practice exams across all ISTQB certification levels, visit the ISTQB Guru study materials hub. CT-QDO practice materials will be available soon.
CT-QDO vs. Other DevOps Certifications
CT-QDO is not the only DevOps certification on the market, and it is worth understanding how it compares to alternatives.
The DevOps Institute offers several DevOps certifications (DevOps Foundation, DevOps Leader, SRE Foundation), but these focus on DevOps practices, culture, and leadership rather than on quality and testing specifically. CT-QDO is unique in its focus on quality engineering within DevOps.
SAFe DevOps Practitioner (SDP) focuses on applying DevOps within the Scaled Agile Framework. It is tied to a specific framework. CT-QDO is framework-agnostic and applies to any DevOps implementation.
AWS, Azure, and Google Cloud DevOps certifications are vendor-specific and focus on implementing DevOps using a particular cloud platform’s tools. CT-QDO is vendor-neutral and focuses on principles and practices that apply regardless of your technology stack.
The key differentiator for CT-QDO is its ISTQB pedigree. It is part of the ISTQB certification scheme that is recognized in over 130 countries, and it builds on the CTFL foundation that many employers already require or prefer for testing professionals.
Frequently Asked Questions (FAQ)
1. What is the ISTQB CT-QDO certification?
ISTQB CT-QDO (Certified Tester Quality in DevOps) is a Specialist level certification that covers quality assurance and testing within DevOps environments. It addresses DevOps fundamentals, QA in the DevOps value stream, automated and manual testing in DevOps teams, and the tools and practices that support quality in DevOps.
2. What are the prerequisites for the CT-QDO exam?
You must hold a valid ISTQB Certified Tester Foundation Level (CTFL) certification. No Advanced Level certification is required. DevOps experience is helpful but not mandatory.
3. How many questions are on the CT-QDO exam, and what is the pass score?
The exam has 40 multiple-choice questions worth a total of 45 points. You need 30 points (66.7%) to pass. There is no negative marking.
4. How long is the CT-QDO exam?
The exam duration is 60 minutes. Non-native language speakers receive a 25% extension, giving them 75 minutes.
5. When was the CT-QDO syllabus released?
The CT-QDO v1.0 syllabus was released on May 27, 2026. It was announced alongside CT-FT (Finance Testing) and CTAL-AT v2.0 (Advanced Agile Tester) at the ISTQB General Assembly.
6. Does the CT-QDO certification expire?
No. Like all ISTQB Specialist certifications, CT-QDO is valid for life once earned.
7. How is CT-QDO different from the ISTQB Agile Tester certification?
The Agile Tester certification focuses on testing within Agile teams, covering practices like TDD, BDD, and iterative testing. CT-QDO goes further by covering the entire DevOps value stream including CI/CD pipelines, deployment automation, monitoring, and how quality engineering spans all these stages. They are complementary, not overlapping.
8. Is CT-QDO relevant if I am a developer, not a tester?
Yes. CT-QDO is designed for everyone involved in DevOps quality, including developers, DevOps engineers, SREs, and product owners. The DevOps principle that quality is everyone’s responsibility is central to this certification.
Start Your CT-QDO Journey
DevOps adoption continues to accelerate across industries. The 2024 State of DevOps Report from DORA found that elite performing teams deploy multiple times per day with change fail rates under 5%. These teams do not achieve that by skipping quality. They achieve it by embedding quality into every stage of the value stream, exactly what CT-QDO teaches.
If you are building, testing, or operating software in a DevOps environment, this certification gives you a structured framework for doing quality right. If you are transitioning to DevOps from a traditional testing background, it provides a clear bridge between what you already know from CTFL and what DevOps quality engineering demands.
The syllabus is freely available, sample exam questions are published, and exams are live. For study materials across all ISTQB certifications and the latest news on certification releases, visit the ISTQB Guru articles and blog section.