How can I see what capybara found in a failing cucumber step?

Question

I started migrating from cucumber + webrat to cucumber + capybara. Now the behavior of "I should see " seems to be somewhat different. Most of these fail now, although I didn't change anything on the page. I replaced the snippet that should be found with some stuff that is on every page and for some text it works and for other text it doesn't. I can't find any pattern in what is found in the page's content and what is not. Webrat used to print what the page content is that it found, in case it did not contain the required phrase. Is there anyway to have capybara show what text it got from the page in which it tried to find the text?

Alvar

As someone completely unfamiliar with the technologies named, this is my favourite stack overflow question title, ever! – Electret

Yeah, it sounds like something zoo related. – Alvar

@Electret ignorance is bliss – Clea

Answer 1

Try adding this step:

Then show me the page

Longe

I know this is super old, but after adding that directive I had to install the gem 'launchy' and it launched the page with the contents, truly great. – Jenjena

Answer 2

Then show me the page calls webrat/capybara's underlying save_and_open_page method. Found that useful when working with steak.

Tolley

Answer 3

If you want to have the browser open the page when the page fails you use the 'launchy' gem. Add it to your gem file, and then in /features/support create a file called debugging.rb with contents:

After do |scenario|
   save_and_open_page if scenario.failed?
end

Laundryman

This is spectacularly useful, thanks. It seems like it should be installed by default with Cucumber. – Wealthy

Answer 4

If you're using Javascript or Ajax in your pages and want to see what's going on, I've found that the Poltergeist driver is very good at letting you get into the DOM and find out what's going wrong.

If you setup your Capybara driver with the remote debugging option:

Capybara.register_driver :poltergeist do |app|
  Capybara::Poltergeist::Driver.new(app, inspector: true)
end

You can then put the following line in your steps:

page.driver.debug 

Which fires up a new Chromium browser with the current DOM state set, letting you get at the console. (On my version of Linux, I had to symlink chromium to chromium-browser but it otherwise worked fine).

Source Info: http://jonathanleighton.com/articles/2012/poltergeist-0-6-0/

Ichthyo

Answer 5

Then show me the response didn't work for me with cucumber 1.1. I found useful to write a step using capybara's command:

print page.html

This outputs the current state of the DOM

Consubstantiation

Answer 6

You could also use "Then show me the response" which outputs the HTML to the console if you don't want to use a browser.

Monstrance

Answer 7

You could always have it take a screen shot when something failed. I debug a LOT of failing features that way.

Intendance