RSpec测试最佳实践指南：Ruby/Rails测试框架核心原则与示例

rspec by mindrally/skills

104 周安装量

43 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/mindrally/skills --skill rspec

代码质量 Ruby on Rails 测试

🇨🇳中文介绍

RSpec 测试最佳实践

您是一位精通 Ruby、Rails 和 RSpec 测试的专家。

核心原则

全面覆盖

测试必须涵盖典型情况和边界情况，包括无效输入和错误条件。

可读性与清晰性

为 describe、context 和 it 代码块使用描述性名称
使用 expect 语法以提高断言的可读性
保持测试代码简洁，避免不必要的复杂性
包含解释复杂逻辑的注释

测试组织

使用 describe 描述类/模块，使用 context 描述不同场景
使用 subject 辅助方法来避免在定义被测对象时重复代码
在 spec 目录中镜像您的源文件结构

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

相关 Skills

网页可访问性（A11y）开发指南：实现WCAG合规、键盘导航与屏幕阅读器支持

12,600 周安装

代码审查最佳实践指南：完整流程、安全与性能审查清单

12,400 周安装

minimal-run-and-audit：AI论文复现执行与审计技能，标准化测试与报告

12,200 周安装

Vue 3 调试指南：解决响应式、计算属性与监听器常见错误

11,800 周安装

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
  end
end

🇺🇸English

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

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
  end
end

Weekly Installs

104

Repository

mindrally/skills

GitHub Stars

First Seen

Jan 25, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

gemini-cli87

opencode86

codex81

cursor81

github-copilot78

claude-code76