RSpec describe and it blocks in Ruby - Step-by-Step Execution

Concept Flow - RSpec describe and it blocks

Start RSpec Test File

↓

describe block: Group tests

↓

it block: Define example

↓

Run example code

↓

Check expectation

↓

Pass?

Yes→Next it or describe

↓

Fail test

↓

End tests

RSpec tests start with describe blocks grouping tests, inside which it blocks define individual test examples that run code and check expectations.

Execution Sample

Ruby

describe "Calculator" do
  it "adds two numbers" do
    expect(1 + 2).to eq(3)
  end
end

This code groups a test for Calculator and checks if 1 + 2 equals 3.

Execution Table

Step	Block	Action	Code Run	Expectation	Result
1	describe	Start group 'Calculator'	No code run	No expectation	Continue
2	it	Run example 'adds two numbers'	Calculate 1 + 2	expect(1 + 2).to eq(3)	Pass
3	describe	No more it blocks	End group	All tests passed	Finish

💡 All it blocks executed, expectations passed, tests complete

Variable Tracker

Variable	Start	After it block	Final
result	undefined	3 (from 1 + 2)	3

Key Moments - 3 Insights

Why do we use describe blocks in RSpec?

Describe blocks group related tests together, as shown in step 1 of the execution_table, making tests organized and readable.

What happens inside an it block?

Inside an it block (step 2), the example code runs and an expectation checks if the result matches what we want, deciding pass or fail.

Does code run when describe block starts?

No, describe blocks only group tests and do not run code themselves, as seen in step 1 where no code runs.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result of the calculation in step 2?

A 3

B 2

C 1

D undefined

💡 Hint

Check the 'Code Run' and 'Result' columns in step 2 of the execution_table.

At which step does the expectation get checked?

A Step 3

B Step 1

C Step 2

D No expectation checked

💡 Hint

Look at the 'Expectation' column in the execution_table to see when expect() is called.

If we add another it block inside describe, how would the execution_table change?

A Remove step 3

B Add another row for the new it block execution

C Change step 1 to run code

D No change at all

💡 Hint

Each it block runs separately, so each gets its own step in the execution_table.

Concept Snapshot

RSpec uses describe blocks to group tests.
Inside describe, it blocks define individual test examples.
Each it block runs code and checks expectations.
Passing means code behaves as expected.
Describe blocks do not run code themselves.
This structure keeps tests clear and organized.

Full Transcript

RSpec testing uses describe blocks to group related tests. Inside these, it blocks define individual test examples. When running, describe blocks organize tests but do not execute code. Each it block runs the example code and checks expectations using methods like expect().to eq(). If the expectation matches, the test passes; otherwise, it fails. This flow helps keep tests readable and structured.

Practice

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