Rails%203%20In%20Action

100 CHAPTER 5 Nested resources
New Ticket link on a project’s show page. The link must lead to a form where a title
and a description for your ticket can be entered, and the form needs a button that
submits it to a create action in your controller. You also want to ensure the data is
valid, just as you did with the Project model. Start by using the code from the following
listing in a new file.
Listing 5.1 features/creating_tickets.feature
Feature: Creating Tickets
In order to create tickets for projects
As a user
I want to be able to select a project and do that
Background:
Given there is a project called "Internet Explorer"
And I am on the homepage
When I follow "Internet Explorer"
And I follow "New Ticket"
Scenario: Creating a ticket
When I fill in "Title" with "Non-standards compliance"
And I fill in "Description" with "My pages are ugly!"
And I press "Create Ticket"
Then I should see "Ticket has been created."
Scenario: Creating a ticket without valid attributes fails
When I press "Create Ticket"
Then I should see "Ticket has not been created."
And I should see "Title can't be blank"
And I should see "Description can't be blank"
When you run the code in listing 5.1 using the bin/cucumber features/
creating_tickets.feature command, your background fails, as shown here:
And I follow "New Ticket"
no link with title, id or text 'New Ticket' found ...
You need to add this New Ticket link to the app/views/projects/show.html.erb template.
Add it underneath the Delete Project link, as shown in the following listing.
Listing 5.2 app/views/projects/show.html.erb
This helper is called a nested routing helper and is just like the standard routing helper.
The similarities and differences between the two are explained in the next section.
5.1.1 Nested routing helpers
In listing 5.2, you used a nested routing helper—new_project_ticket_path—rather
than a standard routing helper such as new_ticket_path because you want to create a
new ticket for a given project. Both helpers work in a similar fashion, except the
nested routing helper takes one argument always, the @project object for which you
want to create a new ticket: the object that you’re nested inside. The route to any