Rails%203%20In%20Action

246 CHAPTER 10 Tracking state
group :test do
gem 'cucumber-rails'
gem 'capybara'
gem 'database_cleaner'
gem 'factory_girl'
gem 'email_spec'
gem 'launchy'
end
When you run bundle install, it will install the launchy gem for you. Let’s rerun
your feature again. This time, a page pops up with your home page, as shown in
figure 10.2.
See how there are two Ticketee links on this page? Capybara’s dutifully following
your instruction to click the Ticketee link, and it clicks the first link it finds on the
page! You want it to click the second link. Let’s change the line in your features/
creating_comments.feature that follows this link to the following:
And I follow "Ticketee" within "#projects"
Here you use the within version of this step which will look up the link within the element
with the id attribute set to “projects.” No element currently has this attribute, so
let’s preempt the scenario failing on this step and add this id to the ul element in
app/views/projects/index.html.erb, as shown in the following listing.
Listing 10.2 app/views/projects/index.html.erb
Good! That should make your scenario follow the correct link. Try rerunning it now.
You should see this:
And I fill in "Text" with "Added a comment!"
cannot fill in, no text field, text area or password field
with id, name, or label 'Text' found (Capybara::ElementNotFound)
Oops! A web page from the "Then show me the page" step came up. Remove this step
from your scenario now.
This failing step means that you’ve got work to do! The label it’s looking for is
going to belong to the comment box underneath your ticket’s information.
Figure 10.2 The home page