Closed looshi closed 9 years ago
Can you try using http://localhost:4444/wd/hub
as the --webdriver
parameter for Gagarin?
@looshi I was expecting the same problems - except the error messages - when I forgot to use /wd/hub
suffix. BTW, I've just realized that if you don't try start your selenium instance with -role hub
option you can get away with using the second selenium process.
@apendua forgot to mention I was also using -V verbose mode, so got the error in the Gagarin console output. maybe that's the discrepancy in our experience. I will give your suggestion a try tomorrow. thanks!
@looshi I double checked and it seems that everything works fine when using the /wd/hub
suffix. Except that it's pretty important to have an adequate selenium version, e.g. for FF 36, selenium 2.45
is required. Anyway, the problem you've described shows that we still need better documentation on this one.
I did have this setup working a couple of weeks ago, but no longer works.
mac os 10.9.5 firefox 33.0.1 selenium-server-standalone-2.43.0
steps to replicate :
expected results : firefox driver launches and the client tests execute
actual results : firefox driver does not launch and client tests all fail with the following error
Error: [init({})] The environment you requested was unavailable.
the hub shows this exception :