Ruby
RSpec is the most widely used testing framework for Ruby. Its expressive syntax reads almost like natural language, which makes test suites easier to understand and maintain. This tutorial covers the core building blocks: describe, context, it, expect, and matchers. Installing RSpec Add RSpec to your Gemfile: group :test do
Ruby
Ruby developers have two excellent unit testing frameworks to choose from: RSpec and Minitest. Both ship with strong matchers, mock support, and Rails integration. The choice is mostly about style preference, but there are real differences worth understanding. Overview RSpec is a Behavior-Driven Development (BDD) framework. It emphasizes human-
Ruby
shoulda-matchers provides a collection of one-liner matchers for testing common Rails patterns: validations, associations, and controller behavior. Instead of writing multi-line setup to test validates :name, presence: true, you write one line: it { is_expected.to validate_presence_of(:name) }. This guide covers setup, all major matchers,
Ruby
RSpec integrates deeply with Rails through the rspec-rails gem. It provides spec types tuned for each layer of a Rails application: model specs, request specs, system specs, and more. This guide shows you how to set up rspec-rails and write effective tests for all three layers. Setup Add
Ruby
factory_bot (formerly FactoryGirl) is the standard library for managing test data in Ruby on Rails applications. Instead of manually building objects in each test, you define factories once and reuse them everywhere. The result: cleaner tests, consistent data, and less setup noise. Why factory_bot? Consider two approaches to
Ruby
Capybara is the standard Ruby library for simulating browser interactions in tests. It's the engine behind Rails system specs and RSpec feature specs. Instead of asserting on raw HTML, you interact with your app the way a user would: clicking buttons, filling forms, navigating pages. How Capybara Works