Playwright C# E2E

What problem does it solve?

Playwright E2E tests often become brittle, slow, and hard to refactor when they duplicate locators across test files, repeat login flows, hardcode URLs, and lack CI diagnostics; this skill provides a safe, consistent .NET testing pattern that makes changes localized and failures easier to debug.

Core Features & Use Cases

• Page Object Model (POM) for resilience: Encapsulates locators and user-action sequences in Pages/ so tests call intent-based async methods instead of raw page/locator queries.
• Auth-ready fixtures via storage state: Uses StorageStatePath with an authenticated base class so most tests skip the login boundary and run faster.
• CI-optimized reliability: Emphasizes async/await correctness, environment-configurable base URLs, retries/trace on failure, and troubleshooting outputs (trace/screenshot) instead of brittle sleeps.
• Use Case: Converting an existing C# UI test suite into a maintainable structure where each feature gets a dedicated test class and each screen interaction is expressed as a POM method, reducing churn during UI changes.

Quick Start

Run an init step in your project, then ask your coding agent to generate a Playwright C# E2E plan and implement it with Pages, Fixtures, and feature-based Tests that use authenticated storage state.