Your SlideShare is downloading. ×
0
Applying RSpec Best Practises
Applying RSpec Best Practises
Applying RSpec Best Practises
Applying RSpec Best Practises
Applying RSpec Best Practises
Applying RSpec Best Practises
Applying RSpec Best Practises
Applying RSpec Best Practises
Applying RSpec Best Practises
Applying RSpec Best Practises
Applying RSpec Best Practises
Applying RSpec Best Practises
Applying RSpec Best Practises
Applying RSpec Best Practises
Applying RSpec Best Practises
Applying RSpec Best Practises
Applying RSpec Best Practises
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Applying RSpec Best Practises

493

Published on

Kevin McKelvin …

Kevin McKelvin
Rubyfuza 2013

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
493
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Applying RSpec Best Practices Kevin McKelvin Rubyfuza 2013
  • 2. Ground Rules• Tests must support OO principles• Tests must be technical documentation for the code
  • 3. The Example Conway’s Game of LifeDeterministicZero Player Game
  • 4. Be descriptive it “should work!” do end
  • 5. The describe block describe Game do end Describe a Ruby Constant
  • 6. The describe block describe Game do describe "#tick" do end end Prefix instance methods with # and class methods with .
  • 7. The context blockdescribe Game do describe "#tick" do context "when given an empty world" do end endend Use contexts to find edge cases Start contexts with when or with
  • 8. The it blockdescribe Game do describe "#tick" do context "when given an empty world" do it "returns an empty world" do end end endend “Do or do not, there is no try” - Yoda
  • 9. Use RSpec Matchersdescribe Game do describe "#tick" do context "when given an empty world" do it "returns an empty world" do empty_world = World.new second_world = subject.tick( empty_world) second_world.empty?.must.equal true end end endend
  • 10. Use RSpec Matchersdescribe Game do describe "#tick" do context "when given an empty world" do it "returns an empty world" do empty_world = World.new second_world = subject.tick( empty_world) second_world.must.be_empty end end endend
  • 11. RSpec Settings.rspec --color --profile --format d
  • 12. Running Your SpecsGame #tick when given an empty world returns an empty world when given a world with one cell returns an empty world when given a world with three adjacentcells returns a world with one cell
  • 13. Remember TDDSupport Object Oriented best-practices SOLID Law of Demeter
  • 14. Remember TDDDon’t test your framework
  • 15. Remember TDDAvoid integration testing where possible
  • 16. Remember TDDBe the first consumer of your public API
  • 17. ResourcesRSpec:http://rspec.info/The RSpec Book:http://pragprog.com/book/achbd/the-rspec-bookBetter Specs:http://www.betterspecs.orgMustard:https://github.com/ryanb/mustard

×