From ee6480a2f86f2726fa459c3af2918d8f3380935b Mon Sep 17 00:00:00 2001 From: aguspe Date: Wed, 18 Sep 2024 18:41:02 +0200 Subject: [PATCH 1/2] Add documentation to show the alternative use of an environment variable --- .../documentation/selenium_manager.en.md | 18 ++++++++++++++++++ .../documentation/selenium_manager.ja.md | 18 ++++++++++++++++++ .../documentation/selenium_manager.pt-br.md | 18 ++++++++++++++++++ .../documentation/selenium_manager.zh-cn.md | 18 ++++++++++++++++++ 4 files changed, 72 insertions(+) diff --git a/website_and_docs/content/documentation/selenium_manager.en.md b/website_and_docs/content/documentation/selenium_manager.en.md index c95ba868cf0b..4f273a506bf8 100644 --- a/website_and_docs/content/documentation/selenium_manager.en.md +++ b/website_and_docs/content/documentation/selenium_manager.en.md @@ -326,5 +326,23 @@ In this case, the library to be installed is the following: sudo apt-get install libatk-bridge2.0-0 ``` +### Using an environment variable for the driver path +It's possible to use an environment variable to specify the driver path without using Selenium Manager. +The following environment variables are supported: + +* SE_CHROMEDRIVER +* SE_EDGEDRIVER +* SE_GECKODRIVER +* SE_IEDRIVER +* SE_SAFARIDRIVER + +For example, to specify the path to the chromedriver, you can set the `SE_CHROMEDRIVER` environment variable to the path of the chromedriver executable. +The following bindings allow you to specify the driver path using an environment variable: + +* Ruby +* Java + +This feature is available in the Selenium Ruby binding starting from version 4.25.0. + ## Roadmap You can trace the work in progress in the [Selenium Manager project dashboard](https://github.com/orgs/SeleniumHQ/projects/5). Moreover, you can check the new features shipped with each Selenium Manager release in its [changelog file](https://github.com/SeleniumHQ/selenium/blob/trunk/rust/CHANGELOG.md). diff --git a/website_and_docs/content/documentation/selenium_manager.ja.md b/website_and_docs/content/documentation/selenium_manager.ja.md index c95ba868cf0b..4f273a506bf8 100644 --- a/website_and_docs/content/documentation/selenium_manager.ja.md +++ b/website_and_docs/content/documentation/selenium_manager.ja.md @@ -326,5 +326,23 @@ In this case, the library to be installed is the following: sudo apt-get install libatk-bridge2.0-0 ``` +### Using an environment variable for the driver path +It's possible to use an environment variable to specify the driver path without using Selenium Manager. +The following environment variables are supported: + +* SE_CHROMEDRIVER +* SE_EDGEDRIVER +* SE_GECKODRIVER +* SE_IEDRIVER +* SE_SAFARIDRIVER + +For example, to specify the path to the chromedriver, you can set the `SE_CHROMEDRIVER` environment variable to the path of the chromedriver executable. +The following bindings allow you to specify the driver path using an environment variable: + +* Ruby +* Java + +This feature is available in the Selenium Ruby binding starting from version 4.25.0. + ## Roadmap You can trace the work in progress in the [Selenium Manager project dashboard](https://github.com/orgs/SeleniumHQ/projects/5). Moreover, you can check the new features shipped with each Selenium Manager release in its [changelog file](https://github.com/SeleniumHQ/selenium/blob/trunk/rust/CHANGELOG.md). diff --git a/website_and_docs/content/documentation/selenium_manager.pt-br.md b/website_and_docs/content/documentation/selenium_manager.pt-br.md index c95ba868cf0b..4f273a506bf8 100644 --- a/website_and_docs/content/documentation/selenium_manager.pt-br.md +++ b/website_and_docs/content/documentation/selenium_manager.pt-br.md @@ -326,5 +326,23 @@ In this case, the library to be installed is the following: sudo apt-get install libatk-bridge2.0-0 ``` +### Using an environment variable for the driver path +It's possible to use an environment variable to specify the driver path without using Selenium Manager. +The following environment variables are supported: + +* SE_CHROMEDRIVER +* SE_EDGEDRIVER +* SE_GECKODRIVER +* SE_IEDRIVER +* SE_SAFARIDRIVER + +For example, to specify the path to the chromedriver, you can set the `SE_CHROMEDRIVER` environment variable to the path of the chromedriver executable. +The following bindings allow you to specify the driver path using an environment variable: + +* Ruby +* Java + +This feature is available in the Selenium Ruby binding starting from version 4.25.0. + ## Roadmap You can trace the work in progress in the [Selenium Manager project dashboard](https://github.com/orgs/SeleniumHQ/projects/5). Moreover, you can check the new features shipped with each Selenium Manager release in its [changelog file](https://github.com/SeleniumHQ/selenium/blob/trunk/rust/CHANGELOG.md). diff --git a/website_and_docs/content/documentation/selenium_manager.zh-cn.md b/website_and_docs/content/documentation/selenium_manager.zh-cn.md index c95ba868cf0b..4f273a506bf8 100644 --- a/website_and_docs/content/documentation/selenium_manager.zh-cn.md +++ b/website_and_docs/content/documentation/selenium_manager.zh-cn.md @@ -326,5 +326,23 @@ In this case, the library to be installed is the following: sudo apt-get install libatk-bridge2.0-0 ``` +### Using an environment variable for the driver path +It's possible to use an environment variable to specify the driver path without using Selenium Manager. +The following environment variables are supported: + +* SE_CHROMEDRIVER +* SE_EDGEDRIVER +* SE_GECKODRIVER +* SE_IEDRIVER +* SE_SAFARIDRIVER + +For example, to specify the path to the chromedriver, you can set the `SE_CHROMEDRIVER` environment variable to the path of the chromedriver executable. +The following bindings allow you to specify the driver path using an environment variable: + +* Ruby +* Java + +This feature is available in the Selenium Ruby binding starting from version 4.25.0. + ## Roadmap You can trace the work in progress in the [Selenium Manager project dashboard](https://github.com/orgs/SeleniumHQ/projects/5). Moreover, you can check the new features shipped with each Selenium Manager release in its [changelog file](https://github.com/SeleniumHQ/selenium/blob/trunk/rust/CHANGELOG.md). From ba252cc14031f7f908bbe0f66daa1b62097c3857 Mon Sep 17 00:00:00 2001 From: aguspe Date: Fri, 20 Sep 2024 09:51:42 +0200 Subject: [PATCH 2/2] Update line length --- website_and_docs/content/documentation/selenium_manager.en.md | 3 ++- website_and_docs/content/documentation/selenium_manager.ja.md | 3 ++- .../content/documentation/selenium_manager.pt-br.md | 3 ++- .../content/documentation/selenium_manager.zh-cn.md | 3 ++- 4 files changed, 8 insertions(+), 4 deletions(-) diff --git a/website_and_docs/content/documentation/selenium_manager.en.md b/website_and_docs/content/documentation/selenium_manager.en.md index 4f273a506bf8..86dea97d1806 100644 --- a/website_and_docs/content/documentation/selenium_manager.en.md +++ b/website_and_docs/content/documentation/selenium_manager.en.md @@ -336,7 +336,8 @@ The following environment variables are supported: * SE_IEDRIVER * SE_SAFARIDRIVER -For example, to specify the path to the chromedriver, you can set the `SE_CHROMEDRIVER` environment variable to the path of the chromedriver executable. +For example, to specify the path to the chromedriver, +you can set the `SE_CHROMEDRIVER` environment variable to the path of the chromedriver executable. The following bindings allow you to specify the driver path using an environment variable: * Ruby diff --git a/website_and_docs/content/documentation/selenium_manager.ja.md b/website_and_docs/content/documentation/selenium_manager.ja.md index 4f273a506bf8..463b984231e1 100644 --- a/website_and_docs/content/documentation/selenium_manager.ja.md +++ b/website_and_docs/content/documentation/selenium_manager.ja.md @@ -336,7 +336,8 @@ The following environment variables are supported: * SE_IEDRIVER * SE_SAFARIDRIVER -For example, to specify the path to the chromedriver, you can set the `SE_CHROMEDRIVER` environment variable to the path of the chromedriver executable. +For example, to specify the path to the chromedriver, +you can set the `SE_CHROMEDRIVER` environment variable to the path of the chromedriver executable. The following bindings allow you to specify the driver path using an environment variable: * Ruby diff --git a/website_and_docs/content/documentation/selenium_manager.pt-br.md b/website_and_docs/content/documentation/selenium_manager.pt-br.md index 4f273a506bf8..463b984231e1 100644 --- a/website_and_docs/content/documentation/selenium_manager.pt-br.md +++ b/website_and_docs/content/documentation/selenium_manager.pt-br.md @@ -336,7 +336,8 @@ The following environment variables are supported: * SE_IEDRIVER * SE_SAFARIDRIVER -For example, to specify the path to the chromedriver, you can set the `SE_CHROMEDRIVER` environment variable to the path of the chromedriver executable. +For example, to specify the path to the chromedriver, +you can set the `SE_CHROMEDRIVER` environment variable to the path of the chromedriver executable. The following bindings allow you to specify the driver path using an environment variable: * Ruby diff --git a/website_and_docs/content/documentation/selenium_manager.zh-cn.md b/website_and_docs/content/documentation/selenium_manager.zh-cn.md index 4f273a506bf8..463b984231e1 100644 --- a/website_and_docs/content/documentation/selenium_manager.zh-cn.md +++ b/website_and_docs/content/documentation/selenium_manager.zh-cn.md @@ -336,7 +336,8 @@ The following environment variables are supported: * SE_IEDRIVER * SE_SAFARIDRIVER -For example, to specify the path to the chromedriver, you can set the `SE_CHROMEDRIVER` environment variable to the path of the chromedriver executable. +For example, to specify the path to the chromedriver, +you can set the `SE_CHROMEDRIVER` environment variable to the path of the chromedriver executable. The following bindings allow you to specify the driver path using an environment variable: * Ruby