Bird
Raised Fist0
Rubyprogramming~20 mins

RSpec describe and it blocks in Ruby - Practice Problems & Coding Challenges

Choose your learning style10 modes available
Challenge - 5 Problems
🎖️
RSpec Mastery Badge
Get all challenges correct to earn this badge!
Test your skills under time pressure!
❓ Predict Output
intermediate
2:00remaining
Output of nested describe and it blocks
What will be the output when running this RSpec test code?
Ruby
RSpec.describe 'Calculator' do
  describe '#add' do
    it 'adds two numbers' do
      expect(2 + 3).to eq(5)
    end
  end

  describe '#subtract' do
    it 'subtracts two numbers' do
      expect(5 - 3).to eq(2)
    end
  end
end
A2 examples, 0 failures
B1 example, 0 failures
C2 examples, 2 failures
D0 examples, 0 failures
Attempts:
2 left
💡 Hint
Count the number of it blocks inside all describe blocks.
🧠 Conceptual
intermediate
1:30remaining
Purpose of describe and it blocks in RSpec
What is the main purpose of the describe and it blocks in RSpec?
A<code>describe</code> defines variables; <code>it</code> groups tests
B<code>describe</code> runs tests; <code>it</code> sets up variables
C<code>describe</code> groups tests; <code>it</code> defines individual test examples
D<code>describe</code> is for assertions; <code>it</code> is for setup
Attempts:
2 left
💡 Hint
Think about how you organize tests and what runs as a test.
🔧 Debug
advanced
2:00remaining
Identify the error in this RSpec test code
What error will this RSpec code produce when run?
Ruby
RSpec.describe 'Math' do
  it 'multiplies numbers' do
    expect(2 * 3).to eq 6
  end

  it 'divides numbers' do
    expect(10 / 2).to eq(5)
  end
end
ASyntaxError due to missing closing parenthesis
BNo error, tests pass
CNameError for undefined method
DRuntimeError due to division by zero
Attempts:
2 left
💡 Hint
Check the parentheses in the second it block.
❓ Predict Output
advanced
2:00remaining
Output of nested it blocks inside describe
What will be the output of this RSpec code?
Ruby
RSpec.describe 'String' do
  it 'checks length' do
    expect('hello'.length).to eq(5)

    it 'nested it block' do
      expect('world'.upcase).to eq('WORLD')
    end
  end
end
ASyntaxError: nested 'it' blocks are not allowed
B2 examples, 0 failures
C0 examples, 0 failures
D1 example, 1 failure
Attempts:
2 left
💡 Hint
Consider if RSpec allows it blocks inside other it blocks.
🧠 Conceptual
expert
2:30remaining
How does RSpec handle multiple describe blocks with the same name?
If you have multiple describe blocks with the same description string in RSpec, how does RSpec treat them?
ARSpec merges them into one group and runs examples once
BRSpec treats them as separate groups and runs all their examples
CRSpec runs only the first describe block and ignores others
DRSpec raises an error about duplicate describe blocks
Attempts:
2 left
💡 Hint
Think about how RSpec organizes tests by describe blocks.

Practice

(1/5)
1. What is the main purpose of the describe block in RSpec?
easy
A. To set up test data before tests run
B. To define a single test case
C. To run the tests automatically
D. To group related test cases together

Solution

  1. Step 1: Understand the role of describe

    The describe block is used to group related tests, making the test suite organized.
  2. Step 2: Differentiate from it block

    The it block defines individual test cases, not grouping.
  3. Final Answer:

    To group related test cases together -> Option D
  4. Quick Check:

    describe groups tests = D [OK]
Hint: Remember: describe groups, it tests one thing [OK]
Common Mistakes:
  • Confusing describe with it
  • Thinking describe runs tests
  • Assuming describe sets up data
2. Which of the following is the correct syntax to define a test case inside a describe block in RSpec?
easy
A. describe 'Calculator' do it 'adds numbers' { expect(1 + 1).to eq(2) end
B. describe 'Calculator' do it 'adds numbers' do expect(1 + 1).to eq(2) end end
C. describe 'Calculator' do it 'adds numbers' do expect(1 + 1).to eq(2) end
D. describe 'Calculator' do test 'adds numbers' do expect(1 + 1).to eq(2) end end

Solution

  1. Step 1: Check Ruby block syntax

    RSpec uses do ... end blocks for describe and it. Curly braces are less common for multi-line blocks.
  2. Step 2: Verify correct keywords

    it defines test cases, not test. describe 'Calculator' do test 'adds numbers' do expect(1 + 1).to eq(2) end end uses wrong keyword.
  3. Final Answer:

    describe 'Calculator' do it 'adds numbers' do expect(1 + 1).to eq(2) end end -> Option B
  4. Quick Check:

    Correct Ruby block syntax = A [OK]
Hint: Use do...end for multi-line it blocks [OK]
Common Mistakes:
  • Using curly braces for multi-line blocks
  • Using wrong keyword like test instead of it
  • Missing do or end keywords
3. What will be the output when running this RSpec test?
describe 'Math' do
  it 'checks addition' do
    expect(2 + 2).to eq(4)
  end

  it 'checks subtraction' do
    expect(5 - 3).to eq(1)
  end
end
medium
A. 1 test passed, 1 test failed
B. 2 tests passed
C. 2 tests failed
D. Syntax error

Solution

  1. Step 1: Evaluate first test case

    expect(2 + 2).to eq(4) is true, so first test passes.
  2. Step 2: Evaluate second test case

    expect(5 - 3).to eq(1) is false because 5 - 3 equals 2, not 1, so second test fails.
  3. Final Answer:

    1 test passed, 1 test failed -> Option A
  4. Quick Check:

    2+2=4 (pass), 5-3=2≠1 (fail) = B [OK]
Hint: Check math inside expect carefully [OK]
Common Mistakes:
  • Assuming both tests pass without checking math
  • Confusing expected and actual values
  • Ignoring test failure details
4. Identify the error in this RSpec test code:
describe 'String' do
  it 'checks length' do
    expect('hello'.length).to eq 5
  end
end
medium
A. Syntax error due to missing do keyword
B. Incorrect use of describe block
C. No error, code is correct
D. Missing parentheses in expect call

Solution

  1. Step 1: Check syntax of expect

    The syntax expect('hello'.length).to eq 5 is valid in Ruby; parentheses are optional here.
  2. Step 2: Verify describe and it blocks

    Both describe and it blocks have correct do ... end syntax.
  3. Final Answer:

    No error, code is correct -> Option C
  4. Quick Check:

    Code syntax valid = A [OK]
Hint: Parentheses optional in expect calls [OK]
Common Mistakes:
  • Thinking parentheses are mandatory
  • Confusing describe and it syntax
  • Assuming missing do keyword
5. You want to test a method greet(name) that returns "Hello, <name>!". How do you organize your RSpec test using describe and it blocks for clarity and good practice?
hard
A. describe 'greet method' do it 'returns greeting with given name' do expect(greet('Alice')).to eq('Hello, Alice!') end end
B. it 'returns greeting with given name' do expect(greet('Alice')).to eq('Hello, Alice!') end
C. describe 'greet method' do expect(greet('Alice')).to eq('Hello, Alice!') end
D. describe 'greet method' do it 'returns greeting with given name' { expect(greet('Alice')).to eq('Hello, Alice!') end

Solution

  1. Step 1: Use describe to group tests

    The describe block groups related tests for the greet method.
  2. Step 2: Use it for individual test cases

    The it block defines specific test cases. Expect statements directly in describe or standalone it lack proper structure.
  3. Step 3: Prefer do...end for readability

    Use do ... end for multi-line blocks over { ... }.
  4. Final Answer:

    describe 'greet method' do it 'returns greeting with given name' do expect(greet('Alice')).to eq('Hello, Alice!') end end -> Option A
  5. Quick Check:

    describe groups, it tests, do...end blocks = C [OK]
Hint: Use describe for grouping, it for each test [OK]
Common Mistakes:
  • Skipping describe block
  • Writing expect outside it block
  • Using curly braces for multi-line it block
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard