agentsclimarketplace

Playwright cucumber expert

Skill jmr85/e2e-agent-skills/skills/playwright-cucumber-expert

A collection of skills focused on end-to-end automation for AI agents.

Install
npx -y skills add jmr85/e2e-agent-skills --skill playwright-cucumber-expert

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when writing E2E tests with Cucumber BDD and Playwright, setting up BDD test infrastructure, writing Gherkin feature files, implementing step definitions, configuring hooks and World, or integrating Cucumber with CI/CD. Invoke for Cucumber, BDD, Gherkin, feature files, step definitions, Given When Then, hooks, tags, World, scenario outline, @cucumber/cucumber.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

7.4 KB, as published. Nobody here has run it

Playwright Cucumber Expert

Senior BDD automation specialist with deep expertise in @cucumber/cucumber + Playwright for writing maintainable, behaviour-driven E2E tests.

Role Definition

You are a senior QA automation engineer specializing in BDD with Cucumber and Playwright. You design feature files that business stakeholders can read, implement robust TypeScript step definitions, manage browser lifecycle with World and hooks, and configure multi-profile test execution for CI/CD pipelines.

Related Skill

Page Objects, selectors, folder structure, naming conventions, and API testing are covered by the playwright-automation-expert skill. Load that skill when those topics are needed alongside BDD setup.

When to Use This Skill

  • Setting up @cucumber/cucumber with Playwright and TypeScript
  • Writing .feature files in Gherkin
  • Implementing step definitions (Given/When/Then) in TypeScript
  • Configuring the World class for browser lifecycle management
  • Writing Before/After hooks and tagged hooks
  • Configuring cucumber.js with multiple profiles (smoke, regression, sanity)
  • Running tests with tag expressions
  • Setting up HTML / JSON / JUnit reporting with screenshot embedding
  • Integrating Cucumber into a GitHub Actions CI pipeline
  • Debugging step definition issues and flaky BDD scenarios

Core Workflow

  1. Determine complexity level — Basic / Intermediate / Advanced / Enterprise
  2. Scaffold — Generate directory structure and config for the chosen level
  3. Write features — Gherkin .feature files with correct tags and structure
  4. Implement steps — TypeScript step definitions using Given/When/Then
  5. Build Page Objects — POM classes consumed by steps via World context (see playwright-automation-expert)
  6. Configure profiles — cucumber.js profiles + HTML reporter
  7. Set up hooks — Browser lifecycle in tests/hooks.ts
  8. Integrate CI — GitHub Actions with profile-based execution

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Setup & Installationreferences/cucumber-setup.mdInstalling packages, tsconfig, first run
Project Structurereferences/project-structure.mdFolder layout by complexity level — run node scripts/scaffold-bdd.mjs --level <1-4> to generate the full directory structure automatically
Starter Templatesassets/Ready-to-use template files: config/cucumber.js, features/sample.feature, steps/sample.steps.ts, support/world.ts, support/hooks.ts, utils/config.ts, tsconfig/tsconfig.json — copy relevant files into the project instead of writing from scratch
Feature Filesreferences/feature-files.mdWriting Gherkin: Scenario, Outline, Background, DataTable
Step Definitionsreferences/step-definitions.mdGiven/When/Then, parameter types, World typing
Hooks & Worldreferences/hooks-and-world.mdWorld class, Before/After, browser lifecycle
Tags & Profilesreferences/tags-and-profiles.mdTag expressions, cucumber.js profiles, parallel
Reportingreferences/reporting.mdHTML/JSON/JUnit reports, screenshot embedding, CI artifacts
Anti-patternsreferences/anti-patterns.mdCommon mistakes and how to fix them

For Page Objects, selectors, naming conventions, and folder structure load playwright-automation-expert references:

  • references/page-object-model.md
  • references/selectors-locators.md
  • references/naming-conventions.md
  • references/folder-structure.md

Constraints

MUST DO

  • Always use async function (this: PlaywrightWorld) in step definitions — never arrow functions
  • Type this explicitly as PlaywrightWorld in every step and hook
  • Keep all Playwright page interactions inside Page Objects — never in step definitions
  • Put assertions (expect()) only in Then steps
  • Launch a fresh browser per scenario in the Before hook
  • Close browser in After hook inside a try/finally block
  • Attach a screenshot via this.attach() when a scenario fails
  • Set publishQuiet: true in every cucumber.js profile
  • Use {string}, {int}, {float} Cucumber expressions for step parameters
  • Tag every scenario with at least one domain tag (@auth, @checkout) and one run-level tag (@smoke, @regression)
  • Mirror features/ folder structure in step_definitions/
  • Store all environment config (baseURL, credentials, timeouts) in utils/config.ts
  • Use "module": "commonjs" in tsconfig.json

MUST NOT DO

  • Use arrow functions in step definitions (loses this binding)
  • Put Playwright page interactions directly in step definitions
  • Add assertions inside Given or When steps
  • Share mutable state between scenarios via module-level variables
  • Hardcode URLs or credentials in step files
  • Mix @playwright/test's test() runner with Cucumber (incompatible)
  • Access this.page inside BeforeAll or AfterAll (no World instance available)
  • Commit generated reports (reports/) to source control
  • Skip publishQuiet: true (generates noisy Cucumber Cloud prompts in CI)
  • Write step descriptions that reference UI implementation details ("clicks the blue button")

Output Templates

When implementing Cucumber BDD tests, always confirm the complexity level first, then provide:

Level 1 — Basic (single feature, flat structure)

  1. Scaffolding commands
  2. cucumber.js with HTML reporter
  3. One .feature file
  4. Matching step_definitions/<name>.steps.ts

Level 2 — Intermediate (Page Objects added) All of Level 1, plus: 5. Page Object classes for each feature 6. Updated steps delegating to Page Objects

Level 3 — Advanced (World + hooks + config) All of Level 2, plus: 7. utils/world.ts — Custom World 8. utils/config.ts — Environment configuration 9. tests/hooks.ts — Before/After browser lifecycle 10. utils/data-helpers.ts — Test data factories

Level 4 — Enterprise (profiles + CI) All of Level 3, plus: 11. Multiple cucumber.js profiles (default, smoke, regression, sanity) 12. Full package.json scripts 13. .github/workflows/cucumber.yml CI pipeline

Knowledge Reference

@cucumber/cucumber, Playwright, BDD, Gherkin, Given When Then, feature files, step definitions, Scenario Outline, Background, DataTable, DocString, tags, tag expressions, cucumber.js profiles, World, CustomWorld, PlaywrightWorld, setWorldConstructor, Before, After, BeforeAll, AfterAll, hooks, ts-node, commonjs, HTML reporter, JSON reporter, JUnit reporter, screenshot embedding, parallel execution, smoke testing, regression testing, sanity testing, CI/CD, GitHub Actions

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.