Testing
Canary Deployments Testing Strategy with Argo Rollouts
Canary deployments reduce release risk by routing a small percentage of production traffic to the new version before rolling it out fully.
Testing
Canary deployments reduce release risk by routing a small percentage of production traffic to the new version before rolling it out fully.
Testing
Shadow testing (also called traffic mirroring or dark launching) sends a copy of real production requests to a new version of your service alongside the production version. The new version handles the request but its response is discarded — users only see the response from the stable version. This lets you
Testing
Progressive delivery is the practice of gradually rolling out changes to users while automatically verifying that the release meets your quality standards at each step. Flagger is a Kubernetes operator that automates this process — it manages canary deployments, traffic mirroring, and A/B testing with automated analysis and rollback. Unlike
Testing
A/B testing and canary deployments both route subsets of users to different versions of your software. Both involve traffic splitting.
Testing
The traditional software testing model was sequential: developers wrote code, then testers found bugs, then developers fixed them.
IaC Testing
Kustomize makes Kubernetes manifest management tractable. It does not make it safe.
IaC Testing
Compliance frameworks like CIS Benchmarks contain hundreds of controls.
IaC Testing
The basics of Atlantis—comment atlantis plan on a PR, review the plan, apply—are well documented.
Testing
Getting BDD tests to pass on a developer's laptop is one problem. Getting them to run reliably in a CI/CD pipeline — in parallel, with good reporting, fast feedback, and minimal flakiness — is a different problem entirely. Many teams set up Cucumber locally but struggle to make it
IaC Testing
Spacelift sits between Atlantis (self-hosted, minimal) and Terraform Cloud (SaaS, opinionated).
IaC Testing
Basic Molecule usage—spin up a Docker container, run a playbook, verify with Ansible—covers maybe 30% of real-world scenarios.
Test Automation
Dark launch is the practice of running a new version of a service in production — receiving real requests, doing real work — while still serving responses from the current version. Users see nothing different. Your new service processes every request, you measure its behavior, and only when you are confident does