Rails%203%20In%20Action

296 CHAPTER 11 Tagging
Because the user that is set up in spec/controllers/comments_controller_spec.rb
doesn’t have permission to tag, when you re-run your spec it will now pass:
2 examples, 0 failures
Good! You have something in place to block users from tagging tickets when they create
a comment. Now you’re only missing the blocking code for tagging a ticket when it
is being created. You can create a spec test for this too, this time in spec/controllers/
tickets_controller_spec.rb. Underneath the “Cannot delete a ticket without permission”
example, add this example:
it "can create tickets, but not tag them" do
Permission.create(:user => user, :thing => project,
➥:action => "create tickets")
post :create, :ticket => { :title => "New ticket!",
:description => "Brand spankin' new" },
:project_id => project.id,
:tags => "these are tags"
Ticket.last.tags.should be_empty
end
You can run this spec by running bin/rspec spec/controllers/tickets_controller
_spec.rb:59, and you’ll see that it fails:
Failure/Error: Ticket.last.tags.should be_empty
expected empty? to return true, got false
Because there is no restriction on tagging a ticket through the create action, there
are tags for the ticket that was just created, and so your example fails. For your
TicketsController’s create action, you can do exactly what you did in the
CommentsController’s create action and change the line that calls tag! to this:
if can?(:tag, @project) || current_user.admin?
@ticket.tag!(params[:tags])
end
When you re-run your spec it will pass:
1 example, 0 failures
Great, now you’re protecting both the ways a ticket can be tagged. Because of this
new restriction, the two scenarios that you created earlier to test this behavior will be
broken.
11.3.2 Tags are allowed, for some
When you run rake cucumber:ok you see them listed as the only two failures:
Failing Scenarios:
cucumber features/creating_comments.feature:45
cucumber features/creating_tickets.feature:48
To fix these two failing scenarios, you use a new step, which you first put in the “Creating
comments” feature underneath this line in the Background for this feature
And "user@ticketee.com" can view the "Ticketee" project