Redis
Redis Cluster is the native horizontal scaling solution for Redis. It partitions data across multiple nodes using consistent hashing (16384 slots), with each node responsible for a subset. When a primary fails, a replica is promoted. This guide covers how to test cluster behavior—slot assignment, redirects, failover, and reconnection—
Infrastructure Testing
Crossplane lets you build a platform API on top of Kubernetes — your developers claim a PostgreSQLInstance, your platform delivers an RDS instance. But testing that pipeline, from XRD to provider to real cloud resource, requires a different approach than testing regular Kubernetes operators. This post covers Crossplane provider testing: unit
Copado
Choosing a Salesforce DevOps platform is a long-term commitment. Once your team's workflows, pipelines, and compliance controls are built around a tool, switching costs are high. The three platforms that dominate the market — Copado, Gearset, and Flosum — each take meaningfully different approaches to the same problem. This
Copado
Salesforce development without a proper DevOps process is a recipe for deployment failures, overwritten changes, and late-night emergency releases. Copado is the most widely adopted DevOps platform built natively on Salesforce, and it changes how teams deliver metadata changes from development through production. This guide walks you through everything
Testing Culture
Most engineering organizations begin their quality journey the same way: a dedicated QA team that receives code from developers, runs it through test scripts, and files bug reports. This model made sense when releases happened monthly and testing was a manual process. It does not make sense when teams deploy
Continuous Testing
Continuous testing is the backbone of a high-velocity engineering team. Without it, every deployment becomes a gamble. With it, you gain confidence that every change is verified before it reaches production. This guide walks through the practical mechanics of integrating automated tests into your CI/CD pipeline — from structuring
Testing
Infrastructure validation should happen at every stage of the development lifecycle, not just at apply time. By combining static analysis (terraform validate, tflint), security scanning (checkov), cost estimation (infracost), and smoke tests into a single CI pipeline, you catch problems when they're cheapest to fix—during code review,
Testing
In December 2020, attackers inserted a backdoor into a SolarWinds software update. In 2022, a malicious package mimicking a popular npm library was downloaded 300,000 times before removal. In 2024, the XZ Utils backdoor was only caught by accident. The pattern is consistent: software supply chain attacks work by
Testing
Container security scanning finds known vulnerabilities (CVEs) in your image's base OS packages and language dependencies before you ship them to production. Trivy is the most widely used scanner — it's fast, accurate, covers OS packages and application dependencies, and integrates with every major CI platform. This
Code Coverage
Effective CI coverage strategies enforce coverage on new code (patch coverage), gradually increase thresholds over time (ratchet), and fail builds only for meaningful drops—not arbitrary percentages. This guide covers threshold patterns, per-language implementations, and common anti-patterns to avoid. Coverage metrics are misused more often than used well.
Testing
Pulumi infrastructure code is real programming-language code, so it deserves real tests. Pulumi's SDK provides a mock framework for unit tests (no cloud required) and an Automation API for integration tests against ephemeral stacks. This guide covers both layers in Go and Python, with CI patterns for
Testing
Pulumi's core advantage over Terraform is that infrastructure is real code — you can test it with real testing tools. But most Pulumi testing guides stop at mocking: mock the AWS provider, assert outputs, done. That misses the Automation API, which lets you manage Pulumi stacks programmatically — no CLI