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

TestOps 90-Day Learning Path

Build TestOps expertise in 90 days: test infrastructure automation, distributed test execution, test analytics platforms, flaky test detection, and test environment orchestration at scale.

What TestOps means

TestOps is the discipline of treating test infrastructure, test data, and test environments as engineering products. It is distinct from QAOps: where QAOps embeds quality into CI/CD workflows, TestOps focuses on the platform layer — building and operating the infrastructure that makes testing fast, reliable, and scalable. This includes distributed test execution grids, test analytics dashboards, environment provisioning, and flaky test management.

Who should follow this path

Test infrastructure engineers and platform engineers
DevOps engineers responsible for CI/CD test environments
Senior QA engineers moving into platform-side tooling
Engineering managers scaling test capacity across many teams
SREs responsible for pre-production environment reliability

Prerequisites

Experience with automated testing frameworks (pytest, JUnit, or similar)
Familiarity with CI/CD systems (GitHub Actions, Jenkins, or CircleCI)
Basic Kubernetes and Docker knowledge
Some experience with cloud infrastructure
Understanding of test pyramid and test strategy concepts

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

TestOps vs QAOps vs DevOps: responsibilities and boundaries
Test infrastructure as code principles
Test pyramid and testing strategy for large-scale systems
Test environment taxonomy: dev, staging, perf, prod-like
TestOps maturity model

Outcome: Define a TestOps strategy with clear ownership boundaries and environment taxonomy.

Days 16–30: Core concepts

Distributed test execution with Selenium Grid and Playwright Grid
Cloud-based device and browser grids (BrowserStack, Sauce Labs)
Parallel test execution configuration
Test sharding and splitting strategies
Containerized test runners on Kubernetes

Outcome: Deploy a distributed test execution grid on Kubernetes with parallel sharding configured.

Days 31–45: Tools and workflows

Test analytics platforms: Allure TestOps, ReportPortal
Flaky test detection and quarantine automation
Test execution trend analysis and failure pattern mining
Test coverage tracking and gap analysis
Test suite health metrics and SLAs

Outcome: Set up test analytics with automated flaky test detection and quarantine workflows.

Days 46–60: Hands-on projects

Test data management: generation, masking, and provisioning
Database snapshot and restore for test environments
Contract testing with Pact for service dependencies
Test environment provisioning with Terraform
Ephemeral environments for pull request testing

Outcome: Build automated test data provisioning and ephemeral environment creation pipelines.

Days 61–75: Advanced practices

Performance and load test infrastructure (k6, Gatling, Locust)
Chaos testing integration into TestOps pipelines
Visual regression testing infrastructure (Percy, Applitools)
Accessibility testing automation
Cross-platform and cross-browser orchestration

Outcome: Integrate performance, chaos, and visual regression testing into a unified TestOps platform.

Days 76–90: Portfolio, interview & certification prep

TestOps portfolio project: self-service test platform
Preparing for ISTQB Advanced Test Manager exam
TestOps interview questions
Metrics: test execution time, flakiness rate, environment MTTR, coverage
Emerging: AI-assisted test generation and self-healing selectors

Outcome: Deliver a self-service TestOps platform project and be ready for test infrastructure engineer interviews.

Weekly outcomes at a glance

Phase	Outcome
Days 1–15	Define a TestOps strategy with clear ownership boundaries and environment taxonomy.
Days 16–30	Deploy a distributed test execution grid on Kubernetes with parallel sharding configured.
Days 31–45	Set up test analytics with automated flaky test detection and quarantine workflows.
Days 46–60	Build automated test data provisioning and ephemeral environment creation pipelines.
Days 61–75	Integrate performance, chaos, and visual regression testing into a unified TestOps platform.
Days 76–90	Deliver a self-service TestOps platform project and be ready for test infrastructure engineer interviews.

Tools to learn

Selenium Grid
Playwright
k6
Gatling
Allure TestOps
ReportPortal
BrowserStack
Pact
Terraform
Kubernetes
GitHub Actions
Percy

Labs to practice

Mini projects

Build a Kubernetes-based Playwright test execution grid with Allure TestOps analytics and flaky test quarantine
Create ephemeral PR test environments using Terraform with automated teardown and test result reporting
Implement a contract testing platform with Pact broker integration into CI pipelines across 5 microservices

Interview questions to prepare

What is the difference between TestOps and QAOps?
How do you detect and handle flaky tests at scale?
Explain test sharding and when you would use it.
How do you manage test data for integration tests in a microservices architecture?
What is contract testing and how does Pact work?
How do you provision ephemeral test environments on demand?
What metrics would you track for a test infrastructure platform?
How do you balance test execution speed with test coverage?

Certification suggestions

ISTQB Advanced Level Test Manager (CTAL-TM) — ISTQB
ISTQB Advanced Level Technical Test Analyst — ISTQB
Certified Kubernetes Application Developer (CKAD) — CNCF
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 ↗