Rails%203%20In%20Action

208 CHAPTER 8 More authorization
Listing 8.20 features/assigning_permissions.feature
Scenario: Updating a ticket for a project
When I check "View" for "TextMate 2"
And I check "Edit tickets" for "TextMate 2"
And I press "Update"
And I follow "Sign out"
Given I am signed in as "user@ticketee.com"
When I follow "TextMate 2"
And I follow "Shiny!"
And I follow "Edit"
And I fill in "Title" with "Really shiny!"
And I press "Update Ticket"
Then I should see "Ticket has been updated"
Scenario: Deleting a ticket for a project
When I check "View" for "TextMate 2"
And I check "Delete tickets" for "TextMate 2"
And I press "Update"
And I follow "Sign out"
Given I am signed in as "user@ticketee.com"
When I follow "TextMate 2"
And I follow "Shiny!"
And I follow "Delete"
Then I should see "Ticket has been deleted."
The scenarios should be descriptive enough to understand—no particular magic
going on here. But you’re acting on a ticket in both these scenarios that doesn’t exist:
the Shiny! ticket. You need to create this ticket in your Background if you want these
scenarios to pass. Add this step definition right under the line in the Background that
creates the TextMate 2 project, as shown next:
And "user@ticketee.com" has created a ticket for this project:
| title | description |
| Shiny! | Eye-blindingly so |
Now when you run this feature, your two newest scenarios are failing, both with similar
errors:
cannot check field, no checkbox with id, name,
or label 'permissions_1_update_tickets' found
# and
cannot check field, no checkbox with id, name,
or label 'permissions_1_delete_tickets' found
Of course! You have no check boxes for Capybara to check yet! Add them now by changing
the permissions method in app/helper/admin/permissions_helper.rb from this
def permissions
{
"view" => "View",
"create tickets" => "Create Tickets"
}
end