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!
  • 相关阅读:
    C++编译期间字节序判断
    解决:无法使用前导 .. 在顶级文件夹上退出
    手动脱WinUpack 壳实战
    浅谈cocos2dx(18) 中工厂模式
    手把手带你画一个 时尚仪表盘 Android 自己定义View
    Git实战(二)原理
    <html>
    Ubuntu局域网下利用client联网
    Desugar Scala(17) -- Option和for,以及脑子里发生的事情
    通过Canvas及File API缩放并上传图片完整演示样例
  • 原文地址:https://www.cnblogs.com/feika/p/4206573.html
Copyright © 2011-2022 走看看