What problem does it solve? Testing how a UI reacts to API failures, timeouts, empty lists, and malformed payloads is hard to do deterministically against a live backend. This Skill guides the creation of Playwright tests that use page.route network mocks to simulate controlled API outcomes for the Didaxis programs flow, so edge cases are reproducible without depending on backend state. ## Core Features & Use Cases - Deterministic API failure simulation: Mock 500/503 save failures, 401/403 auth errors, 404 missing resources, 3xx redirects, and timeouts via route.abort for the /api/programs endpoints. - Empty and malformed payload coverage: Fulfill GET requests with empty arrays or malformed bodies to verify empty-state rendering and crash guards. - Observe-before-assert discipline: Requires opening the real Programs UI first to capture actual error and empty-state copy, so tests never assert invented strings. - Use Case: A QA engineer needs to verify the Programs page shows an error banner when the save API returns 503. The Skill produces a tagged @api spec that routes POST /api/programs to a 503 fulfillment and asserts the observed UI error through existing page object models. ## Quick Start Write a Playwright test that mocks the programs API to return a 503 on save and asserts the error state shown in the real UI.
