selenium

Selenium browser automation framework. Use for web testing.

7 stars

Best use case

selenium is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Selenium browser automation framework. Use for web testing.

Teams using selenium 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

$curl -o ~/.claude/skills/selenium/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/testing/selenium/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/selenium/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How selenium Compares

Feature / AgentseleniumStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Selenium browser automation framework. Use for web 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

Selenium is an umbrella project for a range of tools and libraries that enable and support the automation of web browsers. It is the grandfather of browser automation and defined the W3C WebDriver standard.

## When to Use

- **Legacy/Enterprise**: Vast ecosystems and existing test suites.
- **Obscure Browsers**: Need to test Internet Explorer (IE Mode) or specialized browsers.
- **Grid**: Distributing tests across a massive farm of diverse OS/Browser combinations.

## Quick Start (Java)

```java
WebDriver driver = new ChromeDriver();
driver.get("https://selenium.dev");
WebElement element = driver.findElement(By.id("search"));
element.sendKeys("webdriver");
element.submit();
driver.quit();
```

## Core Concepts

### WebDriver

The API protocol that talks to the specific browser driver (chromedriver, geckodriver) which then controls the browser.

### Selenium Grid

Allows running tests on different machines against different browsers in parallel.

### Page Object Model (POM)

A design pattern where each UI page is a class. Tests interact with the class methods rather than raw elements.

## Best Practices (2025)

**Do**:

- **Use Explicit Waits**: `WebDriverWait(driver).until(ExpectedConditions....)`.
- **Use Headless Mode**: For faster CI execution (`ChromeOptions.addArguments("--headless")`).
- **Migrate to W3C**: Ensure you are using W3C compliant capabilities.

**Don't**:

- **Don't use Thread.sleep**: It slows down tests and is flaky.
- **Don't mix Logic and Tests**: Strictly follow Page Object Model (POM) to keep tests readable.

## References

- [Selenium Documentation](https://www.selenium.dev/)