Rspec

by mindrally97184105b5daNo license269 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 5 weeks ago

RSpec testing best practices for Ruby and Rails applications, covering test organization, data management, and isolation patterns.

Instructions onlySoftware Development

AI-generated overview

RSpec testing best practices for Ruby and Rails, covering test organization, data management, and isolation.

What it does: This skill provides guidance on writing RSpec tests for Ruby and Rails applications. It covers principles such as comprehensive coverage, readable assertions, test organization with describe and context blocks, test data management with let and FactoryBot, test isolation, and reducing duplication through shared examples. It includes an example spec structure for a model.
When to use it: Use it when writing or reviewing RSpec specs for Ruby or Rails code. It is suited to structuring test suites, choosing data setup approaches, and keeping tests isolated and readable.
Requirements: No scripts are shipped; it is instructions only. Following the guidance assumes an RSpec setup, typically with FactoryBot for test data.

RSpec Testing Best Practices

You are an expert in Ruby, Rails, and RSpec testing.

Key Principles

Comprehensive Coverage

Tests must cover both typical cases and edge cases, including invalid inputs and error conditions.

Readability and Clarity

Employ descriptive names for describe, context, and it blocks
Use the expect syntax for improved assertion readability
Keep test code concise without unnecessary complexity
Include comments explaining complex logic

Test Organization

Use describe for classes/modules and context for different scenarios
Use the subject helper to prevent repetition when defining objects under test
Mirror your source file structure within the spec directory

Test Data Management

Leverage let and let! for minimal, necessary setup
Prefer FactoryBot factories over fixtures for generating test data
Create only the data necessary for each test

Test Isolation

Each test must be independent without shared state between tests
Mock external services (APIs, databases) and stub methods appropriately
Avoid over-mocking: test real behavior when feasible

Reduce Duplication

Share common behaviors across contexts using shared_examples
Extract repetitive patterns into helpers or custom matchers
Use shared_context for common setup across multiple specs

Example Structure

ruby

RSpec.describe User, type: :model do  subject { build(:user) }
  describe 'validations' do    it { is_expected.to validate_presence_of(:email) }    it { is_expected.to validate_uniqueness_of(:email) }  end
  describe '#full_name' do    context 'when both first and last name are present' do      let(:user) { build(:user, first_name: 'John', last_name: 'Doe') }
      it 'returns the combined name' do        expect(user.full_name).to eq('John Doe')      end    end
    context 'when last name is missing' do      let(:user) { build(:user, first_name: 'John', last_name: nil) }
      it 'returns only the first name' do        expect(user.full_name).to eq('John')      end    end  endend

RSpec.describe User, type: :model do  subject { build(:user) }
  describe 'validations' do    it { is_expected.to validate_presence_of(:email) }    it { is_expected.to validate_uniqueness_of(:email) }  end
  describe '#full_name' do    context 'when both first and last name are present' do      let(:user) { build(:user, first_name: 'John', last_name: 'Doe') }
      it 'returns the combined name' do        expect(user.full_name).to eq('John Doe')      end    end
    context 'when last name is missing' do      let(:user) { build(:user, first_name: 'John', last_name: nil) }
      it 'returns only the first name' do        expect(user.full_name).to eq('John')      end    end  endend

Source and attribution

Source:mindrally/skillsinrspecat commit9718410

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Rspec

RSpec Testing Best Practices

Key Principles

Comprehensive Coverage

Readability and Clarity

Test Organization

Test Data Management

Test Isolation

Reduce Duplication

Example Structure

Source and attribution

More from mindrally/skills

Zustand State Management

Zod Schema Validation

Woocommerce

Wordpress

Websocket Development

Web Development

More in Software Development

Playground

M5 Onboard

Cardputer Buddy

Web Design Guidelines

Vercel React Native Skills

Vercel React Best Practices