Selenium E2E

What problem does it solve?

Selenium-based end-to-end testing often becomes flaky and hard to debug because tests wait incorrectly, duplicate WebDriver setup logic, and scatter brittle selectors throughout spec files; this Skill turns E2E tests into a maintainable Page Object Model workflow with explicit waits and failure screenshots.

Core Features & Use Cases

• Deterministic Page Object Model (POM): Centralizes locators and user actions in tests/e2e/pages, with Page Objects extending BasePage for shared explicit wait helpers, while specs call high-level POM methods instead of raw driver.findElement() or By selectors.
• Explicit waits everywhere: Enforces driver.wait(..., until.*) for element interaction (no implicit waits, no fixed sleeps), improving stability across slow CI environments.
• Robust driver lifecycle and CI debugging: Uses a single createDriver() factory to build WebDriver instances and ensures driver.quit() in afterEach, plus captures screenshots on failure for fast diagnosis.
• Auth and flow coverage: Supports dedicated authentication boundary tests for login/logout, redirects for unauthorized access, and CSRF handling, covering the highest-value regressions in production systems.

Quick Start

Tell your coding agent to restructure your Selenium tests to follow the Selenium E2E skill layout by creating tests/e2e/pages Page Objects that extend BasePage, adding a shared WebDriver factory in tests/e2e/fixtures/create-driver.ts, and updating specs to use POM methods with explicit waits and screenshot-on-failure cleanup.