browser-workflow-to-playwright

You can convert browser workflow markdown into Playwright e2e tests by processing step-by-step workflow documents, which automatically maps selectors, resolves ambiguities, and outputs structured test blocks ready for CI execution.

Selector mapping integrates a discovery workflow to generate robust locators, resolving ambiguous selectors through user prompts to ensure reliable end-to-end test execution without manual selector debugging.

Yes, you need a Playwright-enabled project with a configured test runner and installed browsers, along with your browser workflow markdown placed at the specified file path to generate the test script.

Yes, the conversion process compares new workflow steps against existing tests to add or update test blocks via diffing, preserving custom code while integrating new automated actions.

Manual steps that cannot be automated are explicitly labeled within the generated Playwright test file, ensuring non-automatable actions are documented while remaining steps execute automatically.

Automating e2e test generation involves translating human-readable markdown workflows into structured Playwright tests with per-step comments, handling selector mapping, and outputting a ready-to-run spec file.