playwright-bdd

What playwright-bdd is

playwright-bdd converts BDD .feature files into native Playwright tests, allowing readable scenarios to become executable tests. Its documented workflow is to generate tests with `npx bddgen` and then run `npx playwright test`. Configuration uses `defineBddConfig()` in a Playwright config file, which returns the output test directory.

Generated tests can use Playwright features such as parallel execution, sharding, fixtures, reports, screenshots, videos and traces. The project also lists advanced tagging, step decorators, scoped step definitions, AI step exporting and reusable step functions. It is an open-source package under the MIT license, which the README says permits commercial use, modification and sharing. The package requires Node.js 20 or later and declares `@playwright/test` version 1.53 or later as a peer dependency. The project directs users to GitHub issues and Playwright-BDD Discord for bug reports, feature proposals and feedback. GitHub reports that the repository has no SECURITY.md policy and no published security advisories.

Who it suits

playwright-bdd suits teams and AI agents that want to define behavior in readable BDD scenarios and verify generated code. It is for users working with Playwright who can meet its Node.js and peer-dependency requirements.

Getting started

1. Open the project website on GitHub.
2. Use Node.js version 20 or later and `@playwright/test` version 1.53 or later.
3. Configure playwright-bdd in a Playwright config file with `defineBddConfig()`.
4. Generate tests with `npx bddgen`.
5. Run the generated tests with `npx playwright test`.
6. Use GitHub issues or Playwright-BDD Discord for reports and feedback.

Verdict

playwright-bdd connects Gherkin-style scenarios with Playwright’s test capabilities through a documented generate-then-run workflow. Check the runtime requirements and the repository’s stated security-policy status before adopting it.