Its not easy to keep your local machine's Firefox version to match the one used for tests. In that case, it would be better to download the proper Firefox version and use it when running tests, after all we are doing it for Firebug.
On Thu, Jul 14, 2016 at 4:07 PM, Prabhjyot Singh <[email protected]> wrote: > > https://raw.githubusercontent.com/SeleniumHQ/selenium/master/dotnet/CHANGELOG > > v2.51.0 Says, they have added support for firefox 44, and the one we > are using v2.48.2 has officially support for FF31 but works till 45. > > I keep both FF31 to test CI on local box, and FF-latest to do rest of the > stuff. > > > On 14 July 2016 at 12:18, moon soo Lee <[email protected]> wrote: > > > 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. > > > > > > > > > > > > > -- > Thankx and Regards, > > Prabhjyot Singh >
