Testing
Since Rails 6, parallel test execution is built into the framework — no third-party gems required. One method call in your test helper can turn a 10-minute test suite into a 2-minute run. This guide covers the setup, database isolation, and the operational details that matter for CI.
Contract Testing
Contract testing only protects you if it runs in CI/CD. A manually run Pact verification that isn't blocking deploys is just documentation. This guide shows how to wire contract testing into a real CI/CD pipeline: consumer tests publish pacts on every build, providers verify on every
Ruby on Rails
Rails request specs are the right tool for testing APIs—they exercise the full stack from routing through serialization without a real browser. This post covers JSON assertion patterns, authentication header strategies, API versioning in tests, and shared helpers that keep API specs readable and maintainable. Rails provides three layers
Ruby
Testing a Rails API is one of the highest-leverage testing activities in a Rails application. A well-tested API means consumers — mobile apps, frontend SPAs, third-party integrations — can rely on consistent behavior. Request specs are the right tool for this job. Why Request Specs for APIs Rails provides
Testing
Background jobs are notoriously undertested. They run asynchronously, fail silently, and interact with external services — all the characteristics that make testing uncomfortable. Rails ActiveJob provides testing tools that make job testing as straightforward as controller testing, without requiring a running queue worker. Queue Adapter Configuration Set the queue adapter to
Testing
Email is one of the most undertested parts of Rails applications. Bugs in welcome emails, password resets, and notifications often slip through because developers don't know how to write email tests efficiently. Rails makes it straightforward — the test mailbox captures every email sent during tests, and both RSpec
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
Your RAG system passes all tests in staging. You deploy to production. Three weeks later, users start complaining that answers are wrong. You check the code — nothing changed. You look at the LLM — same model, same prompts. But something degraded. What actually happened: the knowledge base grew, old documents became
Testing
Most testing methodology debates are arguments about which one approach is universally correct. Should you use TDD or BDD? Should you have 80% code coverage or 100%? Should you write test cases before or after development? These debates generate enormous amounts of noise and very little useful guidance because they&
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
Retrieval-Augmented Generation (RAG) pipelines are complex systems with multiple failure points: chunking can destroy context, retrieval can miss relevant documents, and the LLM can hallucinate facts not present in the retrieved chunks. Testing a RAG system requires evaluating each stage and the full pipeline together. This guide covers how
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