cucumber-cypress

Write Gherkin scenarios and TypeScript step definitions for Cypress BDD tests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cooldaemon/dotfiles --skill cucumber-cypress
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cucumber-cypress
Source: https://github.com/cooldaemon/dotfiles/tree/main/.claude/skills/cucumber-cypress
Command: npx skills add https://github.com/cooldaemon/dotfiles --skill cucumber-cypress

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @badeball/cypress-cucumber-preprocessor, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of writing and executing Behavior-Driven Development (BDD) tests for web applications using Cypress and Cucumber.

Core Features & Use Cases

  • Gherkin Scenario Implementation: Write tests in a human-readable Gherkin format (.feature files).
  • Cypress Step Definitions: Implement corresponding step definitions in TypeScript (.steps.ts).
  • Use Case: Ensure a consistent and maintainable testing suite by defining application behavior in a clear, collaborative format that bridges the gap between technical and non-technical stakeholders.

Quick Start

Execute the Cypress test suite using the command npx cypress run.

Frequently Asked Questions about cucumber-cypress

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write BDD tests for Cypress using Gherkin scenarios?

Behavior-Driven Development tests for Cypress are written as human-readable Gherkin scenarios in `.feature` files, which are then executed by implementing corresponding TypeScript step definitions within your Cypress project structure.

What is the best way to run Cucumber Gherkin scenarios in a Cypress test suite?

To run Cucumber Gherkin scenarios, you write your tests in `.feature` files and implement the matching step definitions in TypeScript, then execute your Cypress test suite using the command `npx cypress run`.

Does Cypress support Cucumber BDD out of the box?

Cypress requires the `@badeball/cypress-cucumber-preprocessor` dependency to support Cucumber BDD, facilitating the integration needed to parse Gherkin `.feature` files and map them to TypeScript step definitions.

How do I implement step definitions for Gherkin feature files in TypeScript?

Step definitions for Gherkin feature files are implemented in TypeScript using `.steps.ts` files, mapping the human-readable steps in your `.feature` scenarios to executable Cypress test logic.

Why use Gherkin for web application testing instead of standard Cypress scripts?

Using Gherkin for web application testing defines application behavior in a clear, collaborative format that bridges the gap between technical and non-technical stakeholders, ensuring a consistent and maintainable testing suite.

Can I use this Cucumber Cypress setup for non-technical stakeholder collaboration?

Yes, this setup uses a human-readable Gherkin format in `.feature` files to define application behavior, enabling clear collaboration and bridging the gap between technical and non-technical stakeholders.