Quality Gates in CI Pipelines
Not every failure should block a merge. Learn which quality gates must block pipelines, which should inform, and how to design gates that prevent bad code from reaching production without slowing.
📚 CI/CD Quality
Quality gates, GitHub Actions, Dockerised E2E, reports, continuous testing, and what QA owns after release.
8 / 8 parts
← All seriesGitHub Actions for Test Automation
Learn how to build fast, reliable CI pipelines with GitHub Actions. Master workflow syntax, dependency caching, matrix strategies, secrets management, and Playwright integration for scalable test.
E2E in Docker and Ephemeral Environments
Reproducible test environments are the foundation of reliable CI/CD. Learn how to use Docker Compose for local and CI E2E testing, and how to run smoke tests against ephemeral preview deployments.
Reports, Artifacts, and Failure Triage in CI
Failed CI runs are only useful if you can diagnose them quickly. Learn how to generate HTML reports, upload trace artifacts, establish ownership loops, and notify teams without creating alert fatigue.
PR Checks That Matter — Shift-Left Without Noise
Fast feedback on pull requests accelerates delivery. Learn how to design PR checks that catch real issues early, use path filters to skip irrelevant checks, and balance required vs. optional checks.
Continuous Testing in Continuous Delivery
Continuous delivery demands confidence at every stage. Learn where QA fits in CD pipelines, how to build release confidence without slowing down, and how progressive delivery and feature flags enable.
Risk-Based Regression — What to Run When You Cannot Run Everything
Choose which regression tests run on a pull request, which wait for nightly, and which should leave the suite.
What QA Owns After Deploy
Decide what QA watches in the first hour after release: synthetic journeys, the signal to stop, and the test you add afterwards.