Minitest vs RSpec in Ruby on Rails - Hands-On Comparison

Minitest vs RSpec: Testing a Simple Rails Model

📖 Scenario: You are building a small Rails app to manage books in a library. You want to write tests to check that your Book model works correctly. You will practice writing tests using two popular Ruby testing frameworks: Minitest and RSpec.

🎯 Goal: Write tests for the Book model using both Minitest and RSpec. You will create the model data, set up test configurations, write core test logic, and complete the test files. This will help you understand the differences and similarities between Minitest and RSpec.

📋 What You'll Learn

Create a Book model instance with specific attributes

Set up a test configuration variable for the minimum page count

Write a test that checks if the book has enough pages

Complete the test file with the correct test framework syntax

💡 Why This Matters

🌍 Real World

Testing Rails models ensures your app works correctly and helps catch bugs early. Minitest and RSpec are two popular ways to write these tests.

💼 Career

Rails developers often write tests using Minitest or RSpec. Knowing both helps you work on different projects and maintain high code quality.

1

Create a Book model instance

In your test file, create a Book instance called book with the attributes title: 'Ruby Basics' and pages: 150.

Ruby on Rails

# Create a Book instance named book with title 'Ruby Basics' and pages 150
# Your code here

Hint

Use Book.new with a hash of attributes inside parentheses.

2

Set up minimum pages configuration

Create a variable called min_pages and set it to 100 to represent the minimum number of pages required for a book.

Ruby on Rails

book = Book.new(title: 'Ruby Basics', pages: 150)
# Create a variable min_pages and set it to 100
# Your code here

Hint

Just assign the number 100 to a variable named min_pages.

3

Write a test to check page count

Write a test that checks if book.pages is greater than or equal to min_pages. Use the syntax assert for Minitest or expect(...).to be >= ... for RSpec depending on your test file.

Ruby on Rails

book = Book.new(title: 'Ruby Basics', pages: 150)
min_pages = 100
# Write a test to check book.pages >= min_pages
# Your code here

Hint

Use assert followed by the condition book.pages >= min_pages.

4

Complete the test file with framework syntax

Add the necessary test class and method definitions for Minitest: define a class BookTest inheriting from ActiveSupport::TestCase and a method test_page_count that contains your assertion. Wrap your code accordingly.

Ruby on Rails

# Wrap your code inside a test class and method for Minitest
# Your code here

Hint

Define a test class and a test method with proper indentation.

Practice

1. Which testing framework is included by default in a new Rails application?

easy

A. Capybara

B. RSpec

C. Cucumber

D. Minitest

Solution

1. Step 1: Understand Rails default setup

   Rails comes with Minitest built-in for testing by default.

2. Step 2: Compare with other frameworks

   RSpec is popular but must be added separately; Cucumber and Capybara are for different testing purposes.

3. Final Answer:

   Minitest -> Option D

4. Quick Check:

   Default Rails test framework = Minitest [OK]

Hint: Remember Rails ships with Minitest by default [OK]

Common Mistakes:

• Thinking RSpec is default in Rails
• Confusing Capybara with test framework
• Assuming Cucumber is default

2. Which of the following is the correct syntax to define a test case in Minitest?

easy

A. describe 'User' do; it 'validates name' do; end; end

B. feature 'User' do; scenario 'validates name' do; end; end

C. test 'validates name' do; assert user.name.present?; end

D. context 'User' do; should 'validate name' do; end; end

Solution

1. Step 1: Identify Minitest syntax

   Minitest uses the test 'description' do ... end syntax for test cases.

2. Step 2: Recognize other framework syntax

   Options A, B, and C use RSpec or Cucumber style keywords like describe, context, and feature.

3. Final Answer:

   test 'validates name' do; assert user.name.present?; end -> Option C

4. Quick Check:

   Minitest test case syntax = test 'desc' do ... end [OK]

Hint: Minitest uses 'test' keyword, RSpec uses 'describe' or 'it' [OK]

Common Mistakes:

• Using RSpec keywords in Minitest
• Confusing 'context' with Minitest syntax
• Mixing feature/scenario from Cucumber

3. Given this RSpec test snippet, what will be the output if the user's name is nil?

RSpec.describe User do
  it 'validates presence of name' do
    user = User.new(name: nil)
    expect(user.valid?).to be false
  end
end

medium

A. Test fails because user is valid without a name

B. Test passes because user is invalid without a name

C. Syntax error due to missing 'describe' block

D. Runtime error because 'valid?' method is undefined

Solution

1. Step 1: Understand test logic

   The test expects user.valid? to be false when name is nil, meaning validation should fail.

2. Step 2: Check typical Rails validation behavior

   By default, if User model validates presence of name, user with nil name is invalid, so valid? returns false.

3. Final Answer:

   Test passes because user is invalid without a name -> Option B

4. Quick Check:

   RSpec test expects invalid user = test passes [OK]

Hint: If expectation matches validation, test passes [OK]

Common Mistakes:

• Assuming user is valid without name
• Confusing test failure with test pass
• Thinking syntax error occurs here

4. Identify the error in this Minitest code snippet:

class UserTest < ActiveSupport::TestCase
  test 'user has a name' do
    user = User.new(name: 'Alice')
    assert user.name.present?
  end
end

medium

A. Incorrect inheritance operator '<' should be '<'

B. Missing 'def' keyword before test method

C. Wrong assertion method used

D. Test description should be a symbol, not string

Solution

1. Step 1: Check class inheritance syntax

   The snippet uses '<' instead of '<' for inheritance, which is invalid Ruby syntax.

2. Step 2: Verify other syntax elements

   Minitest uses 'test' with string description correctly; no 'def' needed here; assertion method is correct.

3. Final Answer:

   Incorrect inheritance operator '<' should be '<' -> Option A

4. Quick Check:

   Class inheritance uses '<' in Ruby [OK]

Hint: Use '<' for inheritance, not HTML entity '<' [OK]

Common Mistakes:

• Confusing test method with regular method needing 'def'
• Thinking assertion method is wrong
• Assuming string description is invalid

5. You want to write a test suite that uses RSpec's expressive syntax but also wants to run tests quickly without adding extra gems. Which approach best balances these needs?

hard

A. Use Minitest with the 'minitest-spec' gem to write spec-style tests

B. Use RSpec only and accept slower test runs

C. Use Minitest with only 'test' methods and no spec syntax

D. Use Cucumber for all tests to get expressiveness and speed

Solution

1. Step 1: Understand trade-offs

   RSpec is expressive but slower and requires extra gems; Minitest is fast and built-in but less expressive.

2. Step 2: Identify hybrid solution

   The 'minitest-spec' gem adds RSpec-like syntax to Minitest, combining expressiveness with speed and no heavy dependencies.

3. Final Answer:

   Use Minitest with the 'minitest-spec' gem to write spec-style tests -> Option A

4. Quick Check:

   minitest-spec = expressiveness + speed [OK]

Hint: Add 'minitest-spec' gem for RSpec style with Minitest speed [OK]

Common Mistakes:

• Assuming RSpec is always faster
• Ignoring hybrid gems like minitest-spec
• Confusing Cucumber with unit test framework