Rails%203%20In%20Action

82 CHAPTER 3 Developing a real Rails application
Next we covered the basic setup of a Rails application, which started with the rails
new command that initializes an application. Then we segued into setting up the Gemfile
to require certain gems for certain environments, such as RSpec in the test environment,
and then running the installers for these gems so your application is fully
configured to use them. For instance, after running rails g rspec:install, your
application is set up to use RSpec and so will generate RSpec specs rather than the
default Test::Unit tests for your models and controllers.
Finally, you wrote the first story for your application, which involved generating a
controller and a model as well as an introduction to RESTful routing and validations.
With this part of your application covered by Cucumber features, you can be notified
if it is broken by running rake cucumber:ok, a command that runs all the features of
the application and lets you know if everything is working or if anything is broken. If
something is broken, the feature fails, and then it’s up to you to fix it. Without this
automated testing, you would have to do it all manually, and that just isn’t any fun.
Now that you’ve got a first feature under your belt, let’s get into writing the next
one!