Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Speaker Deck
PRO
Sign in
Sign up for free
Testing Ruby
Emily Hyland
July 05, 2012
Programming
8
450
Testing Ruby
A fairly high-level intro to testing Ruby using RSpec, Factory Girl, and Autotest.
Emily Hyland
July 05, 2012
Tweet
Share
More Decks by Emily Hyland
See All by Emily Hyland
Programming for Humans
duien
0
33
Git: an introduction
duien
3
150
Other Decks in Programming
See All in Programming
You CANt teach an old dog new tricks
michaelbukachi
0
110
Groovy Roadmap
paulk
7
13k
Let's make a contract: the art of designing a Java API
mariofusco
0
160
Where and how to run UI tests (Droidcon London, 2021)
nonews
0
210
microCMS × imgixを活用して品質とレスポンスを両立したポートフォリオサイトを作成した話
takehitogoto
0
410
TechFeed Conference 2022 - Kotlin Experimental
jmatsu
0
720
Android入門
hn410
0
310
Modern Web Apps with Spring Boot, Angular & TypeScript
toedter
12
14k
iOSアプリの技術選択2022
tattn
6
2.4k
C言語でメモリ管理を考えた話
hkawai
0
190
実録mruby組み込み体験
coe401_
0
100
SPA/MPA 議論の俯瞰と 現代における設計のポイント - #tfcon 2022 フロントエンド設計
ahomu
3
1.7k
Featured
See All Featured
GitHub's CSS Performance
jonrohan
1020
410k
Java REST API Framework Comparison - PWX 2021
mraible
PRO
11
4.6k
Agile that works and the tools we love
rasmusluckow
319
19k
Stop Working from a Prison Cell
hatefulcrawdad
261
17k
Adopting Sorbet at Scale
ufuk
63
7.5k
From Idea to $5000 a Month in 5 Months
shpigford
372
44k
Code Reviewing Like a Champion
maltzj
506
37k
The Illustrated Children's Guide to Kubernetes
chrisshort
14
34k
WebSockets: Embracing the real-time Web
robhawkes
57
5k
ParisWeb 2013: Learning to Love: Crash Course in Emotional UX Design
dotmariusz
100
5.9k
Creatively Recalculating Your Daily Design Routine
revolveconf
205
10k
Building Applications with DynamoDB
mza
83
4.6k
Transcript
TESTING RUBY USING RSPEC WITH FACTORY GIRL AND AUTOTEST Thursday,
July 5, 12
Why Test? Ensure your code is correct Refactor with confidence
Encourages lots of good practices Reference for how code works Thursday, July 5, 12
RUBY — TESTING Thursday, July 5, 12
THE EMILY WAY Thursday, July 5, 12
The Basics Write your test first Test behavior, not implementation
“You ain’t gonna need it” Thursday, July 5, 12
Test First Test-Driven Development Figure out requirements before you start
writing code Interface before implementation Thursday, July 5, 12
RED GREEN REFACTOR START Thursday, July 5, 12
Test Behavior Behavior-Driven Development Unit tests are sentences starting with
“it should” Use mocks for outside collaborators Changing the implementation shouldn’t break the test Thursday, July 5, 12
YAGNI Write only as much code as you need Thursday,
July 5, 12
YAGNI Write only as much code as you need THIS
IS SURPRISINGLY HARD Thursday, July 5, 12
RSPEC Thursday, July 5, 12
Why RSpec? Tests are very easy to read Syntax encourages
good practices Specify behavior instead of verifying state Tests as documentation Tests are more expressive and more maintainable Thursday, July 5, 12
describe Array do context "when empty" do
subject { Array.new } it { should be_empty } its(:first){ should be_nil } its(:length){ should == 0 } end end Basic Syntax Thursday, July 5, 12
More Syntax let(:user){ User.new } before{ set_current_user(user) } it "should
be reasonable" do "foo".should_not eq("bar") end it "should be magic" do pending "invent magic" end Thursday, July 5, 12
Shared Examples shared_examples "collections" do | klass| it "is
empty when first created" do klass.new.should be_empty end end describe Array do include_examples "collections", Array end Thursday, July 5, 12
Matchers it.should eq(expected) it.should == expected it.should be(expected) it.should equal(expected)
it.should be > minimum it.should be_within(x).of(y) Thursday, July 5, 12
Predicate Matchers it.should be_a_kind_of(klass) it.should be_true it.should be_empty it.should be_present
it.should be_* Thursday, July 5, 12
Expect Matchers expect { ... }.to raise_error expect { ...
}.to throw_symbol expect { ... }.to yield_control expect { ... }.to change{ it } Thursday, July 5, 12
On Rails Different file layout than with Test::Unit Directories for
model, controller, helper, and view specs Lots of Rails-specific matchers, etc. Thursday, July 5, 12
Model Classic unit test Test each model individually Ideally, isolate
from the database Check validations, but indirectly Add a context for each non-trivial method Thursday, July 5, 12
Controller Did you get the right response code? Did the
expected redirect happen? Were the correct instance variables set? Were the right flash messages displayed? Thursday, July 5, 12
Legacy Write tests for what you have before you change
it Write a failing test before you fix a bug Don’t try to do it all at once Thursday, July 5, 12
FACTORY GIRL Thursday, July 5, 12
Why Factories? Fixtures quickly get hard to maintain “What did
I call the fixture for my admin user without an email?” Create the right object when you need it Use templates to keep it DRY Thursday, July 5, 12
Syntax FactoryGirl.define do factory :user do
name "John Doe" factory :admin do admin true end end end FactoryGirl.build(:user) Thursday, July 5, 12
AUTOTEST Thursday, July 5, 12
Why Autotest? Never forget to run your tests again Get
nearly instant notification when you break something Run the right tests at the right time Thursday, July 5, 12
AND FINALLY... Thursday, July 5, 12
DO Write your tests first Use contexts Use shared example
groups Test your edge cases Thursday, July 5, 12
DON’T Test the framework Test the implementation Get too clever
Thursday, July 5, 12