{"id":13463351,"url":"https://github.com/seleniumhq/selenium","last_synced_at":"2026-04-06T02:11:07.638Z","repository":{"id":6375788,"uuid":"7613257","full_name":"SeleniumHQ/selenium","owner":"SeleniumHQ","description":"A browser automation framework and ecosystem.","archived":false,"fork":false,"pushed_at":"2025-05-05T08:39:59.000Z","size":2326026,"stargazers_count":32238,"open_issues_count":254,"forks_count":8433,"subscribers_count":1282,"default_branch":"trunk","last_synced_at":"2025-05-05T10:13:24.247Z","etag":null,"topics":["dotnet","java","javascript","python","ruby","rust","selenium","webdriver"],"latest_commit_sha":null,"homepage":"https://selenium.dev","language":"Java","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/SeleniumHQ.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":"AUTHORS","dei":null,"publiccode":null,"codemeta":null,"zenodo":null},"funding":{"open_collective":"selenium"}},"created_at":"2013-01-14T21:40:56.000Z","updated_at":"2025-05-05T10:01:06.000Z","dependencies_parsed_at":"2023-09-23T14:53:10.930Z","dependency_job_id":"a9a47158-75c8-45ec-96e1-368dde8562ab","html_url":"https://github.com/SeleniumHQ/selenium","commit_stats":{"total_commits":32141,"total_committers":878,"mean_commits":36.60706150341686,"dds":0.834354873837155,"last_synced_commit":"0219666ce1bffd30b43efe4d339ee8ca964f3448"},"previous_names":[],"tags_count":245,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/SeleniumHQ%2Fselenium","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/SeleniumHQ%2Fselenium/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/SeleniumHQ%2Fselenium/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/SeleniumHQ%2Fselenium/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/SeleniumHQ","download_url":"https://codeload.github.com/SeleniumHQ/selenium/tar.gz/refs/heads/trunk","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":252478410,"owners_count":21754360,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["dotnet","java","javascript","python","ruby","rust","selenium","webdriver"],"created_at":"2024-07-31T13:00:51.706Z","updated_at":"2026-04-01T18:02:23.945Z","avatar_url":"https://github.com/SeleniumHQ.png","language":"Java","readme":"\u003ch1 align=\"center\"\u003e\n  \u003cbr/\u003e\n  \u003ca href=\"https://selenium.dev\"\u003e\u003cimg src=\"common/images/selenium_logo_mark_green.svg\" alt=\"Selenium\" width=\"100\"\u003e\u003c/a\u003e\n  \u003cbr/\u003e\n  Selenium\n  \u003cbr/\u003e\n\u003c/h1\u003e\n\n\u003ch3 align=\"center\"\u003eAutomates browsers. That's it!\u003c/h3\u003e\n\n\u003cp align=\"center\"\u003e\n  \u003ca href=\"#contributing\"\u003eContributing\u003c/a\u003e •\n  \u003ca href=\"#installing\"\u003eInstalling\u003c/a\u003e •\n  \u003ca href=\"#building\"\u003eBuilding\u003c/a\u003e •\n  \u003ca href=\"#developing\"\u003eDeveloping\u003c/a\u003e •\n  \u003ca href=\"#testing\"\u003eTesting\u003c/a\u003e •\n  \u003ca href=\"#documenting\"\u003eDocumenting\u003c/a\u003e •\n  \u003ca href=\"#releasing\"\u003eReleasing\u003c/a\u003e\n\u003c/p\u003e\n\n\u003cbr\u003e\n\nSelenium is an umbrella project encapsulating a variety of tools and\nlibraries enabling web browser automation. Selenium specifically\nprovides an infrastructure for the [W3C WebDriver specification](https://w3c.github.io/webdriver/)\n— a platform and language-neutral coding interface compatible with all\nmajor web browsers.\n\nThe project is made possible by volunteer contributors who've\ngenerously donated thousands of hours in code development and upkeep.\n\nThis README is for developers interested in contributing to the project.\nFor people looking to get started using Selenium, please check out\nour [User Manual](https://selenium.dev/documentation/) for detailed examples and descriptions, and if you\nget stuck, there are several ways to [Get Help](https://www.selenium.dev/support/).\n\n[![CI](https://github.com/SeleniumHQ/selenium/actions/workflows/ci.yml/badge.svg)](https://github.com/SeleniumHQ/selenium/actions/workflows/ci.yml)\n[![CI - RBE](https://github.com/SeleniumHQ/selenium/actions/workflows/ci-rbe.yml/badge.svg)](https://github.com/SeleniumHQ/selenium/actions/workflows/ci-rbe.yml)\n[![Releases downloads](https://img.shields.io/github/downloads/SeleniumHQ/selenium/total.svg)](https://github.com/SeleniumHQ/selenium/releases)\n\n## Contributing\n\nPlease read [CONTRIBUTING.md](https://github.com/SeleniumHQ/selenium/blob/trunk/CONTRIBUTING.md)\nbefore submitting your pull requests.\n\n## Installing\n\nThese are the requirements to create your own local dev environment to contribute to Selenium.\n\n### All Platforms\n\n* [Bazelisk](https://github.com/bazelbuild/bazelisk), a Bazel wrapper that automatically downloads\n  the version of Bazel specified in `.bazelversion` file and transparently passes through all\n  command-line arguments to the real Bazel binary.\n* Java JDK version 17 or greater (e.g., [Java 17 Temurin](https://adoptium.net/temurin/releases/?version=17))\n  * Set `JAVA_HOME` environment variable to location of Java executable (the JDK not the JRE)\n  * To test this, try running the command `javac`. This command won't exist if you only have the JRE\n  installed. If you're met with a list of command-line options, you're referencing the JDK properly.\n\n### MacOS\n\n  * Xcode including the command-line tools. Install the latest version using: `xcode-select --install`\n  * Rosetta for Apple Silicon Macs. Add `build --host_platform=//:rosetta` to the `.bazelrc.local` file. We are working\n  to make sure this isn't required in the long run.\n\n### Windows\n\nSeveral years ago [Jim Evans](https://www.linkedin.com/in/jimevansmusic/) published a great article on\n[Setting Up a Windows Development Environment for the Selenium .NET Language Bindings](https://jimevansmusic.blogspot.com/2020/04/setting-up-windows-development.html);\nThis article is out of date, but it includes more detailed descriptions and screenshots that some people might find useful.\n\n\u003cdetails\u003e\n\u003csummary\u003eClick to see Current Windows Setup Requirements\u003c/summary\u003e\n\n#### Option 1: Automatic Installation from Scratch\n\nThis script will ensure a complete ready to execute developer environment.\n(nothing is installed or set that is already present unless otherwise prompted)\n\n1. Open Powershell as an Administrator\n2. Execute: `Set-ExecutionPolicy Bypass -Scope Process -Force` to allow running the script in the process\n3. Navigate to the directory you want to clone Selenium in, or the parent directory of an already cloned Selenium repo\n4. Download and execute this script in the powershell terminal: [scripts/dev-environment-setup.ps1]`\n\n#### Option 2: Manual Installation\n\n1. Allow running scripts in Selenium in general:\n    ```\n    Set-ExecutionPolicy -ExecutionPolicy RemoteSigned\n    ```\n2. Enable Developer Mode:\n    ```\n    reg add \"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\AppModelUnlock\" /t REG_DWORD /f /v \"AllowDevelopmentWithoutDevLicense\" /d \"1\"\n    ```\n3. Install [MSYS2](https://www.msys2.org/), which is an alternative shell environment that provides Unix-like commands\n    * Add bin directory to `PATH` environment variable (e.g., `\"C:\\tools\\msys64\\usr\\bin\"`)\n    * Add `bash.exe` location as the `BAZEL_SH` environment variable (e.g., `\"C:\\tools\\msys64\\usr\\bin\\bash.exe\"`)\n4. Install the latest version of [Visual Studio Community](https://visualstudio.microsoft.com/vs/community/)\n    * Use the visual studio installer to modify and add the \"Desktop development with C++\" Workload\n    * Add Visual C++ build tools installation directory location to `BAZEL_VC` environment variable (e.g. `\"C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\VC\"`)\n    * Add Visual C++ Build tools version to `BAZEL_VC_FULL_VERSION` environment variable (this can be discovered from the directory name in `\"$BAZEL_VC\\Tools\\MSVC\\\u003cBAZEL_VC_FULL_VERSION\u003e\"`)\n5. Add support for long file names (bazel has a lot of nested directories that can exceed default limits in Windows)\n    * Enable Long Paths support with these 2 registry commands:\n    ```shell\n    reg add \"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Command Processor\" /t REG_DWORD /f /v \"DisableUNCCheck\" /d \"1\"\n    reg add \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\FileSystem\" /t REG_DWORD /f /v \"LongPathsEnabled\" /d \"1\"\n    ```\n    * Allow Bazel to create short name versions of long file paths: `fsutil 8dot3name set 0`\n    * Set bazel output to `C:/tmp` instead of nested inside project directory:\n        * Create a file `selenium/.bazelrc.windows.local`\n        * Add \"startup --output_user_root=C:/tmp\" to the file\n\n\u003c/details\u003e\n\n### Alternative Dev Environments\n\nIf you want to contribute to the project, but do not want to set up your own local dev environment,\nthere are two alternatives available.\n\n#### Using GitPod\n\nRather than creating your own local dev environment, GitPod provides a ready to use environment for you.\n\n[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/SeleniumHQ/selenium)\n\n#### Using Dev Container\n\nAs an alternative you can build a [Dev Container](https://containers.dev/) - basically a docker container -\nsuitable for building and testing Selenium using the devcontainer.json in the\n[.devcontainer](.devcontainer/devcontainer.json) directory. Supporting IDEs like VS Code or IntelliJ IDEA\nshould point you to how such a container can be created.\n\n#### Using Docker Image\n\nYou can also build a Docker image suitable\nfor building and testing Selenium using the Dockerfile in the\n[dev image](scripts/dev-image/Dockerfile) directory.\n\n## Building\n\nSelenium is built using a common build tool called [Bazel](https://bazel.build/), to\nallow us to easily manage dependency downloads, generate required binaries, build and release packages, and execute tests;\nall in a fast, efficient manner. For a more detailed discussion, read Simon Stewart's article on [Building Selenium](https://www.selenium.dev/blog/2023/building-selenium/)\n\nOften we wrap Bazel commands with our custom [Rake](http://rake.rubyforge.org/) wrapper. These are run with the `./go` command.\n\nThe common Bazel commands are:\n* `bazel build` — evaluates dependencies, compiles source files and generates output files for the specified target.\nIt's used to create executable binaries, libraries, or other artifacts.\n* `bazel run` — builds the target and then executes it.\nIt's typically used for targets that produce executable binaries.\n* `bazel test` — builds and runs the target in a context with additional testing functionality\n* `bazel query` — identifies available targets for the provided path.\n\nEach module that can be built is defined in a `BUILD.bazel` file. To execute the module you refer to it starting with a\n`//`, then include the relative path to the file that defines it, then `:`, then the name of the target.\nFor example, the target to build the Grid is named `executable-grid` and it is\ndefined in the `'selenium/java/src/org/openqa/selenium/grid/BAZEL.build'` file.\nSo to build the grid you would run: `bazel build //java/src/org/openqa/selenium/grid:executable-grid`.\n\nThe Bazel documentation has a [handy guide](https://bazel.build/run/build#specifying-build-targets)\nfor various shortcuts and all the ways to build multiple targets, which Selenium makes frequent use of.\n\nTo build everything for a given language:\n\n```shell\nbazel build //\u003clanguage\u003e/...\n```\n\nTo build just the grid there is an alias name to use (the log will show where the output jar is located):\n\n```shell\nbazel build grid\n```\n\nTo make things more simple, building each of the bindings is available with this `./go` command:\n\n```shell\n./go \u003clanguage\u003e:build\n```\n\n## Developing\n\n### Java\n\n#### IntelliJ\n\nMost of the team uses Intellij for their day-to-day editing. If you're\nworking in IntelliJ, then we highly recommend installing the [Bazel IJ\nplugin](https://plugins.jetbrains.com/plugin/8609-bazel) which is documented on\n[its own site](https://plugins.jetbrains.com/plugin/8609-bazel).\n\nTo use Selenium with the IntelliJ Bazel plugin, import the repository as a Bazel project, and select the project\nview file from the [scripts](scripts) directory. `ij.bazelproject` for Mac/Linux and `ij-win.bazelproject` for Windows.\n\n#### Linting\n\nWe also use Google Java Format for linting, so using the Google Java Formatter Plugin is useful;\nthere are a few steps to get it working, so read their [configuration documentation](https://github.com/google/google-java-format/blob/master/README.md#intellij-jre-config).\nThere is also an auto-formatting script that can be run: `./scripts/format.sh`\n\n#### Local Installation\n\nWhile Selenium is not built with Maven, you can build and install the Selenium pieces\nfor Maven to use locally by deploying to your local maven repository (`~/.m2/repository`), using:\n\n```shell\n./go java:install\n```\n\n#### Updating Dependencies\n\nDependencies are defined in the file [MODULE.bazel](https://github.com/SeleniumHQ/selenium/blob/trunk/MODULE.bazel).\n\nTo update a dependency, modify the version in the `MODULE.bazel` file and run:\n\n```shell\nRULES_JVM_EXTERNAL_REPIN=1 bazel run @maven//:pin\n```\n\nTo automatically update and pin new dependencies, run:\n\n```shell\n./go java:update\n```\n\n### Python\n\n#### Linting and Formatting\n\nWe follow the [PEP8 Style Guide for Python Code](https://peps.python.org/pep-0008) (except we use a 120 character line length).\nThis is checked and enforced with [ruff](https://docs.astral.sh/ruff/), a linting/formatting tool.\nThere is also an auto-formatting script that can be run: `./scripts/format.sh`\n\n#### Local Installation\n\nTo run Python code locally without building/installing the package, you must first install the dependencies:\n\n```shell\npip install -r py/requirements.txt\n```\n\nThen, build the generated files and copy them into your local source tree:\n\n```shell\n./go py:local_dev\n```\n\nAfter that, you can import the selenium package directly from source from the `py` directory.\n\nInstead of running from source, you can build and install the selenium package (wheel) locally:\n\n```shell\n./go py:install\n```\n\nThis will attempt to install into the global Python `site-packages` directory,\nwhich might not be writable. To avoid this, you should create and activate a\n[virtual environment](https://packaging.python.org/en/latest/tutorials/installing-packages/#creating-virtual-environments)\nbefore installing.\n\n\n### Ruby\n\nInstead of using `irb`, you can create an interactive REPL with all gems loaded using: `bazel run //rb:console`\n\nIf you want to debug code, you can do it via [`debug`](https://github.com/ruby/debug) gem:\n\n1. Add `binding.break` to the code where you want the debugger to start.\n2. Run tests with  `ruby_debug` configuration: `bazel test --config ruby_debug \u003ctest\u003e`.\n3. When debugger starts, run the following in a separate terminal to connect to debugger:\n\n```shell\nbazel-selenium/external/bundle/bin/rdbg -A\n```\n\nIf you want to use [RubyMine](https://www.jetbrains.com/ruby/) for development,\nyou can configure it use Bazel artifacts:\n\n1. Open `rb/` as a main project directory.\n2. From the `selenium` (parent) directory, run `./go rb:local_dev` to create up-to-date artifacts.\n3. In \u003ckbd\u003eSettings / Languages \u0026 Frameworks / Ruby SDK and Gems\u003c/kbd\u003e add new \u003ckbd\u003eInterpreter\u003c/kbd\u003e pointing to `../bazel-selenium/external/rules_ruby++ruby+ruby/dist/bin/ruby`.\n4. You should now be able to run and debug any spec. It uses Chrome by default, but you can alter it using environment variables specified in [Ruby Testing](#ruby-2) section below.\n\n### Rust\n\nTo keep `Cargo.Bazel.lock` synchronized with `Cargo.lock`, run:\n\n```shell\nCARGO_BAZEL_REPIN=true bazel run @crates//:all\n```\n\n## Testing\n\nThere are a number of bazel configurations specific for testing.\n\n### Common Options Examples\n\nHere are examples of arguments we make use of in testing the Selenium code:\n* `--pin_browsers=false` - use Selenium Manager to locate browsers/drivers\n* `--headless` - run browsers in headless mode (supported be Chrome, Edge and Firefox)\n* `--flaky_test_attempts 3` - re-run failed tests up to 3 times\n* `--local_test_jobs 1` - control parallelism of tests\n* `--cache_test_results=no`, `-t-` - disable caching of test results and re-runs all of them\n* `--test_output all` - print all output from the tests, not just errors\n* `--test_output streamed` - run all tests one by one and print its output immediately\n* `--test_env FOO=bar` - pass extra environment variable to test process\n* `--run_under=\"xvfb-run -a\"` - prefix to insert before the execution\n\n### Filtering\n\nSelenium tests can be filtered by size:\n* small — typically unit tests where no browser is opened\n* large — typically tests that actually drive a browser\n* medium — tests that are more involved than simple unit tests, but not fully driving a browser\n\nThese can be filtered using the `test_size_filters` argument like this:\n\n```shell\nbazel test //\u003clanguage\u003e/... --test_size_filters=small\n```\n\nTests can also be filtered by tag like:\n\n```shell\nbazel test //\u003clanguage\u003e/... --test_tag_filters=this,-not-this\n```\n\nIf there are multiple `--test_tag_filters`, only the last one is considered,\nso be careful if also using an inherited config\n\n### Java\n\n\u003cdetails\u003e\n\u003csummary\u003eClick to see Java Test Commands\u003c/summary\u003e\n\nTo run unit tests:\n\n```shell\nbazel test //java/... --test_size_filters=small\n```\nTo run integration tests:\n\n```shell\nbazel test //java/... --test_size_filters=medium\n```\nTo run browser tests:\n\n```shell\nbazel test //java/... --test_size_filters=large --test_tag_filters=\u003cbrowser\u003e\n```\n\nTo run a specific test:\n\n```shell\nbazel test //java/test/org/openqa/selenium/chrome:ChromeDriverFunctionalTest\n```\n\n\u003c/details\u003e\n\n### JavaScript\n\n\u003cdetails\u003e\n\u003csummary\u003eClick to see JavaScript Test Commands\u003c/summary\u003e\n\nTo run the tests run:\n\n```shell\nbazel test //javascript/selenium-webdriver:all\n```\n\nYou can use `--test_env` to pass in the browser name as `SELENIUM_BROWSER`.\n\n```shell\nbazel test //javascript/selenium-webdriver:all --test_env=SELENIUM_BROWSER=firefox\n```\n\n\u003c/details\u003e\n\n### Python\n\n\u003cdetails\u003e\n\u003csummary\u003eClick to see Python Test Commands\u003c/summary\u003e\n\nRun unit tests with:\n```shell\nbazel test //py:unit\n```\n\nTo run all tests with a specific browser:\n\n```shell\nbazel test //py:test-\u003cbrowsername\u003e\n```\n\nTo run common tests with a specific browser (include BiDi tests):\n\n```shell\nbazel test //py:test-\u003cbrowsername\u003e-bidi\n```\n\nTo run all Python tests:\n\n```shell\nbazel test //py:all\n```\n\nTo run tests headless:\n```shell\nbazel test //py:test-\u003cbrowsername\u003e --//common:headless=true\n```\n\n\n\u003c/details\u003e\n\n### Ruby\n\n\u003cdetails\u003e\n\u003csummary\u003eClick to see Ruby Test Commands\u003c/summary\u003e\n\nTest targets:\n\n| Command                                                                          | Description                                        |\n| -------------------------------------------------------------------------------- | -------------------------------------------------- |\n| `bazel test //rb/...`                                                            | Run unit, all integration tests and lint           |\n| `bazel test //rb:lint`                                                           | Run RuboCop linter                                 |\n| `bazel test //rb/spec/...`                                                       | Run unit and integration tests for all browsers    |\n| `bazel test //rb/spec/... --test_size_filters small`                             | Run unit tests                                     |\n| `bazel test //rb/spec/unit/...`                                                  | Run unit tests                                     |\n| `bazel test //rb/spec/... --test_size_filters large`                             | Run integration tests for all browsers             |\n| `bazel test //rb/spec/integration/...`                                           | Run integration tests for all browsers             |\n| `bazel test //rb/spec/integration/... --test_tag_filters firefox`                | Run integration tests for local Firefox only       |\n| `bazel test //rb/spec/integration/... --test_tag_filters firefox-remote`         | Run integration tests for remote Firefox only      |\n| `bazel test //rb/spec/integration/... --test_tag_filters firefox,firefox-remote` | Run integration tests for local and remote Firefox |\n\nRuby test targets have the same name as the spec file with `_spec.rb` removed, so you can run them individually.\nIntegration tests targets also have a browser and remote suffix to control which browser to pick and whether to use Grid.\n\n| Test file                                               | Test target                                                      |\n| ------------------------------------------------------- | ---------------------------------------------------------------- |\n| `rb/spec/unit/selenium/webdriver/proxy_spec.rb`         | `//rb/spec/unit/selenium/webdriver:proxy`                        |\n| `rb/spec/integration/selenium/webdriver/driver_spec.rb` | `//rb/spec/integration/selenium/webdriver:driver-chrome`         |\n| `rb/spec/integration/selenium/webdriver/driver_spec.rb` | `//rb/spec/integration/selenium/webdriver:driver-chrome-remote`  |\n| `rb/spec/integration/selenium/webdriver/driver_spec.rb` | `//rb/spec/integration/selenium/webdriver:driver-firefox`        |\n| `rb/spec/integration/selenium/webdriver/driver_spec.rb` | `//rb/spec/integration/selenium/webdriver:driver-firefox-remote` |\n\nSupported browsers:\n\n* `chrome`\n* `edge`\n* `firefox`\n* `firefox-beta`\n* `ie`\n* `safari`\n* `safari-preview`\n\nIn addition to the [Common Options Examples](#common-options-examples), here are some additional Ruby specific ones:\n* `--test_arg \"-eTimeouts\"` - test only specs which name include \"Timeouts\"\n* `--test_arg \"\u003cany other RSpec argument\u003e\"` - pass any extra RSpec arguments (see `bazel run @bundle//bin:rspec -- --help`)\n\nSupported environment variables for use with `--test_env`:\n\n- `WD_SPEC_DRIVER` - the driver to test; either the browser name or 'remote' (gets set by Bazel)\n- `WD_REMOTE_BROWSER` - when `WD_SPEC_DRIVER` is `remote`; the name of the browser to test (gets set by Bazel)\n- `WD_REMOTE_URL` - URL of an already running server to use for remote tests\n- `DOWNLOAD_SERVER` - when `WD_REMOTE_URL` not set; whether to download and use most recently released server version for remote tests\n- `DEBUG` - turns on verbose debugging\n- `HEADLESS` - for chrome, edge and firefox; runs tests in headless mode\n- `DISABLE_BUILD_CHECK` - for chrome and edge; whether to ignore driver and browser version mismatches (allows testing Canary builds)\n- `CHROME_BINARY` - path to test specific Chrome browser\n- `CHROMEDRIVER_BINARY` - path to test specific ChromeDriver\n- `EDGE_BINARY` - path to test specific Edge browser\n- `MSEDGEDRIVER_BINARY` - path to test specific msedgedriver\n- `FIREFOX_BINARY` - path to test specific Firefox browser\n- `GECKODRIVER_BINARY` - path to test specific GeckoDriver\n\nTo run with a specific version of Ruby you can change the version in `rb/.ruby-version` or from command line:\n\n```shell\necho '\u003cX.Y.Z\u003e' \u003e rb/.ruby-version\n```\n\u003c/details\u003e\n\n### .NET\n\n\u003cdetails\u003e\n\u003csummary\u003eClick to see .NET Test Commands\u003c/summary\u003e\n\n.NET tests currently only work with pinned browsers, so make sure to include that.\n\nRun all tests with:\n\n```shell\nbazel test //dotnet/test/common\n```\n\nYou can run specific tests by specifying the class name:\n\n```shell\nbazel test //dotnet/test/common:ElementFindingTests\n```\n\nIf the module supports multiple browsers:\n\n```shell\nbazel test //dotnet/test/common:ElementFindingTests-edge\n```\n\n\u003c/details\u003e\n\n### Rust\n\n\u003cdetails\u003e\n\u003csummary\u003eClick to see Rust Test Commands\u003c/summary\u003e\n\nRust tests are run with:\n\n```shell\nbazel test //rust/...\n```\n\u003c/details\u003e\n\n### Linux\n\n\u003cdetails\u003e\n\u003csummary\u003eClick to see Linux Testing Requirements\u003c/summary\u003e\n\nBy default, Bazel runs these tests in your current X-server UI. If you prefer, you can\nalternatively run them in a virtual or nested X-server.\n\n1. Run the X server `Xvfb :99` or `Xnest :99`\n2. Run a window manager, for example, `DISPLAY=:99 jwm`\n3. Run the tests you are interested in:\n\n```shell\nbazel test --test_env=DISPLAY=:99 //java/... --test_tag_filters=chrome\n```\n\nAn easy way to run tests in a virtual X-server is to use Bazel's `--run_under`\nfunctionality:\n\n```\nbazel test --run_under=\"xvfb-run -a\" //java/...\n```\n\u003c/details\u003e\n\n\n## Documenting\n\nAPI documentation can be found here:\n\n* [C#](https://seleniumhq.github.io/selenium/docs/api/dotnet/)\n* [JavaScript](https://seleniumhq.github.io/selenium/docs/api/javascript/)\n* [Java](https://seleniumhq.github.io/selenium/docs/api/java/index.html)\n* [Python](https://seleniumhq.github.io/selenium/docs/api/py/)\n* [Ruby](https://seleniumhq.github.io/selenium/docs/api/rb/)\n\nTo update API documentation for a specific language: `./go \u003clanguage\u003e:docs`\n\nTo update all documentation: `./go all:docs`\n\n\n## Releasing\n\nThe full process for doing a release can be found in [the wiki](https://github.com/SeleniumHQ/selenium/wiki/Releasing-Selenium)\n\nReleasing is a combination of building and publishing, which often requires coordination of multiple executions\nand additional processing.\nAs discussed in the [Building](#building) section, we use Rake tasks with the `./go` command for these things.\nThese `./go` commands include the `--stamp` argument to provide necessary information about the constructed asset.\n\nYou can build and release everything with:\n\n```shell\n./go all:release\n```\n\nTo build and release a specific language:\n\n```shell\n./go \u003clanguage\u003e:release\n```\n\nIf you have access to the Selenium EngFlow repository, you can have the assets built remotely and downloaded locally using:\n\n```shell\n./go all:release['--config', 'release']\n```\n","funding_links":["https://opencollective.com/selenium"],"categories":["Testing","[Automation Testing](TestingDomains.md/#automation-testing)","1 Data Processing for LLM"],"sub_categories":["Browser testing","1.1 Data Acquisition"],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fseleniumhq%2Fselenium","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fseleniumhq%2Fselenium","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fseleniumhq%2Fselenium/lists"}