Rails%203%20In%20Action

438 CHAPTER 16 Basic performance enhancements
Given /^there are (\d+) tickets for this project$/ do |arg1|
pending # express the regexp above with the code you wish you had
end
Then /^I should see (\d+) pages of pagination$/ do |arg1|
pending # express the regexp above with the code you wish you had
end
Then /^I see page (\d+) of tickets for this project$/ do
pending # express the regexp above with the code you wish you had
end
The first step definition here has to do with tickets, and so you’ll put it in features/
step_definitions/ticket_steps.rb using the code shown in the following listing.
Listing 16.2 features/step_definitions/ticket_steps.rb
Given /^there are (\d+) tickets for this project$/ do |number|
number.to_i.times do |i|
@project.tickets.create!(:title => "Test",
:description => "Placeholder ticket.",
:user => @user)
end
end
This small piece of code will create as many tickets as you’ve specified for the
@project object set up by the “Given there is a project” step, using the @user variable
set up by the “Given there are the following users” step. It’s not important what the
title and description attributes are for these tickets, just that you have enough of them
to trigger the pagination links to appear.
The next two undefined steps can go into a new file called features/step
_definitions/pagination_steps.rb, as they’re about the pagination more than any other
resource in your application.
The Kaminari paginate method you’ll use in your view shortly will output a nav
element with the class of pagination. Inside this nav element there are a couple of
other elements. The first is a span element with the class of prev, which would contain
a Previous button if you’re a page or two in with pagination. After that, there are a
couple more span elements, all with the class of page. The span tag representing the
current page has an additional class name of current, which we’ll discuss a little later.
You can count these span.page elements easily, using the css method to find them
using a CSS selector and then using count on what that returns to count the number
of pages shown in pagination.
By gathering up these page elements and counting them, you easily assert that
there’s pagination on this page. You can define the next step like this in features/
step_definitions/pagination_steps.rb:
Then /^I should see (\d+) pages of pagination$/ do |number|
pages = all(".pagination .page")
pages.count.should eql(number.to_i)
end