Playwright-BDD

Visit Website

Introduction

Playwright-BDD lets teams write Given/When/Then scenarios in .feature files and run them as real Playwright tests. Instead of running Cucumber with Playwright as a library, it converts feature files into Playwright Test files and wires up the step definitions, so you keep Playwright’s runner, parallelism, fixtures, retries, traces and reporters.

The README now frames BDD as especially useful ‘in the AI era’: scenarios are readable enough for people and coding agents to draft, and executable so they stay aligned with the code. The project provides a skill for AI coding agents and describes a workflow where humans review only feature files.

Steps are defined with createBdd() and can use Playwright fixtures directly, including custom fixtures. It also supports Cucumber-style step definitions and tags.

In the quality loop it sits at the acceptance and end-to-end stage for teams that want BDD without giving up Playwright Test.

The source code is at vitalets/playwright-bdd on GitHub under the MIT licence, with about 830 stars; the most recent commit was on 10 November 2026.

Features

1. Native Playwright tests: Feature files compile to Playwright Test files.
2. Fixtures in steps: Use Playwright fixtures inside step definitions.
3. Tags and filtering: Gherkin tags map to Playwright test filtering.
4. Playwright reporters: HTML report, traces and other reporters work unchanged; Cucumber reports are also supported.
5. AI agent skill: A provided skill helps coding agents write compliant scenarios.

Pros

1. Best of both: Readable Gherkin with Playwright’s speed and tooling.
2. Free to use: Open source under the MIT licence, so the core tool costs nothing to use.
3. Actively maintained: The repository had commits as recent as 10 November 2026.

Cons

1. Generation step: Tests are generated with bddgen before running, which adds a build step.
2. Small project: About 830 GitHub stars and mainly one maintainer.

Usage and Links (Example)

npm i -D @playwright/test playwright-bdd

Feature: Login
  Scenario: User signs in
    Given I am on the login page
    When I sign in as "user@example.com"
    Then I see "Welcome"

npx bddgen && npx playwright test

Resources:

• Playwright-BDD website
• GitHub repository

Pricing

Playwright-BDD is free and open source under the MIT licence.

Recommended for?

1. BDD teams moving to Playwright.
2. Teams writing scenarios with AI agents who want them executable.
3. Not a fit if nobody reads the feature files; plain Playwright tests are simpler.

Conclusion

Playwright-BDD is the cleanest way to combine Gherkin scenarios with the Playwright Test runner, and it is actively maintained.

On CheckOps, Playwright-BDD is filed under the End-to-end & functional stage. Related tools listed here include Playwright, Cucumber, Cypress Cucumber Preprocessor, Serenity/JS, CodeceptJS and Reqnroll. Before choosing, compare them on licence, supported languages and platforms, hosting model, and how well each fits your existing CI pipeline. Facts on this page were checked against the official website, documentation and repository on 11 November 2026; statements the vendor makes about its own product are marked as vendor claims.