Minitest vs RSpec in Ruby on Rails - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Difference in Syntax Style Between Minitest and RSpec

Which of the following code snippets correctly shows how to write a simple test that checks if 2 + 2 equals 4 in Minitest and RSpec respectively?

A

Minitest: expect(2 + 2).to eq(4)
RSpec: assert_equal 4, 2 + 2

B

Minitest: test 'sum' do
  expect(2 + 2).to eq(4)
end
RSpec: it 'adds numbers' do
  assert_equal 4, 2 + 2
end

C

Minitest: assert_equal 4, 2 + 2
RSpec: expect(2 + 2).to eq(4)

D

Minitest: it 'adds numbers' do
  expect(2 + 2).to eq(4)
end
RSpec: test 'sum' do
  assert_equal 4, 2 + 2
end

💡 Hint

Remember Minitest uses assert methods, RSpec uses expect syntax.

Minitest uses assert_equal expected, actual style assertions. RSpec uses expect(actual).to eq(expected) syntax.

❓ component_behavior

intermediate

Test Output Differences Between Minitest and RSpec

When running a failing test that expects 5 but gets 3, which output snippet correctly shows how Minitest and RSpec report the failure?

A

Minitest: Expected: 5
  Actual: 3
RSpec: expected: 5 got: 3

B

Minitest: Failure:
Expected: 5
  Actual: 3
RSpec: 
  1) Failure:
  expected: 5
  got: 3

C

Minitest: Error: expected 5 but got 3
RSpec: Failure/Error: expect(3).to eq(5)

D

Minitest: expected 5 got 3
RSpec: Failure: expected 5 but got 3

💡 Hint

Look for the detailed failure message format typical for each framework.

Minitest failure messages start with 'Failure:' followed by expected and actual values. RSpec failure messages include 'Failure/Error:' and show the expectation and actual value with indentation.

❓ lifecycle

advanced

Setup and Teardown Differences in Minitest and RSpec

Which code snippet correctly shows how to run setup code before each test in Minitest and RSpec?

A

Minitest: setup do
  @user = User.new
end
RSpec: before_all do
  @user = User.new
end

B

Minitest: before(:each) do
  @user = User.new
end
RSpec: def setup
  @user = User.new
end

C

Minitest: def before_each
  @user = User.new
end
RSpec: setup do
  @user = User.new
end

D

Minitest: def setup
  @user = User.new
end
RSpec: before(:each) do
  @user = User.new
end

💡 Hint

Minitest uses method overrides, RSpec uses hooks.

Minitest runs setup code by defining a setup method. RSpec uses before(:each) hooks to run code before each example.

📝 Syntax

advanced

Correct Syntax for Skipping Tests in Minitest and RSpec

Which option correctly shows how to skip a test in Minitest and RSpec?

A

Minitest: def test_example
  skip "Not implemented"
end
RSpec: it 'does something', skip: true do
  expect(true).to eq(true)
end

B

Minitest: def test_example
  pending "Not implemented"
end
RSpec: it 'does something' do
  skip "Not implemented"
end

C

Minitest: def test_example
  skip_test "Not implemented"
end
RSpec: it 'does something', pending: true do
  expect(true).to eq(true)
end

D

Minitest: def test_example
  ignore "Not implemented"
end
RSpec: it 'does something', ignore: true do
  expect(true).to eq(true)
end

💡 Hint

Minitest uses skip method, RSpec uses metadata flags.

In Minitest, calling skip inside a test skips it. In RSpec, adding skip: true metadata skips the example.

🔧 Debug

expert

Identifying the Cause of a Test Failure in Minitest vs RSpec

Given the following test code, which option correctly identifies the cause of failure when running in Minitest and RSpec respectively? Minitest test: ```ruby def test_greeting assert_equal 'Hello, Bob!', greet('Alice') end ``` RSpec test: ```ruby it 'greets Bob' do expect(greet('Alice')).to eq('Hello, Bob!') end ``` Assuming the greet method returns "Hello, Alice!", what is the cause of failure?

A Both fail because the expected greeting is for 'Bob' but the method returns greeting for 'Alice'.

B Minitest passes but RSpec fails because of mismatched strings.

C Minitest fails due to syntax error; RSpec fails because of wrong expectation.

D Both pass because the greet method returns a string.

💡 Hint

Check the expected vs actual values carefully.

Both tests expect the greeting for 'Bob' but the method returns greeting for 'Alice'. This mismatch causes failure in both frameworks.

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