Debugging Capybara Poltergeist tests in RailsI made the switch from selenium webdriver to poltergeist on my capybara tests when the suite started taking 20 minutes to run. (For my process of getting the test suite under control, check out my previous post.) While poltergeist has definitely been a boon, it can sometimes be hard to debug because I can’t physically see the page. That’s where this tip comes in handy, stolen from the Quickleft blog:
Find the Port Address and Pause the Test
Sometimes I just want to see what's going on in the browser. Although save_and_open_page gives you some idea of what's going on, you can't really click around, because the page it gives you is static and lacking assets. To dig into what's going on, I like to use a trick I learned from my mentor, Mike Pack.
Just above the broken line in your test, add these two lines of code. Note that you have to have pry installed in your current gemset or specified in the Gemfile for this to work.
require 'pry'; binding.pry
Run the specs, and when they pause, copy the url and port number from the test output.
Open your browser and paste the address into the window. Voila! You're now browsing your site in test mode!
Thanks again to the Quickleft folks for this cool tip - it’s one of five tricks for less painful testing.