Skip to content

Add documentation to show the alternative use of an environment variable #1950

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.

Sign up for GitHub

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

Merged
merged 4 commits into from
Sep 20, 2024
Merged

Add documentation to show the alternative use of an environment variable #1950

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ee6480a
Add documentation to show the alternative use of an environment variable
aguspe Sep 18, 2024
14b220c
Merge branch 'trunk' into add_env_documentation_rb
harsha509 Sep 19, 2024
ba252cc
Update line length
aguspe Sep 20, 2024
c3616ee
Merge remote-tracking branch 'origin/add_env_documentation_rb' into a…
aguspe Sep 20, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions website_and_docs/content/documentation/selenium_manager.en.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).
18 changes: 18 additions & 0 deletions website_and_docs/content/documentation/selenium_manager.ja.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).
18 changes: 18 additions & 0 deletions website_and_docs/content/documentation/selenium_manager.pt-br.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).
18 changes: 18 additions & 0 deletions website_and_docs/content/documentation/selenium_manager.zh-cn.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).
Loading