"session not created exception" with selenium standalone #27
Comments
|
I could never get operadriver v0.2.2 to work with Opera browsers versions later than Opera 32. Chromium releases new chromedrivers that match with the proper Chrome browser version. You can see the Opera -> Chromium version here I was able to get later chromedrivers to work with newer Opera browsers and just rename the binary accordingly. Of course, I'm not using it in a hub with node configuration so not exactly sure how to tell you to configure your capabilities. I am launching the chromedriver and then connecting to it while specifying the Opera browser binary path. Maybe this helps, maybe not. |
|
Doing that would prevent me from having both Opera and Chrome running in the same selenium node, and it feels like a huge hack. I'd prefer Opera to fix their driver, or at least release the source so someone else can. |
|
I don't see how it would prevent you from having both Opera and Chrome on the same node ... I was suggesting that you use the proper chromedriver binary in place of the operadriver binary which may alleviate this problem on getting a session with Opera - you can even rename it if it makes you feel better... Yes, you have to use ChromeOptions. It is a hack, but about the only option that works since technically Opera is Chromium. operadriver v0.2.2 will not launch later versions of Opera. We haven't seen anything from Opera on this in about a couple of years, so I wouldn't expect to - hopefully I'm wrong. Good luck! |
|
Maybe I misunderstood. I'll give it a try. |
|
So, did it work? |
|
Luke, thank you for getting back. I tried as you pointed out above and in #28, however Opera immediately quits after being launched in my case (Mac, current Opera, Selenium 2.53.1). That's why I wanted to make sure, that this "hack" still works. I'll investigate this further as soon as I have some more spare time. Probably it was just a mistake on my side. Good to know that it should still work as you described! |
|
I just verified on Mac 10.12, Opera 41. Here's the logic and setup:
I launch the ChromeDriver as the server separately since I use RemoteWebDriver: Then I use ChromeOptions for the client, set the profile and binary for Opera and launch: capabilities = DesiredCapabilities.opera();
ChromeOptions options = new ChromeOptions();
options.addArguments("user-data-dir=/path/to/profile/if/needed");
options.setBinary('/Applications/Opera.app/Contents/MacOS/Opera');
capabilities.setCapability(ChromeOptions.CAPABILITY, options);
driver = new RemoteWebDriver(new URL("http://127.0.0.1:9515"),capabilities); |
|
Awesome! Works perfectly! Thank you! |
|
So, in a nutshell, OperaDriver will never actually support Opera? We will forever be hacking ChromeDriver into running Opera instead? |
|
There's a comment somewhere on one of these issues where someone at Opera
said that whoever was working on it quit and that someone else would be
maintaining it eventually.... but it is what it is until then, yeah.
…On Thu, Dec 15, 2016 at 1:06 PM, Joey Parrish ***@***.***> wrote:
So, in a nutshell, OperaDriver will never actually support Opera? We will
forever be hacking ChromeDriver into running Opera instead?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAzJ8vTr_NCmjr9Ec1HyShcDJuAEFZBcks5rIZ3LgaJpZM4KivrV>
.
|
|
In the new release, v2.27, I still can't run Opera in Selenium with OperaDriver. I seem to be able to get something to happen without lying and calling it Chrome, but it still isn't working. We've gone from "session not created" to "no such session" / "Opera failed to start". Log from the selenium node: Selenium node config: {
"capabilities": [
{
"browserName": "operablink",
"maxInstances": 2,
"seleniumProtocol": "WebDriver"
}
],
"proxy": "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
"timeout": 30,
"browserTimeout": 1200,
"maxSession": 4,
"port": scrubbed,
"host": "scrubbed",
"register": true,
"registerCycle": 5000,
"hubPort": scrubbed,
"hubHost": "scrubbed"
} |
and others
I get this error trying to start Opera on Mac using selenium:
Opera starts, then closes immediately.
I'm using v0.2.2 of operachromium driver, but due to #10, the above output shows v0.2.0.
Other browsers run fine. My selenium node config is this:
{ "capabilities": [ { "browserName": "firefox", "maxInstances": 1, "seleniumProtocol": "WebDriver" }, { "browserName": "operablink", "maxInstances": 1, "seleniumProtocol": "WebDriver", }, { "browserName": "safari", "maxInstances": 5, "seleniumProtocol": "WebDriver" } ], "maxSession": 4, "port": 5555, "host": "localhost", "register": true, "registerCycle": 5000, "hubPort": 4444, "hubHost": "localhost" }The text was updated successfully, but these errors were encountered: