Skip to content

docs/selenium_manager: mention about Python now supporting ENV for driver path #2055

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
Nov 12, 2024
Merged

docs/selenium_manager: mention about Python now supporting ENV for driver path #2055

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
729dc42
docs/selenium_manager: mention about Python now supporting ENV for dr…
Delta456 Nov 11, 2024
4417ec5
Merge branch 'trunk' into py_selenium_manager
harsha509 Nov 11, 2024
115bee0
Merge branch 'trunk' into py_selenium_manager
Delta456 Nov 11, 2024
1e0538b
commit as what requested
Delta456 Nov 11, 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
13 changes: 7 additions & 6 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 @@ -337,20 +337,21 @@ sudo apt-get install libatk-bridge2.0-0
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
* `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
* Python

This feature is available in the Selenium Ruby binding starting from version 4.25.0.
This feature is available in the Selenium Ruby and Python binding starting from version 4.25.0 and 4.26.0.

## Building a Custom Selenium Manager
In order to build your own custom Selenium Manager that works in an architecture we don't currently support, you can
Expand Down
13 changes: 7 additions & 6 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 @@ -337,20 +337,21 @@ sudo apt-get install libatk-bridge2.0-0
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
* `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
* Python

This feature is available in the Selenium Ruby binding starting from version 4.25.0.
This feature is available in the Selenium Ruby and Python binding starting from version 4.25.0 and 4.26.0.

## Building a Custom Selenium Manager
In order to build your own custom Selenium Manager that works in an architecture we don't currently support, you can
Expand Down
13 changes: 7 additions & 6 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 @@ -337,20 +337,21 @@ sudo apt-get install libatk-bridge2.0-0
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
* `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
* Python

This feature is available in the Selenium Ruby binding starting from version 4.25.0.
This feature is available in the Selenium Ruby and Python binding starting from version 4.25.0 and 4.26.0.

## Building a Custom Selenium Manager
In order to build your own custom Selenium Manager that works in an architecture we don't currently support, you can
Expand Down
13 changes: 7 additions & 6 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 @@ -337,20 +337,21 @@ sudo apt-get install libatk-bridge2.0-0
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
* `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
* Python

This feature is available in the Selenium Ruby binding starting from version 4.25.0.
This feature is available in the Selenium Ruby and Python binding starting from version 4.25.0 and 4.26.0.

## Building a Custom Selenium Manager
In order to build your own custom Selenium Manager that works in an architecture we don't currently support, you can
Expand Down