What problem does it solve? Writing browser-driven end-to-end tests for ECommerceApp.Web requires coordinating Playwright, a real Kestrel host, InMemory databases, and the asynchronous Outbox message dispatcher — a setup with several non-obvious pitfalls (such as accidentally creating a second TestServer-backed host) that this Skill encodes as ready-to-use templates and rules. ## Core Features & Use Cases - Test Scaffolding: Generates xUnit test classes using PlaywrightBrowserFixture and PlaywrightWebApplicationFactory with the mandatory StartKestrelHost() pattern. - Async Event Assertions: Uses OutboxDispatchWatcher to assert UI state both before and after an Outbox message is dispatched, covering the "event not yet processed" bug class. - Page Object Model Guidance: Enforces the Scenario → POM → Component composition model, including persona changes via separate BrowserContext instances. - Use Case: You need to verify that a checkout page renders correctly before and after a payment event is processed by the Outbox poller — this Skill produces the full test class with the watcher-based wait and reload assertions. ## Quick Start Ask the assistant to create a Playwright E2E test for a specific page or flow, for example the guest checkout payment flow, and it will scaffold the test class with the correct fixtures and host setup.