Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to properly configure the Selenium Maven Plugin to work with Xvfb to run headless
    primarykey
    data
    text
    <p><em><strong>Background:</em></strong><br> I'm using selenium-server-2.25.0 in conjunction with J-Unit 4 to run through a handful of UI testing scenarios for my GWT app. In my IDE (Netbeans 7.2), I can right-click on my project, choose "Test", and see Firefox windows pop up all over (as they should) with the Selenium tests running as expected. From the command line, I can also run <code>mvn integration-test</code> and see the same.</p> <p><em><strong>Goal:</em></strong><br> I'm trying to get these tests to run headless in an Xvfb display, but I seem to be having trouble getting this to work with Maven. I can manually run <code>export display=:2</code> (:2 being my Xvfb display) beforehand, and then the tests then DO run in the invisible display successfully.</p> <p><em><strong>Issue:</em></strong><br> Nothing seems to change <strong>at all</strong> when I include the full <code>&lt;plugin&gt;</code> entry from <a href="http://mojo.codehaus.org/selenium-maven-plugin/examples/headless-with-xvfb.html">here</a> in my pom.xml and run <code>mvn integration-test</code>. I still see Windows popping up all over and the tests running <strong>not</strong> in the Xvfb display. If I take it out and run again, same results. When I change the phase from <code>pre-integration-test</code> to <code>qwertyasdf</code> however, Maven <strong>does</strong> complain about an invalid lifecycle phase - so I know it's not completely ignoring it, and I am editing the appropriate pom.xml.</p> <p>Thanks!</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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