-
-
Notifications
You must be signed in to change notification settings - Fork 523
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
Property webdriver.firefox.profile is ignored for gecko driver #885
Comments
The same property is still passed to the Firefox capabilities when the gecko driver is setup. This could be a geckodriver bug, e.g. SeleniumHQ/selenium#2645 |
Could you check if you can do this with raw Selenium? I suspect this is a Geckodriver bug. |
Sorry for out of topic comment. But I am using Serenity with Cucumber, how can I customize Firefox driver in source code? And how to disable gecko debug log ? I am using Serenity 1.5.3 and my current class as below Thanks |
You can use a provided driver (http://thucydides.info/docs/serenity-staging/#_custom_webdriver_implementations) |
Closing due to lack of activity. |
I am a using a custom firefox profile below is my code . |
This is not a defect but a question - could you please post it on https://serenity-bdd.rocket.chat or on stackoverflow instead? |
I have custom firefox profile for special needs. Previously (with Serenity v. 1.1) I set property "webdriver.firefox.profile" in serenity.properties file, and firefox browser was started with this defined profile.
Today I updated Serenity to latest released version (1.5.3), also I set new firefox ESR (v 52.3.0) and latest gecko driver (v0.18.0).
The problem is that currently firefox with gecko driver is not using custom profile, which indicated in property "webdriver.firefox.profile" in serenity.properties file, instead it uses "firefox_profile=org.openqa.selenium.firefox.FirefoxProfile@aa10649}" (as it shown in the log).
Which property I need to set to use custom profile with gecko driver, or it is a bug?
The text was updated successfully, but these errors were encountered: