Selenium Grid Cloud Executor

---
name: "Selenium Grid Cloud Executor"
slug: "selenium-grid-cloud-executor"
description: "Distributes browser test suites across Selenium Grid 4 nodes using RemoteWebDriver and the W3C WebDriver protocol. Supports parallel execution on BrowserStack and Sauce Labs with automatic capability negotiation."
github_stars: 34076
verification: "security_reviewed"
source: "https://github.com/SeleniumHQ/selenium"
category: "Browser Automation"
framework: "Codex"
tool_ecosystem:
  github_repo: "seleniumhq/selenium"
  github_stars: 34076
  npm_package: "selenium-webdriver"
  npm_weekly_downloads: 1932148
---

# Selenium Grid Cloud Executor

Distributes browser test suites across Selenium Grid 4 nodes using RemoteWebDriver and the W3C WebDriver protocol. Supports parallel execution on BrowserStack and Sauce Labs with automatic capability negotiation.

## Installation

Use the upstream install or setup path that matches your environment:
- pip install -r py/requirements_lock.txt

Requirements and caveats from upstream:
- As an alternative you can build a [Dev Container](https://containers.dev/) - basically a docker container -
- #### Using Docker Image
- You can also build a Docker image suitable

Basic usage or getting-started notes:
- to make sure this isn't required in the long run.
- Often we wrap Bazel commands with our custom [Rake](http://rake.rubyforge.org/) wrapper. These are run with the ./go command.
- bazel run — builds the target and then executes it.

- Source: https://github.com/SeleniumHQ/selenium
- Extracted from upstream docs: https://raw.githubusercontent.com/SeleniumHQ/selenium/HEAD/README.md

## Source

- [Agent Skill Exchange](https://agentskillexchange.com/skills/selenium-grid-cloud-executor/)