zoukankan      html  css  js  c++  java
  • WebDriver: Getting it to play nicely with Xvfb

    http://www.markhneedham.com/blog/2011/12/15/webdriver-getting-it-to-play-nicely-with-xvfb/


    Thoughts on Software Development

     

    with 2 comments

    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._
    lazy val firefoxDriver: FirefoxDriver = {
      setProperty("webdriver.firefox.bin", "/our/awesome/starting-firefox.sh")
      new FirefoxDriver()
    }

    Our first version of the script looked like this:

    /our/awesome/starting-firefox.sh

    #!/bin/bash
     
    rm -f ~/.mozilla/firefox/*/.parentlock
    rm -rf /var/go/.mozilla
     
     
    XVFB=`which xVfb`
    if [ "$?" -eq 1 ];
    then
        echo "Xvfb not found."
        exit 1
    fi
     
    $XVFB :99 -ac &
     
     
    BROWSER=`which firefox`
    if [ "$?" -eq 1 ];
    then
        echo "Firefox not found."
        exit 1
    fi
     
    export DISPLAY=:99
    $BROWSER &

    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
    Error cannot open display :99

    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
     
    rm -f ~/.mozilla/firefox/*/.parentlock
    rm -rf /var/go/.mozilla
     
    pkill firefox
     
    BROWSER=`which firefox`
    if [ "$?" -eq 1 ];
    then
        echo "Firefox not found."
        exit 1
    fi
     
    export DISPLAY=:99
    $BROWSER &

    It’s a bit hacky but it does the job more deterministically than anything else we’ve tried previously.

    Be Sociable, Share!
  • 相关阅读:
    Java并发Condition接口
    Java并发ReadWriteLock接口
    简述mapreduce的四个对象
    hadoop IO操作
    java 多线程笔记
    java 四种方式读取文件
    InputStream、InputStreamReader、BufferedReader
    java 自动拆箱与装箱(基本数据类型与引用类型)
    java 之equals与"=="的区别
    vmware搭建hadoop集群完整过程笔记
  • 原文地址:https://www.cnblogs.com/feika/p/4206573.html
Copyright © 2011-2022 走看看