Headless browser testing using X virtual frame buffer
My current setup is using Jenkins as my CI environment, which has some ubuntu server nodes to execute the end to end browser tests on some amazon EC2 machines using selenium 2.
I am wondering if there exist limitations running tests using Xvfb, as oppose to using a real X server hooked up to a real display.
What are the pros and cons of doing headless browser testing on a Linux machine using X virtual frame buffer?
We are using Xvfb in our Continuous Integration environment and it is working great. It's no problem to take screenshots from Selenium for later analysis when errors are found. We have found no problems with this solution, rather a great advantage to be able to use virtual servers to spawn massively parallel tests against installations of the software.