Rails%203%20In%20Action

Viewing projects
If you run the Cucumber feature again, you get this error, which isn’t helpful at first
glance:
Showing /[path to ticketee]/app/views/projects/index.html.erb
where line #5
raised:
You have a nil object when you didn't expect it!
You might have expected an instance of Array.
This error points at line 5 of your app/views/projects/index.html.erb file. From this
you can determine that the error has something to do with the @projects variable.
This variable isn’t yet been defined, and because there’s no each method on nil, you
get this error. As mentioned in chapter 3, instance variables in Ruby return nil rather
than raise an exception if they’re undefined. Watch out for this in Ruby—as seen
here, it can sting you hard.
To define this variable, open ProjectsController at app/controllers/
projects_controller.rb and change the index method definition to look like the following
listing.
Listing 4.4 app/controllers/projects_controller.rb
def index
@projects = Project.all
end
By calling all on the Project model, you retrieve all the records from the database as
Project objects, and they’re available as an Array-like object. Now that you’ve put all
the pieces in place, you can run the feature with bin/cucumber features/
viewing_projects.feature, and all the steps should pass:
1 scenario (1 passed)
4 steps (4 passed)
The feature now passes. Is everything else still working, though? You can check by running
rake cucumber:ok. At the bottom, you should see this:
3 scenarios (3 passed)
16 steps (16 passed)
All of your scenarios and their steps are passing, meaning all of the functionality
you’ve written so far is working as it should. Commit and push this using
git add .
git commit -m "Added the ability to view a list of all projects"
git push
The reading part of this CRUD resource is done! You’ve got the index and show
actions for the ProjectsController behaving as they should. Now you can move on
to updating.
87