Skip to main content

Headless tests with Firefox WebDriver

There are times when you don't want a browser popping each time you execute the test. Or you just don't have privilege of having a browser display like in UNIX based system running your CI and not having any display. These are the times when you would find it right to execute your tests in headless browser mode.

What we need -
  • Xvfb: X virtual frame buffer is X11 server which does graphical operation in memory, hence no output is displayed. Wikipedia has more on it.
  • Firefox: World famous open source browser
  • A simple selenium test: As simple as launching Google in Firefox
First we need to install Xvfb and FF on Ubantu as -

sudo apt-get install Xvfb firefox

Not you can start Xvfb as -

Xvfb :1 -screen 0 1024x768x24 &

From manual of Xvfb -

-screen screennum WxHxD
           This option creates screen screennum and sets  its  width,  height,
           and  depth  to W, H, and D respectively.  By default, only screen 0
           exists and has the dimensions 1280x1024x8.
Now comes the selenium test. You need to guide Firefox so that it executes test in Xvfb started in previous steps.
This could be done by setting System level property for Xvfb as -

String Xport = System.getProperty("", ":1");

and directing Firefox binary to use Xvfb as -

        FirefoxBinary firefoxBinary = new FirefoxBinary();
        firefoxBinary.setEnvironmentProperty("DISPLAY", Xport);
        WebDriver driver = new FirefoxDriver(firefoxBinary, null);

If Firefox is not installed in standard location - /usr/bin/firefox then you can also specify path to Firefox binary as -

        final File firefoxPath = new File(System.getProperty(
                "lmportal.deploy.firefox.path", "/usr/bin/firefox"));
        FirefoxBinary firefoxBinary = new FirefoxBinary(firefoxPath);
        firefoxBinary.setEnvironmentProperty("DISPLAY", Xport);
        WebDriver driver = new FirefoxDriver(firefoxBinary, null);

Whole test looks as -

On execution, FF will be launched in Xvfb and snap shot of google would be saved in your test directory. Since it is headless execution of test, you would not really see any browser popping on your screen.

To execute headless tests in Chrome, start chrome driver as -

ChromeDriverService chromeDriverService = new ChromeDriverService.Builder()
        .usingDriverExecutable(new File("/home/tarun/Downloads/chromedriver"))
        .usingAnyFreePort().withEnvironment(ImmutableMap.of("DISPLAY", ":1")).build();
WebDriver driver = new ChromeDriver(chromeDriverService);

Popular posts from this blog

How can you save resources when instantiaing driver?

I asked on my previous post about what was wrong in instantiating driver on set up method? And here is the solution video on my YouTube channel (After 5 years of gap I finally added new video tutorial :)) The solution described on video tutorial uses following set up - public class BaseClassOnDemandDriverSetup { private WebDriver driver ; @BeforeMethod public void setupTest () { // Any other set up goes here } @AfterMethod public void teardown () { if ( driver != null ) { driver .quit() ; } } public WebDriver getDriver () { if ( driver == null ) { WebDriverManager. chromedriver ().setup() ; driver = new ChromeDriver() ; } return driver ; } }

Security Testing and Selenium

I have come across many articles which talk of carrying out security testing with selenium however I found it very cumbersome to set up such tests. This is what this tutorial is going to make easy for you. It cover. My next Security Testing and Selenium YouTube video covers following - Importance of having security testing on CI What is dynamic application security testing Recommended tools from What is ?   Using    Project setup  <dependency> <groupId> org.zaproxy </groupId> <artifactId> zap-clientapi </artifactId> <version> 1.9.0 </version> </dependency> <dependency> <groupId> org.zaproxy </groupId> <artifactId> zap </artifactId> <version> 2.10.0 </version> </dependency> Start ZAP daemom (headless) mode  ./ -daemon -host -port 8080 -config api.addrs.a

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro