Rails%203%20In%20Action

Viewing tickets
Quite the long feature! We’ll go through it piece by piece in just a moment. First, let’s
examine the within usage in your scenario. Rather than checking the entire page for
content, this step checks the specific element using Cascading Style Sheets (CSS)
selectors. The #ticket prefix finds all elements with an ID of ticket that contain an
h2 element with the content you specified. This content should appear inside the
specified tag only when you’re on the ticket page, so this is a great way to make sure
that you’re on the right page and that the page is displaying relevant information.
The first step passes because you defined it previously; the next one is undefined.
Let’s see this by running bin/cucumber features/viewing_tickets.feature:
Undefined step: "that project has a ticket:" (Cucumber::Undefined)
The bottom of the output tells you how to define the step:
Given /^that project has a ticket:$/ do |table|
# table is a Cucumber::Ast::Table
pending # express the regexp above with the code you wish you had
end
This step in the scenario is defined using the following syntax:
| title | description |
| Make it shiny! | Gradients! Starbursts! Oh my! |
For Cucumber, this syntax represents a table, which is what the step definition hints at.
Using the code shown in the following listing, define this step inside a new file at features/step_definitions/ticket_steps.rb.
Listing 5.9 features/step_definitions/ticket_steps.rb
Given /^that project has a ticket:$/ do |table|
table.hashes.each do |attributes|
@project.tickets.create!(attributes)
end
end
Because you used a table here, Cucumber provides a hashes method for the table
object, which uses the first row in the table as keys and the rest of the rows (as many as
you need) for the values of hashes stored in an array. In this step, you iterate through
this array, and each hash represents the attributes for the tickets you want to create.
One thing that you haven’t done yet is define the @project variable used inside
this iterator. To do that, open features/step_definitions/project_steps.rb and change
this line
Factory(:project, :name => name)
to the following:
@project = Factory(:project, :name => name)
Instance variables are available throughout the scenario in Cucumber, so if you define
one in one step, you may use it in the following steps. If you run the feature again, you
109