http://www.markhneedham.com/blog/2011/12/15/webdriver-getting-it-to-play-nicely-with-xvfb/
Thoughts on Software Development
Another thing we’ve been doing with WebDriver is having it run with the FirefoxDriver while redirecting the display output into the Xvfb framebuffer so that we can run it on our continuous integration agents which don’t have a display attached.
The first thing we needed to do was set the environment property ‘webdriver.firefox.bin’ to our own script which would point the display to Xvfb before starting Firefox:
import java.lang.System._ |
Our first version of the script looked like this:
/our/awesome/starting-firefox.sh
#!/bin/bash |
The mistake we made here was that we started Xvfb in the background which meant that sometimes it hadn’t actually started by the time Firefox tried to connect to the display and we ended up with this error message:
No Protocol specified |
We really wanted to keep Xvfb running regardless of whether the Firefox instances being used by WebDriver were alive or not so we moved the starting of Xvfb out into a separate script which we run as one of the earlier steps in the build.
We also struggled to get the FirefoxDriver to kill itself after each test as calling ‘close’ or ‘quit’ on the driver didn’t seem to kill off the process.
We eventually resorted to putting a ‘pkill firefox’ statement at the start of our firefox starting script:
/our/awesome/starting-firefox.sh
#!/bin/bash |
It’s a bit hacky but it does the job more deterministically than anything else we’ve tried previously.