Rails%203%20In%20Action

Fixing what you broke
When you run bin/cucumber features/editing_tickets.feature, both scenarios
should pass:
2 scenarios (2 passed)
26 steps (26 passed)
Great! You fixed another feature. The one remaining feature that fails is Viewing Tickets,
which you fix in the same way as you fixed the previous features. Add this line
again underneath where you create the TextMate 2 project, this time in features/
viewing_tickets.feature:
And "user@ticketee.com" can view the "TextMate 2" project
You also need to add one for the Internet Explorer project:
And "user@ticketee.com" can view the "Internet Explorer" project
Also in this feature, you’re not signing in as the user who has these permissions, so
directly underneath the first step in your Background, add the following step:
And I am signed in as them
Running bin/cucumber features/viewing_tickets.feature, you’ll see that this feature
is passing:
1 scenario (1 passed)
23 steps (23 passed)
That was fast! All four failing features are fixed. Well, so we hope. You independently
verified them, but run rake cucumber:ok spec to make sure nothing else is broken:
33 scenarios (33 passed)
287 steps (287 passed)
# and
16 examples, 0 failures, 8 pending
Great! Everything’s working again! Let’s commit that:
git add .
git commit -m "Made projects only visible to users with
permission to see them"
git push
In these first two sections, you added the restriction on the ProjectsController that
projects should be accessible only to users with Permission records with the action
set to view. In the process, you broke a couple of features, but fixing them was really
simple.
However, these changes only protect the actions in the ProjectsController that
use the find_project method and not those in the TicketsController. Before you
make changes in the TicketsController, note that the links to all projects are still visible
to all users through the ProjectsController’s index, which is definitely something
you should fix first.
175