Selenium WebDriver
Selenium WebDriver expertise for cross-browser automation and legacy system testing
Best use case
Selenium WebDriver is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Selenium WebDriver expertise for cross-browser automation and legacy system testing
Teams using Selenium WebDriver should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/selenium-webdriver/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Selenium WebDriver Compares
| Feature / Agent | Selenium WebDriver | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Selenium WebDriver expertise for cross-browser automation and legacy system testing
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Selenium WebDriver Skill
## Overview
This skill provides expert-level capabilities for Selenium WebDriver-based automation, enabling cross-browser testing, grid configuration, and integration with mobile testing through Appium.
## Capabilities
### WebDriver Management
- WebDriver initialization and configuration
- Browser driver management (ChromeDriver, GeckoDriver, etc.)
- Session handling and cleanup
### Cross-Browser Testing
- Chrome, Firefox, Safari, Edge support
- Handle browser-specific quirks and capabilities
- Configure browser options and preferences
### Grid Configuration
- Selenium Grid setup for parallel execution
- Node registration and management
- Docker-based grid configuration
### Element Interaction
- Handle dynamic waits and element location strategies
- Implement robust element locators
- Handle iframes, windows, and alerts
### Page Object Model
- Generate Page Object Model patterns
- Implement reusable page components
- Create fluent APIs for test readability
### Mobile Integration
- Mobile browser testing configuration
- Appium integration for native apps
## Target Processes
- `e2e-test-suite.js` - Full E2E test suite implementation
- `cross-browser-testing.js` - Cross-browser compatibility testing
- `mobile-testing.js` - Mobile web testing
## Dependencies
- `selenium-webdriver` - WebDriver client
- Browser-specific drivers (chromedriver, geckodriver)
- Java (for Selenium Grid)
## Usage Example
```javascript
{
kind: 'skill',
skill: {
name: 'selenium-webdriver',
context: {
action: 'execute-tests',
browsers: ['chrome', 'firefox', 'edge'],
gridUrl: 'http://localhost:4444/wd/hub',
parallel: true
}
}
}
```
## Configuration
The skill supports both local WebDriver execution and remote Selenium Grid connections.Related Skills
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.
plan
Plan a Babysitter workflow without executing the run.
observe
Observe, inspect, or monitor a Babysitter run.
model
Inspect or change Babysitter model-routing policy by phase.
issue
Run an issue-centric Babysitter workflow.