DevOps QA: why testing now lives in the CI/CD pipeline, and what the US data says

A few years ago, a tester received a build, tested it and gave a verdict. Today code goes through a pipeline that builds, tests and ships on every change. A tester who cannot read that pipeline only sees part of the work. This article looks at what recent US-based studies say about it, and at what our DevOps QA specialisation offers.

What changes: testing is no longer "the last step"

In a team that ships often, nobody waits for a tester to open a spreadsheet of test cases. Automated checks start on every code change, and the pipeline stops when a test fails. The tester gains a more visible role: deciding which tests run, when, in which environment, and how to read a failure.

Employers in France already ask for it. In our QA skills barometer of 2 October 2026, CI/CD appears in 35.1% of the 405 QA job ads we analysed. That is a French sample, not a US one, but it points the same way. Our article on test automation in CI/CD has concrete examples with Jenkins, GitLab CI and GitHub Actions.

What the US-facing data says, and its limits

Here are public figures that matter for a tester working in or for US teams. Each one measures something specific. None of them measures "the market for DevOps testers", and we do not claim otherwise.

• Kubernetes in production. In the CNCF Annual Cloud Native Survey 2025, published on January 20, 2026, 82% of container users run Kubernetes in production, up from 66% in 2023. In the same survey, 98% of organisations say they have adopted cloud native techniques and 59% say much or nearly all of their development and deployment is cloud native.
• A cultural obstacle first. The same CNCF survey names "cultural changes with the development team" as the top challenge (47%). CNCF says it is the first time the main challenge is organisational rather than technical. For a tester, being able to work with developers weighs as much as knowing the tools.
• AI speeds up code, not trust. The 2025 DORA report from Google Cloud (September 23, 2025, nearly 5,000 technology professionals surveyed) says AI adoption among software professionals reached 90%, and is now linked to higher software delivery throughput. It also notes that the ongoing challenge is making sure software works as intended before it reaches users. That is exactly where testing sits.
• Jobs. The US Bureau of Labor Statistics projects employment of software developers, quality assurance analysts and testers to grow 10% from 2025 to 2035. For the QA analysts and testers line alone, it counts 187,600 jobs in 2025 and projects 198,200 in 2035, a 6% increase. The BLS groups these roles with developers for pay, and its page does not break out DevOps testing, so we quote no salary here.

CI/CD, Docker, Kubernetes: seen from the test side

Four simple ideas, without needless jargon.

CI/CD: tests on every commit

A pipeline runs tests automatically when a change arrives. The tester chooses what runs on every commit (fast), on every merge (broader) and overnight (long). A flaky test that fails the pipeline for no reason costs the whole team its trust, so the job is as much about making tests reliable as automating them.

Docker: the same environment everywhere

A container packages the application and its dependencies. For a tester it ends "it works on my machine": you start the same environment locally and in the pipeline, with controlled test data.

Kubernetes: knowing where tests run

When the application runs on Kubernetes, test environments are created and destroyed there. You do not need to administer a cluster. You need to understand enough to run your tests in the right place and to read a log when something does not start.

Observability: seeing what happens after release

Logs, metrics and traces help explain a failure and spot a regression the tests missed. The programme page lists observability next to CI/CD and containers.

ADC's DevOps QA specialisation

This is what the programme page says, and nothing more.

• Goal: CI/CD, Docker, Kubernetes and observability, "become an expert in testing at DevOps speed", with tests on every commit rather than once a month.
• Format: 399 hours over 3 months, 100% online, one-on-one mentoring included.
• Access: learning platform for 6 months, replays for 24 months.
• Schedule: next session announced for December; exact dates are confirmed with an advisor.
• Language: the programme pages state that ADC courses are taught in French.

Price. €1,500 launch price for individuals (1 to 4 interest-free instalments), €7,500 for companies. We do not promise any certification for this specialisation here; that is to be confirmed with ADC. Public funding schemes are not yet available at ADC, and we do not promise them.

No programme guarantees a job or a salary. What you can expect is a framework, a mentor and projects to learn how to run your tests in a pipeline, with the tools teams actually use.

Questions about your situation (starting level, funding, schedule)? Talk to an advisor, or read the DevOps QA programme page.

Frequently asked questions

Written by Oussama Belakhdar with AI assistance. Market figures come from the sources above, checked on October 19, 2026; programme details come from the specialisation page.