-
-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[🚀 Feature]: Allow to configure Selenium Manager from java #13857
Comments
@kool79, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
Seems that 2nd solution will not work, because in current implementation of Selenium Manager the location of |
This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs. |
Feature and motivation
Currently, the Java bindings do not allow to directly change the Selenium Manager configuration .
The only way to manage this configuration is to define environment variables at OS level (windows) or to use a configuration file.
Both approaches require initial manual configuration on every new machine/os. It requires to write/read additional guides, to execute additional steps by users, who need to execute tests locally (example: manual qa team)
The one of the solutions is to use Java's systems properties and pass them as environment variables into Selenium Manager process (only those, which have prefix 'SE_'
Anther solution is to find a way to pass a path to the custom configuration file (se-config.toml)
Usage example
For our project we want to make things simple: All required configuration should be initialized automatically by the framework code, without additional actions on the part of an inexperienced user who needs to run tests locally.
This avoids potential problems with incorrect configurations, as well as avoiding additional infrastructure maintenance steps (which basically is the main purpose of this library).
P.S>
The properties, which we require to configure:
--driver-mirror-url, --browser-mirror-url (to our local mirrors)
--force-browser-download to use CfT instead of local version (when versions are the same)
--ttl (1h is too little for our case - we want to avoid version switch when use qualifiers like 'stable'). Going to use this key with:
--cache-path : to have local project cache (for stable browser version during --ttl)
The text was updated successfully, but these errors were encountered: