Rails%203%20In%20Action

def edible?
!expired
end
Behavior-driven development
When you run rspec spec again, both your specs will pass:
..
2 examples, 0 failures
Let’s go back in to lib/bacon.rb and remove the self. from the expired! method:
def expired!
expired = true
end
If you run rspec spec again, you’ll see your second spec is now broken:
Failure/Error: Bacon expired!
expected edible? to return false, got true
Tests save you from making mistakes such as this. If you write the test first and then
write the code to make the test pass, you have a solid base and can refactor the code to
be clearer or smaller and finally ensure that it’s still working with the test you wrote in
the first place. If the test still passes, then you’re probably doing it right.
If you change this method back now
def expired!
self.expired = true
end
and then run your specs using rspec spec, you’ll see that they once again pass:
..
2 examples, 0 failures
Everything’s normal and working once again, which is great!
That ends our little foray into RSpec for now. You’ll use it again later when you
develop your application. If you’d like to know more about RSpec, The RSpec Book:
Behavior-Driven Development with RSpec, Cucumber, and Friends (David Chelimsky et al.,
Pragmatic Bookshelf, 2010) is recommended reading.
2.3.2 Cucumber
Listing 2.18 bacon/lib/bacon.rb
For this section, we retire the Bacon example and go for something more formal with
Cucumber.
NOTE This section assumes you have RSpec installed. If you don’t, use this
command to install it: gem install rspec.
Whereas RSpec and Test::Unit are great for unit testing (testing a single part), Cucumber
is mostly used for testing the entire integration stack.
35