Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
The Anatomy of a mocked call - RuLu 2014
Search
Penelope Phippen
June 18, 2014
Technology
0
180
The Anatomy of a mocked call - RuLu 2014
Penelope Phippen
June 18, 2014
Tweet
Share
More Decks by Penelope Phippen
See All by Penelope Phippen
Introducing Rubyfmt
penelope_zone
0
590
How RSpec Works
penelope_zone
0
6.7k
Quick and easy browser testing using RSpec and Rails 5.1
penelope_zone
1
98
Teaching RSpec to play nice with Rails
penelope_zone
2
160
Little machines that eat strings
penelope_zone
1
110
What is processor (brighton ruby edition)
penelope_zone
0
130
What is processor?
penelope_zone
1
370
extremely defensive coding - rubyconf edition
penelope_zone
0
280
Agile, etc.
penelope_zone
2
240
Other Decks in Technology
See All in Technology
AI駆動開発ライフサイクル(AI-DLC)の始め方
ryansbcho79
0
290
Bedrock AgentCore Evaluationsで学ぶLLM as a judge入門
shichijoyuhi
2
310
マーケットプレイス版Oracle WebCenter Content For OCI
oracle4engineer
PRO
5
1.5k
SES向け、生成AI時代におけるエンジニアリングとセキュリティ
longbowxxx
0
290
名刺メーカーDevグループ 紹介資料
sansan33
PRO
0
1k
産業的変化も組織的変化も乗り越えられるチームへの成長 〜チームの変化から見出す明るい未来〜
kakehashi
PRO
1
220
「リリースファースト」の実感を届けるには 〜停滞するチームに変化を起こすアプローチ〜 #RSGT2026
kintotechdev
0
450
Keynoteから見るAWSの頭の中
nrinetcom
PRO
1
160
田舎で20年スクラム(後編):一個人が企業で長期戦アジャイルに挑む意味
chinmo
1
690
「駆動」って言葉、なんかカッコイイ_Mitz
comucal
PRO
0
130
プロンプトエンジニアリングを超えて:自由と統制のあいだでつくる Platform × Context Engineering
yuriemori
0
110
善意の活動は、なぜ続かなくなるのか ーふりかえりが"構造を変える判断"になった半年間ー
matsukurou
0
170
Featured
See All Featured
The Illustrated Guide to Node.js - THAT Conference 2024
reverentgeek
0
220
Git: the NoSQL Database
bkeepers
PRO
432
66k
The Invisible Side of Design
smashingmag
302
51k
Have SEOs Ruined the Internet? - User Awareness of SEO in 2025
akashhashmi
0
220
Put a Button on it: Removing Barriers to Going Fast.
kastner
60
4.1k
Building a A Zero-Code AI SEO Workflow
portentint
PRO
0
220
世界の人気アプリ100個を分析して見えたペイウォール設計の心得
akihiro_kokubo
PRO
65
35k
We Are The Robots
honzajavorek
0
130
Ten Tips & Tricks for a 🌱 transition
stuffmc
0
42
Into the Great Unknown - MozCon
thekraken
40
2.2k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
234
17k
Statistics for Hackers
jakevdp
799
230k
Transcript
The Anatomy of a mocked call
!/samphippen
Hello everyone :)
Why is testing?
x`
None
Tests force behaviour
Without tests Anything could happen
Unit Testing makes me happy :)
Stubbing and mocking
Stubbing
Fake response to a method
allow(x).to( receive(:foo).and_return(3) )
x.foo will return 3
Mocking
Testing methods get called
expect(x).to receive(:foo)
Test fails if x does not receive foo
expect(x).to receive(:foo).with(3)
expect(x).to( receive(:foo) .with(3) .exactly(4).times )
How does it work?
Stubs
it “does something” do allow(foo).to receive(:bar) expect(foo.bar).to eq(nil) end
it “does something” do allow(foo).to receive(:bar) expect(foo.bar).to eq(nil) end
allow is syntax sugar for AllowanceTarget.new
Allowance Target
Allowance Target TargetBase
AllowanceTarget calls #delegate_to with :setup_allowance on TargetBase
Allowance Target TargetBase
TargetBase defines #to on AllowanceTarget
Defined #to calls :setup_allowance on matchers passed to #to
Allowance Target TargetBase
it “does something” do allow(foo).to receive(:bar) expect(foo.bar).to eq(nil) end
Things passed to #to are called “matchers”
Receive is a commonly used mocking/stubbing matcher
AllowanceTarget#to calls setup_allowance on the passed matcher
Allowance Target TargetBase Allowance Target TargetBase Receive
Receive#setup_allowance creates a Mock Proxy for object
Receive#setup_allowance calls #add_stub on the Mock Proxy
Allowance Target TargetBase Receive Proxy
Proxy objects manage all mocks/stubs for an object
it “does something” do allow(foo).to receive(:bar) allow(foo).to receive(:baz) expect(foo.bar).to eq(nil)
end
Proxy#add_stub creates a MethodDouble for the stubbed method
Allowance Target TargetBase Proxy Receive Method Double
MethodDouble saves the original implementation
MethodDouble creates stub implementation
it “does something” do allow(foo).to receive(:bar) expect(foo.bar).to eq(nil) end
it “does something” do allow(foo).to receive(:bar) expect(foo.bar).to eq(nil) end
foo.bar is the stubbed implementation
Call foo.bar
Method Double Call foo.bar
Method Double Call foo.bar Proxy
Method Double Call foo.bar Proxy Invokes stub
Method Double Call foo.bar Proxy Invokes stub Return value
it “does something” do allow(foo).to receive(:bar) expect(foo.bar).to eq(nil) end
RSpec manages lifecycle of mocks
RSpec::Mocks.setup
RSpec::Mocks.setup Your test
RSpec::Mocks.setup Your test RSpec::Mocks.verify
RSpec::Mocks.teardown RSpec::Mocks.setup Your test RSpec::Mocks.verify
All of this happens in a mock space
Allowance Target TargetBase Proxy Receive Method Double
RSpec::Mocks.teardown calls #reset_all on the current Space
Space#reset_all calls #reset on each proxy
Proxy#reset calls #reset on each MethodDouble
MethodDouble#reset returns original methods to objects
RSpec::Mocks.teardown RSpec::Mocks.setup Your test RSpec::Mocks.verify
Phew
Mocks
it “does something” do expect(foo).to receive(:bar).with(3) expect(foo.bar(3)).to eq(nil) end
expect is syntax sugar for ExpectationTarget.new
Expectation Target TargetBase Proxy Receive Method Double
Calls #setup_expectation
it “does something” do expect(foo).to receive(:bar).with(3) expect(foo.bar(3)).to eq(nil) end
Receive stores details of stubbed/ mocked implementation
Expectation Target TargetBase Proxy Receive Method Double
Method Double Call foo.bar Proxy Invokes stub Return value
Proxy callback checks arguments
Proxy raises if args don’t match
it “does something” do expect(foo).to receive(:bar).with(3) expect(foo.bar(3)).to eq(nil) end
RSpec::Mocks.teardown RSpec::Mocks.setup Your test RSpec::Mocks.verify
RSpec::Mocks.verify calls Space#verify_all
Space#verify_all calls #verify on each Proxy
Proxy raises if mock not called
And that’s how it all works :)
RSpec::Mocks.teardown RSpec::Mocks.setup Your test RSpec::Mocks.verify
expect(x).to receive(:foo) allow(x).to receive(:foo)
Target TargetBase
expect(x).to receive(:foo) allow(x).to receive(:foo)
Target TargetBase
expect(x).to receive(:foo) allow(x).to receive(:foo)
Receive
Proxy Receive
Proxy Receive Method Double
Target TargetBase Proxy Receive Method Double
Method Double Call foo.bar Proxy Invokes stub Return value
Target TargetBase Proxy Receive Method Double
RSpec 3.0.0 is out Please use it
tinyurl.com/ samrl2014
Let’s have some questions !/samphippen
[email protected]