Quality Engineering 90 days 2-3 hours/day updated 2026-06-01

QAOps 90-Day Learning Path

Master QAOps in 90 days: shift-left testing, QA in CI/CD pipelines, automated regression suites, API testing, and quality metrics that keep defect escape rates near zero.

What QAOps means

QAOps integrates quality assurance practices directly into CI/CD pipelines so that testing is continuous, automated, and embedded in the development workflow rather than a separate phase. QAOps practitioners design automated test suites, implement shift-left testing strategies, own quality metrics dashboards, and collaborate closely with developers to eliminate defects early. The goal is to make ‘quality’ a measurable pipeline property.

Who should follow this path

QA engineers transitioning from manual to automation-first practices
Automation engineers embedding tests in CI/CD pipelines
DevOps engineers responsible for pipeline quality gates
SDETs (Software Development Engineers in Test)
Engineering leads wanting to improve defect escape rates

Prerequisites

Basic programming in Python, Java, or JavaScript
Understanding of software testing types (unit, integration, E2E)
Familiarity with at least one test automation framework
Basic Git workflow experience
Some exposure to CI/CD pipelines

The 90-day plan

Daily study recommendation: 2-3 hours/day, six days a week. Consistency beats intensity — block the time in your calendar like a meeting.

Days 1–15: Foundation

QAOps philosophy: quality as a pipeline property
Shift-left testing principles and practices
Test pyramid revisited: unit, integration, E2E proportions
CI/CD quality gates: pass/fail thresholds
Defect escape rate and quality metrics baseline

Outcome: Define a shift-left QA strategy with quality gates for each CI/CD stage.

Days 16–30: Core concepts

Unit testing frameworks: pytest, JUnit 5, Jest
Integration testing with testcontainers
API testing with Postman/Newman and REST-assured
Code coverage measurement and thresholds
Static analysis in CI: linting and code smells

Outcome: Build a multi-layer automated test suite covering unit, integration, and API layers in CI.

Days 31–45: Tools and workflows

E2E testing with Playwright and Cypress
Page Object Model and maintainable test architecture
Test data setup and teardown strategies
Cross-browser and cross-device testing in CI
Visual regression testing with Percy or Applitools

Outcome: Implement a Playwright E2E suite with Page Object Model running in GitHub Actions CI.

Days 46–60: Hands-on projects

Performance testing in CI with k6 or Gatling
Security testing in CI: DAST scan integration
Mutation testing to validate test suite quality
Accessibility testing automation (axe-core, Lighthouse CI)
Contract testing for microservices APIs

Outcome: Integrate performance, security, and accessibility testing into CI pipeline quality gates.

Days 61–75: Advanced practices

Quality metrics dashboards and reporting
Test result trend analysis and anomaly detection
Defect tracking integration with Jira
Risk-based testing and exploratory charter design
Root cause analysis for defect escape patterns

Outcome: Build a quality dashboard tracking defect escape rates, test coverage, and pipeline quality gates.

Days 76–90: Portfolio, interview & certification prep

QAOps portfolio project
Preparing for ISTQB CTFL exam
QAOps interview questions
Metrics: defect escape rate, test coverage, pipeline pass rate, MTTF
Emerging: AI-assisted test generation and intelligent test selection

Outcome: Deliver a complete QAOps pipeline project and be ready for SDET and QAOps engineer interviews.

Weekly outcomes at a glance

Phase	Outcome
Days 1–15	Define a shift-left QA strategy with quality gates for each CI/CD stage.
Days 16–30	Build a multi-layer automated test suite covering unit, integration, and API layers in CI.
Days 31–45	Implement a Playwright E2E suite with Page Object Model running in GitHub Actions CI.
Days 46–60	Integrate performance, security, and accessibility testing into CI pipeline quality gates.
Days 61–75	Build a quality dashboard tracking defect escape rates, test coverage, and pipeline quality gates.
Days 76–90	Deliver a complete QAOps pipeline project and be ready for SDET and QAOps engineer interviews.

Tools to learn

Playwright
Cypress
pytest
JUnit 5
Postman/Newman
k6
testcontainers
SonarQube
GitHub Actions
Allure Report
Jira
axe-core

Labs to practice

Mini projects

Build a full QAOps pipeline in GitHub Actions with unit, integration, API, and Playwright E2E tests with quality gates
Create a quality metrics dashboard in Grafana tracking defect escape rate, coverage trends, and pipeline health
Implement mutation testing with Pitest to validate test suite effectiveness and improve weak test areas

Interview questions to prepare

What is shift-left testing and why does it matter?
How do you decide what percentage of tests should be unit vs integration vs E2E?
Explain how you would implement quality gates in a CI/CD pipeline.
What is mutation testing and what does it tell you about your test suite?
How do you handle test data management for E2E tests in CI?
What is contract testing and how does it differ from integration testing?
How do you measure and improve test suite execution speed?
Describe how you would investigate a spike in defect escape rate.

Certification suggestions

ISTQB Certified Tester Foundation Level (CTFL) — ISTQB
ISTQB Advanced Level Test Automation Engineer — ISTQB
Playwright Certified Professional — Microsoft (via LinkedIn Learning)
AWS Certified DevOps Engineer Professional — AWS

Browse the full certification registry for exam details and official links.

Free resources

// instructor-led option

Prefer live, guided training with mentors and certification support? DevOpsSchool.com runs paid instructor-led programs that pair well with this free path.

Explore paid training on DevOpsSchool.com ↗