The solution was to simply define another constant to hold the original default per page value.

In features/support/hooks.rb:

Before(‘@no-pagination’) do
ActiveRecord::Base.instance_eval do
def per_page; 1_000_000; end
end
silence_warnings { DEFAULT_PER_PAGE = ActiveRecord::Base.per_page }
end

After(‘@no-pagination’) do
ActiveRecord::Base.instance_eval do
def per_page; ORIGINAL_PER_PAGE; end
end
silence_warnings { DEFAULT_PER_PAGE = ActiveRecord::Base.per_page }
end

And modified my config/environments/test.rb:

DEFAULT_PER_PAGE = ORIGINAL_PER_PAGE = ActiveRecord::Base.per_page

So now for the features and scenarios that I require no pagination, I tag them with @no-pagination and it all works.

silence_warnings { DEFAULT_PER_PAGE = ActiveRecord::Base.per_page }

One the Gems (env-js perhaps?) requires Johnson, and Johnson doesn’t compile with Ruby 1.9 right now:
http://groups.google.com/group/johnson-talk/msg/cf2ad08e55dd0911

I’ll try this again in a month or so.

The @javascript tag is what you need to add to any of your cucumber scenarios/features that use javascript. The envjs is the driver that Capybara uses to carry out these javascript related scenarios. That’s the basic difference.

I hope that helps.

Cheers,

Michael.