This still doesn't work but when I did export BROWSER=chrome and it now works. Does BROWSER_LABEL have any effect? Can this be documented somewhere?
On Tue, Mar 18, 2014 at 11:13 AM, Chris McMahon <cmcma...@wikimedia.org> wrote: > > You shouldn't have to start Chromedriver, the framework will do that for > you. > > * Chrome is installed in the normal location > * chromedriver is downloaded and exists in /usr/bin and can be executed > * $ export BROWSER_LABEL=chrome > * bundle exec cucumber features/foo.feature > > should launch Chrome to run foo.feature > > > On Tue, Mar 18, 2014 at 11:07 AM, Jon Robson <jrob...@wikimedia.org> wrote: >> >> No luck.. it still loads Firefox even though binary exists. Any >> further suggestions? >> >> i18nhook x ~/Sites/w/extensions/MobileFrontend $ chromedriver >> Starting ChromeDriver (v2.9.248307) on port 9515 >> >> On Tue, Mar 18, 2014 at 10:50 AM, Chris McMahon >> <christopher.mcma...@gmail.com> wrote: >> > >> > https://code.google.com/p/selenium/wiki/ChromeDriver >> > >> > with ChromeDriver in a directory in your path (probably >> > /user/bin/chromedriver) just set your env var BROWSER_LABEL=chrome and >> > it >> > should Just Work. >> > >> > >> > >> > >> > On Tue, Mar 18, 2014 at 11:35 AM, Jon Robson <jrob...@wikimedia.org> >> > wrote: >> >> >> >> is there any kind of timeline for this? This problem is still >> >> surfacing and is rendering our test infrastructure close to useless.. >> >> Let me know what I can do to help move this along. I currently don't >> >> have the Chrome driver setup. I have a Mac - how do I get the tests >> >> running on Chrome rather than Firefox - is this documented anywhere? >> >> >> >> https://bugzilla.wikimedia.org/show_bug.cgi?id=62614 >> >> https://bugzilla.wikimedia.org/show_bug.cgi?id=62583 >> >> >> >> On Thu, Mar 13, 2014 at 2:16 PM, Chris McMahon >> >> <christopher.mcma...@gmail.com> wrote: >> >> > >> >> > >> >> > >> >> > On Thu, Mar 13, 2014 at 3:06 PM, Arthur Richards >> >> > <aricha...@wikimedia.org> >> >> > wrote: >> >> >> >> >> >> Thanks for bringing this convo to the lists. Chris has mentioned in >> >> >> IRC >> >> >> a >> >> >> few times now ongoing issues with the Chrome driver and if I recall >> >> >> correctly expressed that the QA group was hoping to get them >> >> >> resolved >> >> >> shortly. Any update, Chris? >> >> > >> >> > >> >> > Yes, Zeljko reverted our specified Chrome version back to Sauce's >> >> > recommendations. It's not an ideal situation, but it'll get us >> >> > through >> >> > the >> >> > short term. When Sauce supports v.33 we'll try that. >> >> > >> >> > Also, bugs: https://bugzilla.wikimedia.org/show_bug.cgi?id=62622 >> >> > -Chris >> >> > >> >> > _______________________________________________ >> >> > QA mailing list >> >> > QA@lists.wikimedia.org >> >> > https://lists.wikimedia.org/mailman/listinfo/qa >> >> > >> >> >> >> _______________________________________________ >> >> QA mailing list >> >> QA@lists.wikimedia.org >> >> https://lists.wikimedia.org/mailman/listinfo/qa >> > >> > >> > >> > _______________________________________________ >> > QA mailing list >> > QA@lists.wikimedia.org >> > https://lists.wikimedia.org/mailman/listinfo/qa >> > >> >> _______________________________________________ >> QA mailing list >> QA@lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/qa > > > > _______________________________________________ > QA mailing list > QA@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/qa > _______________________________________________ QA mailing list QA@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/qa
