Rails%203%20In%20Action

Pagination
Here you use Capybara’s all method, which will find all the elements matching the
CSS selector specified and return them as an Array object. Then it’s a simple matter of
calling count on that Array and making sure it contains as many as you say it should.
You final undefined step asserts that you’re on a specific page of the pagination.
Write this step like this:
Then /^I see page (\d+) of tickets for this project$/ do |number|
current_page = find(".pagination .current").text.strip
current_page.should eql(number)
end
You use the find method rather than the all method because there is only going to
be one current page element. This method will only return a single element, which
matches the specified CSS selector. Calling text on this element will return the number
inside it, and you can strip it (as it contains spaces) and then compare that to the
number passed in for your step. If the two numbers are equal, then this step will pass.
With the last of your undefined steps now actually defined, let’s see what happens
when you run bin/cucumber features/pagination.feature:
Then I should see 2 pages of pagination
expected 2
got 0
IMPLEMENTING PAGINATION HELPERS
Your step that checks for two pages of pagination wasn’t able to see any at all, most
likely because you aren’t showing any right now! To fix this, you’ll have to display the
pagination link in app/views/projects/show.html.erb by putting this line above the ul
that displays tickets:
This line will display the pagination links that your failing step currently requires.
You’re going to need to set up the @tickets variable for pagination in your controller
so that these pagination links know what page you’re on and that there are only 50
tickets displayed. You’ll replace this line in the show action of app/controllers/
projects_controller.rb
@tickets = @project.tickets
with this line:
@tickets = @project.tickets.page(params[:page]).per(50)
This page method will set @tickets to display only the tickets for the current page
number, available in the params[:page] variable. The per method after it will retrieve
50 ticket objects rather than Kaminari’s default 25. Your tickets don’t take up much
room on your page so you can bump this up.
When you run your feature again with bin/cucumber features/paginating
_tickets.feature, it will pass because you’ve now got your pagination links showing:
439