Selenium Java E2E

What problem does it solve?

End-to-end UI tests often become flaky, slow, and hard to maintain when they use raw selectors, fixed sleeps, duplicated driver setup, and inconsistent teardown.

Core Features & Use Cases

• Page Object Model enforcement: Centralizes locators and user flows into Page Objects (POMs) that extend a shared BasePage, while tests call high-level POM methods instead of using findElement/By directly.
• Explicit waits everywhere: Uses WebDriverWait with ExpectedConditions for robust synchronization, avoiding Thread.sleep to reduce flakiness.
• Consistent driver lifecycle: Creates browsers through a single DriverFactory and reliably shuts them down with driver.quit() in @AfterEach.
• Failure debugging via screenshots: Captures screenshots on test failure using a JUnit5 TestWatcher extension for CI visibility.

Quick Start

Tell your agent to scaffold Selenium Java E2E tests using the required folder structure, implementing BasePage explicit waits, a shared DriverFactory, and JUnit5 lifecycle with screenshot capture on failure.