Rails%203%20In%20Action

Linking tickets to users
attributes = attributes.merge!(:user => User.find_by_email!(email))
@project.tickets.create!(attributes)
end
end
With this step definition in place, the feature should pass. Let’s do another run of
bin/cucumber features/viewing_tickets.feature:
1 scenario (1 passed)
19 steps (20 passed)
Let’s now fix up the other two, beginning with the Editing Tickets feature.
6.5.4 Fixing the Editing Tickets feature
You can re-use the step definition you created in the previous section in the features/
editing_tickets.feature by changing the first few lines of the Background to be identical
to the next listing.
Listing 6.11 features/editing_tickets.feature
Given there are the following users:
| email | password |
| user@ticketee.com | password |
Given there is a project called "TextMate 2"
And "user@ticketee.com" has created a ticket for this project:
| title | description |
| Make it shiny! | Gradients! Starbursts! Oh my! |
When you run the feature—unlike the Viewing Tickets feature—it doesn’t pass, complaining
that it can’t find the field called Title. Uh oh:
cannot fill in, no text field, text area or password field with id,
name, or label 'Title' found (Capybara::ElementNotFound)
Back in the TicketsController, you restricted some of the actions by using the
before_filter:
before_filter :authenticate_user!, :except => [:index, :show]
This before_filter restricts any access to the edit action for people who are not
signed in. In this feature then, you should sign in as the user you create so you can
edit this ticket. Change the first line of the Background to sign in as that user:
Background:
Given there are the following users:
| email | password |
| user@ticketee.com | password |
And I am signed in as them
When you run this feature, you see the last step in the example is undefined. You must
define this new step so you can sign in as the user set up in the first step of the
Background. Because you assigned @user in the there are the following users step,
you can reference this variable in the new step. Define this new step at the bottom of
features/step_definitions/user_steps.rb by copying the lines from features/signing_in
.feature and doing a couple of replacements, as shown in the following listing.
133