Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>There are a few options:</p> <ul> <li><p>You could use Selenium Grid so that the browser is opened on a completely different machine (or virtual machine) that you can then connect to via VNC or Remote Desktop Connection if you wanted to see the browser. Also, another option: if you run a Jenkins foreground process on that remote server, it can execute your test project on the desktop.</p></li> <li><p>You can run Selenium 'headless' on Linux in XVFB. I've never tried doing this and doubt it's really worth the effort. <a href="http://www.alittlemadness.com/2008/03/05/running-selenium-headless/" rel="noreferrer">http://www.alittlemadness.com/2008/03/05/running-selenium-headless/</a></p></li> <li><p>You can wrap Selenium RC in a Windows service. <a href="http://support.microsoft.com/kb/137890" rel="noreferrer">http://support.microsoft.com/kb/137890</a> . Except that permissions constraints on later versions of windows will probably prevent Selenium from accessing the desktop like Windows 2000 used to allow us to do.</p></li> <li><p>Another option would be to use something like WebDriver HTMLUnitDriver, which doesn't launch a 'real' browser. <a href="http://code.google.com/p/webdriver/" rel="noreferrer">http://code.google.com/p/webdriver/</a> . Also there is a PhantomJS option as well as a 'headless Chrome' that you could use.</p></li> <li><p>Of course there's also the option of using a service like SauceLabs, where you can get your tests to be run in the cloud. After your tests have completed you can watch a video of them running.</p></li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload