Minitest vs RSpec in Ruby on Rails - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a simple test case in Minitest.

Ruby on Rails

class CalculatorTest < [1]
  def test_addition
    assert_equal 4, 2 + 2
  end
end

Drag options to blanks, or click blank then click option'

ARSpec::Core::ExampleGroup

BTest::Unit::TestCase

CActiveSupport::TestCase

DMinitest::Test

Attempts:

3 left

💡 Hint

Common Mistakes

Using RSpec class names in Minitest tests.

Confusing ActiveSupport::TestCase with Minitest::Test.

In Minitest, test classes inherit from Minitest::Test to define test cases.

2fill in blank

medium

Complete the code to write an example group in RSpec.

Ruby on Rails

RSpec.describe Calculator do
  it '[1]' do
    expect(2 + 2).to eq(4)
  end
end

Drag options to blanks, or click blank then click option'

Aadds numbers correctly

Btest addition

Cshould add numbers

Dchecks addition

Attempts:

3 left

💡 Hint

Common Mistakes

Using imperative phrases like 'test addition' instead of descriptive behavior.

Not using a string inside the it block.

RSpec uses descriptive strings inside it blocks to explain the behavior being tested.

3fill in blank

hard

Fix the error in the Minitest assertion syntax.

Ruby on Rails

def test_subtraction
  [1] 2, 5 - 3
end

Drag options to blanks, or click blank then click option'

Aassert_equal

Bshould

Cexpect

Dassert

Attempts:

3 left

💡 Hint

Common Mistakes

Using RSpec syntax like 'expect' in Minitest.

Using 'assert' without '_equal' for equality checks.

Minitest uses assert_equal(expected, actual) for equality checks.

4fill in blank

hard

Fill both blanks to complete the RSpec expectation syntax.

Ruby on Rails

expect([1]).to [2](5)

Drag options to blanks, or click blank then click option'

Acalculator.add(2, 3)

Beq

Cbe

Dequal

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'be' matcher incorrectly for equality.

Putting the expected value inside expect().

In RSpec, expect(value).to eq(expected) checks if value equals expected.

5fill in blank

hard

Fill all three blanks to write a Minitest setup method and test.

Ruby on Rails

class UserTest < Minitest::Test
  def [1]
    @user = User.new(name: 'Alice')
  end

  def [2]
    assert_equal '[3]', @user.name
  end
end

Drag options to blanks, or click blank then click option'

Asetup

Btest_name

CAlice

Dinitialize

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'initialize' instead of 'setup' for test preparation.

Not prefixing test methods with 'test_'.

Using wrong expected value in assertion.

The setup method runs before each test. Test methods start with test_. The assertion checks the user's name.

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