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
530
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
42
Git: an introduction
duien
3
160
Other Decks in Programming
See All in Programming
Micro Frontends for Java Microservices - Devnexus 2024
mraible
PRO
0
490
PHPはいつから死んでいるかの調査
chiroruxx
1
400
大規模Reactアプリのリアーキテクチャ~8万行のTanStack Query移行の軌跡~
kj455
4
960
Git Lint
bkuhlmann
4
750
Kotlin Multiplatform at Stable and Beyond (Android Makers 2024)
zsmb
0
260
使ってみよう Azure AI Document Intelligence
kosmosebi
2
310
Komplexe Oberflächen mit SVG und der Web Animation API
joergneumann
0
670
Site Reliability Engineering for GMO
pyama86
8
1k
if constexpr文はテンプレート世界のラムダ式である
faithandbrave
3
650
スクラムガイドのスプリントレトロスペクティブを改めて読みかえしてみた / Re-reading the Sprint Retrospective Section in the Scrum Guide
mackey0225
3
430
デフォルトにして至高、RubyMineの大好きな所
ruzia
0
390
try!Swift Tokyo 2024 参加報告 LT
akidon0000
1
220
Featured
See All Featured
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
9
8.3k
Done Done
chrislema
178
15k
Being A Developer After 40
akosma
57
580k
Gamification - CAS2011
davidbonilla
76
4.6k
5 minutes of I Can Smell Your CMS
philhawksworth
199
19k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
125
32k
Into the Great Unknown - MozCon
thekraken
10
990
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
30
6k
[RailsConf 2023] Rails as a piece of cake
palkan
23
4k
Faster Mobile Websites
deanohume
299
30k
Scaling GitHub
holman
457
140k
Keith and Marios Guide to Fast Websites
keithpitt
408
22k
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