{"id":2946,"date":"2015-06-14T11:51:10","date_gmt":"2015-06-14T15:51:10","guid":{"rendered":"http:\/\/qxf2.com\/blog\/?p=2946"},"modified":"2024-10-15T16:14:15","modified_gmt":"2024-10-15T20:14:15","slug":"xvfb-plugin-for-jenkins-selenium","status":"publish","type":"post","link":"https:\/\/qxf2.com\/blog\/xvfb-plugin-for-jenkins-selenium\/","title":{"rendered":"Xvfb plugin for Jenkins"},"content":{"rendered":"

Problem:<\/strong> Error while running Selenium tests via Jenkins on a Ubuntu machine.
\n<\/p>\n

\nWebDriverException(“The browser appears to have exited ”
\nselenium.common.exceptions.WebDriverException: Message: The browser appears to have exited before we could connect. If you specified a log_file in the FirefoxBinary constructor, check it for details.\n<\/div>\n

\"Error\"<\/a>
\n<\/p>\n

\n

Why this post?<\/h3>\n

We faced this issue when we were trying to run our Selenium tests using Jenkins on an Ubuntu system. The same tests were working fine when we ran it through the terminal. We figured out that this was probably because Jenkins user did not have access to the appropriate display. <\/p>\n

We solved the issue at first by making changes to the Jenkins start script. You can refer to this link<\/a> for details. Then the client<\/a> suggested (thanks, Prashanth!) using Xvfb<\/a>. In rest of the post we will explain in detail how we solved this issue using Xvfb.<\/p>\n

\n

1. Xvfb installation:<\/strong>
\nXvfb or X virtual framebuffer is a display server implementing the X11 display server protocol. In contrast to other display servers, Xvfb performs all graphical operations in memory without showing any screen output.
\nMake sure you have Xvfb installed in your Ubuntu system if not Install xvfb in ubuntu using below code<\/p>\n

sudo apt-get install xvfb<\/code><\/p>\n

\n

2. Install Xvfb Plugin for Jenkins:<\/strong><\/p>\n

Xvfb Plugin<\/a> for jenkins lets you control Xvfb virtual frame buffer X11 server with each build. It starts Xvfb before the build starts, and stops it with the build.
\n\"Xvfb<\/a><\/p>\n

\n

3. Configure Jenkins:<\/strong>
\nStart by going to Manage Jenkins \/ Configure System and setup your Xvfb installation. You need to give it a arbitrary name like default Xvfb and directory in which the Xvfb executable is located. Eg:\/usr\/bin.<\/p>\n

\"Jenkins<\/a><\/p>\n

\n

4. Project Configuration:<\/strong>
\nOn the job configuration page, enable the “Start Xvfb before the build, and shut it down after.” under the Build Environment. In case need you can customize defaults by clicking on Advanced… button.<\/p>\n

\"Project<\/a><\/p>\n

\n

5. Re-running the test:<\/strong>
\nAfter making the above changes the test ran fine. Note that the plugin starts Xvfb before the build starts, and stops it with the build
\n\"Rerun<\/a><\/p>\n

\n

Well, that was cool. As always, we are happy to answer any questions you may have.<\/p>\n

Note: <\/strong>We think you would be interested in our open-sourced Selenium + Python test automation framework<\/a> based on the page object pattern.<\/p>\n

Qxf2 provides QA for startups – hire us!<\/h3>\n

Qxf2 is the home of the technical tester. We are early-adopters of tooling and techniques in the QA space. Contact us to work with the experts at providing QA for startups<\/a>.<\/p>\n

\n