Continuous Testing Foundation study guide
Continuous Testing Foundation · Work through your exam, one topic at a time.
The Continuous Testing Foundation (CTF)℠ certification is offered by DevOps Institute, now part of the PeopleCert Group. It is aimed at professionals who want to build or validate skills in integrating testing across the continuous delivery pipeline - the source describes continuous testing as enabling "faster, higher quality releases and reduced costs by seamlessly integrating into the Continuous Delivery process to identify and address risks at all stages of the development pipeline thereby minimizing business risk and impact on customers." The published target audience spans developers, DevOps engineers, quality assurance teams and managers, testers, release managers, project managers, IT managers, maintenance and support staff, and lab staff. The Continuous Testing Foundation study guide has 8 sections and about 3,230 words.
01DevOps Continuous Testing Concepts, Terminology, and Benefits
This domain tests whether you can define continuous testing precisely, separate it from test automation and from continuous delivery, and state its benefits in business and risk terms rather than as slogans. Continuous testing (CT) is testing performed throughout the delivery pipeline, at every stage, to give fast feedback on the business risk of a release candidate.
471 words, about 2 min02DevOps Continuous Testing and Culture
This domain examines the cultural conditions that make continuous testing work: shared ownership of quality, blameless learning, transparent feedback, and collaboration across development, testing and operations. Whole-team quality : developers, testers and operations share responsibility for quality.
394 words, about 2 min03DevOps Continuous Testing Strategies
This domain tests your ability to choose a testing strategy across the pipeline: which tests to run, where, how often, and against which risks, including testing in production. Risk-based testing : allocate effort by likelihood and impact of failure.
394 words, about 2 min04DevOps Continuous Testing Frameworks and Tools
This domain tests your ability to select and combine tools by testing need, and to recognise healthy framework design rather than tool-name recall alone. Tool categories by purpose : unit and component (JUnit, TestNG, NUnit, pytest); BDD and specification (Cucumber, SpecFlow); API (REST Assured, Karate, Postman/Newman); UI (Selenium, Cypress, Playwright); performance (JMeter, Gatling, k6); security (SAST and DAST tools such as SonarQube and OWASP ZAP); service virtualization (WireMock, Mountebank); contract testing (Pact); test management (TestRail, Zephyr, Xray); CI/CD orchestration (Jenkins, GitLab CI, GitHub Actions, Azure DevOps); containers (Docker, Testcontainers).
379 words, about 2 min05DevOps Test Planning Best Practices
This domain tests how to plan testing in a continuous delivery context: lightweight, collaborative, risk-based and continually updated rather than a large document written once. Plan continuously : test planning starts with the release or iteration and is revisited as scope, risk and code change.
376 words, about 2 min06DevOps Test Automation Best Practices
This domain tests how to build automation that stays fast, trustworthy and maintainable inside a pipeline, and how to avoid the failure modes that make teams abandon automated suites. Automate by risk and level : use the test pyramid; prefer fast, isolated unit and API tests; reserve UI automation for critical journeys.
410 words, about 2 min07DevOps Test Management and Analysis Best Practices
This domain tests how to manage testing information in a continuous delivery world: traceability, meaningful metrics, fast defect analysis and dashboards that support decisions rather than vanity reporting. Lightweight management : test management is embedded in the pipeline and backlog, not a separate bureaucratic system.
394 words, about 2 min08Defining a DevOps Test Strategy
This domain tests whether you can define an organisation-level test strategy that aligns testing with DevOps goals, rather than writing a test plan or copying a template. Strategy versus plan : a test strategy is long-lived and organisation-wide; it states principles, approach, scope, governance and how testing supports business and DevOps objectives.
412 words, about 2 min