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
Testing Ruby
Search
Emily Hyland
July 05, 2012
Programming
8
620
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
52
Git: an introduction
duien
3
170
Other Decks in Programming
See All in Programming
uniqueパッケージの内部実装を支えるweak pointerの話
magavel
0
810
Swift Concurrency - 状態監視の罠
objectiveaudio
2
280
ポスターセッション: 「まっすぐ行って、右!」って言ってラズパイカーを動かしたい 〜生成AI × Raspberry Pi Pico × Gradioの試作メモ〜
komofr
0
750
階層構造を表現するデータ構造とリファクタリング 〜1年で10倍成長したプロダクトの変化と課題〜
yuhisatoxxx
3
800
Playwrightはどのようにクロスブラウザをサポートしているのか
yotahada3
7
2.2k
AIで開発生産性を上げる個人とチームの取り組み
taniigo
0
130
iOSアプリの信頼性を向上させる取り組み/ios-app-improve-reliability
shino8rayu9
0
120
Swiftビルド弾丸ツアー - Swift Buildが作る新しいエコシステム
giginet
PRO
0
1.5k
CSC509 Lecture 02
javiergs
PRO
0
400
WebエンジニアがSwiftをブラウザで動かすプレイグラウンドを作ってみた
ohmori_yusuke
0
160
Advance Your Career with Open Source
ivargrimstad
0
190
非同期jobをtransaction内で 呼ぶなよ!絶対に呼ぶなよ!
alstrocrack
0
300
Featured
See All Featured
Visualization
eitanlees
148
16k
Connecting the Dots Between Site Speed, User Experience & Your Business [WebExpo 2025]
tammyeverts
8
560
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
194
16k
Art, The Web, and Tiny UX
lynnandtonic
303
21k
Exploring the Power of Turbo Streams & Action Cable | RailsConf2023
kevinliebholz
34
6.1k
Build The Right Thing And Hit Your Dates
maggiecrowley
37
2.9k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
667
120k
Being A Developer After 40
akosma
90
590k
Testing 201, or: Great Expectations
jmmastey
45
7.7k
Practical Orchestrator
shlominoach
190
11k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
32
2.2k
The Art of Delivering Value - GDevCon NA Keynote
reverentgeek
15
1.7k
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