Rails%203%20In%20Action

Summary
controller so anyone who reads the code knows that the controller responds to these
actions.
Back to the spec now: if you run bin/rspec spec/controllers/projects
_controller_spec.rb once more, the test now passes:
.
1 example, 0 failures
Let’s check to see if everything else is still working by running rake cucumber:ok and
then rake spec. You should see these outputs:
6 scenarios (6 passed)
37 steps (37 passed)
# and
.
3 examples, 0 failures, 2 pending
The RSpec output shows two pending examples. These come from the spec files for
ProjectsHelper (spec/helpers/projects_helper_spec.rb) and Project model (spec/
models/project_spec.rb) respectively. You can delete these files or remove the pending
lines from them to make your RSpec output green instead of yellow when it passes.
Other than that, these two specs have no effect on your test output.
It’s great to see that everything is still going! Let’s commit and push that!
git add .
git commit -m "Users should be redirected back to the projects page
if they try going to a project that doesn't exist."
git push
This completes the basic CRUD implementation for your project’s resource. Now you
can create, read, update, and delete projects to your heart’s content, and these features
are all well covered with tests, which leads to greater maintainability.
4.4 Summary
This chapter covered developing the first part of your application using BDD practices
and Cucumber and then making each step pass. Now you have an application that is
truly maintainable. If you want to know if these features or specs are working later in
the project, you can run rake cucumber:ok or rake spec and if something is broken,
you’ll know about it. Doesn’t that beat manual testing? Just think of all the time you’ll
save in the long run.
You learned firsthand how rapidly you can develop the CRUD interface for a
resource in Rails. There are even faster ways to do it (such as by using scaffolding, discussed
in chapter 1), but to absorb how this whole process works, it’s best to go
through it yourself, step by step, as you did in this chapter.
So far you’ve been developing your application using BDD techniques, and as your
application grows, it will become more evident how useful these techniques are. The
main thing they’ll provide is assurance that what you’ve coded so far is still working
exactly as it was when you first wrote it. Without these tests, you may accidentally break
97