Selenium C# E2E

What problem does it solve?

Selenium C# end-to-end tests often become flaky, hard to maintain, and tightly coupled to DOM selectors, making refactors risky and slowing development.

Core Features & Use Cases

• Enforces the Page Object Model (POM): centralizes locators and user flows in Pages classes and prevents raw FindElement/By usage in Tests.
• Standardizes driver setup via a DriverFactory: ensures browser options, headless mode, and window sizing live in one place.
• Improves reliability with explicit waits and failure diagnostics: uses explicit WebDriverWait helpers (no Thread.Sleep) and captures screenshots on failure for faster debugging.
• Supports clean test structure for NUnit/xUnit: keeps setup, teardown disposal, and assertions in test orchestration, not in page objects.

Quick Start

Run architect init in your C# test project and then use the installed skill to guide your agent to reorganize tests into Tests/, Pages/, and Fixtures/ with explicit waits and screenshot-on-failure TearDown.