Rails Phantomjs, poltergeist, and Capybara not playing well together

Question

Working in a rails 3.1.2 project (mac OS X), I have PhantomJS properly installed (I can run code like the following and it works perfectly, accurately grabbing the title of the page and saving an accurate screenshot)

try_phantom.coffee

page = require('webpage').create()
page.open 'http://localhost:5000/parties/onetestparty', (status) ->
    title = page.evaluate -> document.title
    console.log "Title: #{title}"
    page.render './log/javascript_screenshot.png'
    phantom.exit()

However, when I attempt to use capybara/poltergeist in rspec as follows:

spec_helper.rb

require 'capybara/poltergeist'
Capybara.javascript_driver = :poltergeist

and then using a spec with a call requiring javascript:

parties_spec.rb

        it "should allow a simple screenshot", js: true do
            visit "/"
            page.driver.render('./log/screen_Home.png', :full => true)
        end

It doesn't appear that my javascript is being rendered, and also the screenshot is always blank!

I've tried the debugger, but that seems to also bring up a blank HTML page (just html with empty head and body tags)

I'm pretty sure the problem is either the interface between capybara and poltergeist or (more likely) poltergeist and phantomjs. Here are the versions of the relevant gems:

capybara 1.1.3
capybara-webkit 0.13.0
poltergeist 1.0.2
phantomjs is 1.7.0

Not sure how to troubleshoot further... Any help would be appreciated.

Note: One thing I have also tried is telling poltergeist explicitly where my phantomjs can be found: :phantomjs => "/usr/local/Cellar/phantomjs/1.7.0/bin/phantomjs". This doesn't change the result... However, I think it proves that phantomjs IS actually getting run, because if I give it a bogus path, I do get an error. — Dave Collins, Nov 27 '12 at 01:03

score 11 · Accepted Answer · answered Nov 27 '12 at 14:43

11

Create a very simple test and see what happens.

simple_spec.rb

require 'spec_helper'
require 'capybara/poltergeist'
include Capybara::DSL
Capybara.javascript_driver = :poltergeist

describe 'some stuff which requires js', :js => true do
  it 'will take a screenshot' do
    visit("http://google.com")
    page.driver.render('./file.png', :full => true)
  end
end

Does that get you an image of Google?

answered Nov 27 '12 at 14:43

theSociableme

842
1
10
23

Yes, it does... In fact, I have found that if I leave a rails server running, and modify your above code to visit "http://localhost:5000" then it does indeed render that page faithfully. However, when I add include Capybara::DSL into my other test specs they are crashing at different locations... Troubleshooting now. Thanks!! – Dave Collins Nov 27 '12 at 16:22
I'm going to mark this answer as correct because it got me past the issue of "cannot make a screenshot from within rspec". I've still got Capybara::DSL troubleshooting, but that is a separate issue. Thanks! – Dave Collins Nov 28 '12 at 13:11

score 6 · Answer 2 · answered Dec 05 '12 at 11:00

6

I had the same problem, but in my case it was caused by using subdomains. Poltergeist was pointed to meaningless url (sort of "http://spb.:22789") so it receives nothing but 'about:blank'.

To solve this issue I did following:

Set app_host and server_port for Capybara

Capybara.app_host = 'http://city.tulp.test:3003'
Capybara.server_port = 3003
Add dummy domain to /etc/hosts

Hope this helps.

answered Dec 05 '12 at 11:00

Eugene

448
4
12

I will try this out and let you know! Thanks! – Dave Collins Dec 05 '12 at 21:46
Hmmm. Same result... @Eugene I am assuming that you set your .app_host to your LOCAL machine? Where the test suite is running? – Dave Collins Dec 06 '12 at 17:35
Oh.. I've just noticed your question, sorry. In case if it is still actual - yes, tests are running on local machine, but you can use http://lvh.me (which always points to 127.0.0.1) as more common solution. – Eugene Jan 11 '13 at 15:32

BvuRVKyUVlViVIc7 · Answer 3 · 2013-09-16T21:05:50.400

2

Maybe it helps if you register the driver?

Capybara.register_driver :poltergeist do |app|
  Capybara::Poltergeist::Driver.new(app, {debug: false})
end
Capybara.current_driver = :poltergeist # NOTE THE CURRENT_DRIVER, NOT JAVASCRIPT_DRIVER!

edited Sep 16 '13 at 21:05

answered Nov 26 '12 at 22:02

BvuRVKyUVlViVIc7

11,641
9
59
111

Great suggestion, but I have tried that (with debug both false and true) and no difference in the problem. Continually blank screen capture. – Dave Collins Nov 26 '12 at 22:50
1

try to add sleep 5 and then make the screenshot.. maybe it needs some time to display – BvuRVKyUVlViVIc7 Nov 26 '12 at 23:41
Another great suggestion, but no matter how long I sleep, it just comes up empty. – Dave Collins Nov 27 '12 at 00:20
Interesting note, though: When I add that .current_driver line, the whole process takes longer... But same result. – Dave Collins Nov 27 '12 at 01:32
2

Note: There is two `r` for `current_driver` – Dorian Sep 16 '13 at 19:29
3

Haha so funny, after one year i tried to solve the same problem again.. and found my own answer ^^ – BvuRVKyUVlViVIc7 Dec 04 '13 at 22:10
@Lichtamberg I also face the same problem now. Can you tell me your solution? Thank before hand. :) – Phanith Mar 21 '16 at 08:34
I just had to register the driver via Capybara.current_driver... I think at least.. Already some time ago :) – BvuRVKyUVlViVIc7 Mar 21 '16 at 10:07

Rails Phantomjs, poltergeist, and Capybara not playing well together

3 Answers3