I don't know how much Firefox 45 and 31.0 are different. But I think it's good idea to use 31.0 for running selenium test, unless we update firefox version in travis ci. (travis runs selenium test with 31.0)
On Wed, Jul 13, 2016 at 11:32 PM Corneau Damien <[email protected]> wrote: > Answering myself. > Don't update to Firefox 47, stay in 45 :) > > On Thu, Jul 14, 2016 at 2:43 PM, Corneau Damien <[email protected]> > wrote: > > > Hi, > > > > Does anybody have a good way to run Selenium tests from command line? > > There isn't much documentation about it, and I can't get it to run > anymore. > > > > I tried both: > > > > *TEST_SELENIUM="true" mvn package -DfailIfNoTests=false -pl > > 'zeppelin-interpreter,zeppelin-zengine,zeppelin-server' > > -Dtest=ParagraphActionsIT* > > (Next to running Zeppelin) > > > > and > > > > *PATH=~/Applications/Firefox.app/Contents/MacOS/:$PATH CI="true" mvn > > verify -Pspark-1.6 -Phadoop-2.3 -Ppyspark -B -pl > > > "zeppelin-interpreter,zeppelin-zengine,zeppelin-server,zeppelin-display,spark-dependencies,spark" > > -Dtest="org.apache.zeppelin.AbstractFunctionalSuite" > -DfailIfNoTests=false* > > > > (Just like CI) > > But no luck. > > > > When trying to fix tests, it can take a lot of trials, and making a > commit > > and waiting for CI isn't an option. > > >
