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.