Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

desktop.md - are the capabilites string examples not correct? #98

Open
mlipok opened this issue Feb 25, 2022 · 5 comments
Open

desktop.md - are the capabilites string examples not correct? #98

mlipok opened this issue Feb 25, 2022 · 5 comments

Comments

@mlipok
Copy link

mlipok commented Feb 25, 2022

I tried to use capabilites string examples from here:
https://github.com/operasoftware/operachromiumdriver/blob/master/docs/desktop.md

Unfortunately, no luck.

My finall workable versoin is

{
    "capabilities":{
        "alwaysMatch":{
            "goog:chromeOptions":{
                "w3c":true,
                "excludeSwitches":[
                    "enable-automation"
                ],
                "binary":"C:\\Users\\Szef\\AppData\\Local\\Programs\\Opera\\opera.exe"
            }
        }
    }
}

so my question is:
Are the capabilites string examples form desktop.md not correct?

@aleksandr-kotlyar
Copy link
Contributor

@mlipok for selenium 4 its better to use ChromeOptions instead of capabilities
Take a look at new examples i pushed today in PR #106

https://github.com/aleksandr-kotlyar/operachromiumdriver/blob/32ce4b702188c21e2cd1faf0854a47a6a229e4f7/examples/desktop_selenium_4.x.py

@mlipok
Copy link
Author

mlipok commented Mar 12, 2023

@mlipok for selenium 4 its better to use ChromeOptions instead of capabilities

Ok. So I ask if this following document:
https://github.com/operasoftware/operachromiumdriver/blob/master/docs/desktop.md

should be changed accordingly?

@mlipok
Copy link
Author

mlipok commented Mar 12, 2023

Are the capabilites string examples form desktop.md not correct?

It was my question in OP but maybe not well worderd.

@aleksandr-kotlyar
Copy link
Contributor

@mlipok for selenium 4 its better to use ChromeOptions instead of capabilities

Ok. So I ask if this following document: https://github.com/operasoftware/operachromiumdriver/blob/master/docs/desktop.md

should be changed accordingly?

Merged. Should be actual now. ;-)

@mlipok
Copy link
Author

mlipok commented Apr 21, 2023

I had in a mind that using:

capabilities = {
'operaOptions': {
'binary': opera_exe_path
}
}

or
capabilities = {
'operaOptions': {
'debuggerAddress': port # Same port as passed to the Opera.
}
}

failed when I was used it.

I asked/proposed to change to something like this:

"goog:chromeOptions":{
	"w3c":true,
	"excludeSwitches":[
	    "enable-automation"
	],
	"binary":"C:\\Users\\Szef\\AppData\\Local\\Programs\\Opera\\opera.exe"
    }

summary:
specifically 'operaOptions' was wrong in my cases and I had to use `"goog:chromeOptions"

btw.
Of course I can be wrong, becuase I not use Selenium/Python, instead of I use AutoIt and we automate websites with sending HTTP request to running instance of operadriver.exe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants