Ruby
FactoryBot is the standard library for generating test data in Rails applications. It replaces fixtures with a programmable approach: define templates for your models, then build or create instances with exactly the attributes each test needs. This guide covers everything from basic setup to advanced patterns. Installation and Setup Add
Ruby
SimpleCov is the standard code coverage library for Ruby. It hooks into Ruby's Coverage module, tracks which lines and branches your tests exercise, and generates HTML reports so you can see exactly what's untested. Installation # Gemfile group :test do gem 'simplecov', require: false end
Ruby
RSpec is the dominant testing framework in the Rails ecosystem. Its BDD-style syntax encourages you to write tests that read like specifications, which makes test failures easier to diagnose and test suites easier to navigate. This tutorial walks through everything you need to get RSpec working well in a
Ruby
Rails ships with a testing framework built in. Most teams either use it as-is (Minitest) or replace it with RSpec. Both are solid choices, but they have different philosophies and different ecosystems. This guide covers what you need to know to test a Rails application effectively — regardless of which
Ruby
System tests are the closest thing to a real user clicking through your application. They drive a browser, fill in forms, click buttons, and assert what the user sees. Rails has built-in support for system tests via Capybara, and this guide covers how to use them effectively. What System
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.
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
Ruby
Tests that make real HTTP requests are slow, flaky, and dependent on external services staying available.
Ruby
Rails system tests let you test your application through a real browser, exercising JavaScript, authentication flows, and multi-step user interactions that unit tests cannot reach. They use Capybara as the test DSL and Selenium WebDriver to control Chrome or Firefox. This guide covers writing effective system tests, handling JavaScript
Ruby
Rails APIs need a different testing approach than HTML applications. There's no browser to drive, no UI interactions — just HTTP requests and JSON responses.