---
name: "selenium-grid-test-automation"
description: "Distribute browser automation tasks across a scalable Selenium Grid infrastructure."
metadata:
  author: "SeleniumHQ"
  version: "1.0.0"
  runtime_compatibility:
    - "codex"
    - "claude-code"
    - "cursor"
    - "windsurf"
triggers:
  - "run tests on selenium grid"
  - "configure selenium hub and nodes"
  - "remote webdriver python"
permissions:
  fs_read: true
  fs_write: "workspace"
  shell_exec: false
  net_access: false
---

# Selenium Grid Distributed Node Execution

Configures Selenium Grid (Hub and Nodes): executing browser automation across Chrome, Firefox, and Edge nodes, managing remote WebDriver sessions, and handling dynamic grid scaling in Docker.

## When to Invoke
Invoke this skill whenever you need to:
- run tests on selenium grid
- configure selenium hub and nodes
- remote webdriver python

## Execution SOP & Rules
1. Deploy Selenium Hub and Node containers using docker-compose.
2. Instantiate drivers with webdriver.Remote(command_executor='http://hub:4444/wd/hub', options=options).
3. Always quit drivers in try...finally blocks with driver.quit() to release grid node slots.
4. Set explicit page load timeouts to prevent hung sessions from blocking grid capacity.

## Verification Checklist
- Run local linting, syntax validation, and type-checks before reporting completion.
- Ensure all created or modified files adhere to workspace boundaries and avoid uncommitted secrets.
- Verify tests or build commands exit cleanly with return code 0.