Rails%203%20In%20Action

Linking tickets to users
Make sure to run db:test:prepare
If you don’t prepare the test database, the following error occurs when you run the
feature:
And I press "Create Ticket"
undefined method 'email' for nil:NilClass (ActionView::Template::Error)
Watch out for that one.
Only one scenario fails now. We’re right back to the missing “Created by user@ticketee
.com” text. Open app/views/tickets/show.html.erb and, above the ticket description,
put the following line:
Created by
This line adds the text the feature needs to pass, so when you run bin/cucumber
features/creating_tickets.feature, you get the following output:
3 scenarios (3 passed)
44 steps (44 passed)
You should run rake cucumber:ok spec as usual to ensure you haven’t broken anything:
Failing Scenarios:
cucumber features/deleting_tickets.feature:15
cucumber features/editing_tickets.feature:16
cucumber features/viewing_tickets.feature:18
Oops, it looks like you did! If you didn’t have these tests in place, you wouldn’t have
known about this breakage unless you tested the application manually or guessed (or
somehow knew) that your changes would break the application in this way. Let’s see if
you can fix it.
6.5.2 We broke something!
Luckily, all the failed tests have the same error
When I follow "Make it shiny!"
undefined method 'email' for nil:NilClass (ActionView::Template::Error)
...
./app/views/tickets/show.html.erb:4:in ...
Whatever is causing this error is on line 4 of app/views/tickets/show.html.erb:
Created by
Aha! The error is undefined method 'email' for nil:NilClass, and the only place
you call email on this line is on the user object from @ticket, so you can determine
that user must be nil. But why? Let’s have a look at how to set up the data in the
features/viewing_tickets.feature feature, as shown in the following listing.
131