playwright-cucumber-e2e-steps-generator

To generate Playwright step definitions from Cucumber feature files, you parse the Gherkin scenarios to extract steps and automatically scaffold the corresponding TypeScript step definition functions to bridge features with executable tests.

A Page Object Model generator works with Cucumber and Playwright by parsing feature files and creating reusable TypeScript Page Object classes, structuring interactive selectors and element interactions to separate test logic from page representation.

Yes, you can use Playwright MCP for interactive selector discovery in E2E tests to automatically locate elements during generation, or alternatively supply manual selector inputs when building your Page Object classes and step definitions.

Yes, you need TypeScript to use this Playwright and Cucumber E2E testing setup, as the generator requires a project structure configured with src/ directories to properly scaffold and output the TypeScript step definitions and Page Objects.

The best way to scaffold missing Playwright test implementations is to parse existing Cucumber feature files to identify unimplemented scenarios and automatically generate TypeScript test skeletons with the required step definitions and Page Object structures.