af-write-playwright-tests

To generate Playwright tests from Markdown, provide a scenario specification file detailing user workflows. The Skill translates these human-readable steps into executable end-to-end test code automatically.

Yes, you can automate end-to-end testing for multi-page user flows. The Skill generates Playwright tests capable of covering complex, multi-step user journeys directly from your defined scenarios.

To debug existing Playwright E2E test failures, use your scenario specifications to generate targeted automated tests. This Skill helps replicate user workflows to isolate and resolve end-to-end testing issues.

Scenario specifications must be written in Markdown format. The Skill requires these human-readable Markdown files to translate defined user workflows and steps into executable Playwright test code.

Yes, you need to adhere to a defined selector contract. The Skill uses this contract to correctly map Markdown scenario steps to Playwright actions, and optionally utilizes seed data for test preconditions.

The best way to convert user stories into automated tests is documenting the user workflow in a Markdown scenario file. The Skill then translates that specification into executable Playwright end-to-end tests.