Generate Cucumber BDD tests with Gherkin scenarios

This skill generates Cucumber BDD tests - Gherkin feature files and step definitions in Java, JavaScript, or Ruby. It covers Gherkin feature file structure with Feature, Background, Scenario, and Scenario Outline sections using Examples tables for data-driven runs, such as a login feature with successful and invalid-credential scenarios plus a parameterized outline testing multiple email, password, and result combinations. It covers Java step definitions using Cucumber's annotation-based Given, When, and Then with typed string parameters and JUnit assertions, JavaScript step definitions using the cucumber-js library with async page interactions and chai assertions, lifecycle hooks that set up a driver before a scenario and tear it down after, attaching a failure screenshot when a scenario fails, and tag-based scenario filtering using tags like smoke, critical, slow, and regression, run through Maven's tag-filter expressions with AND and NOT logic. It documents anti-patterns to avoid: UI details in Gherkin instead of business language, one step per line of code instead of meaningful business-level steps, no Background for shared setup instead of using one, and imperative instead of declarative step style, each with a readability, DRY, or maintainability rationale. It also covers cloud execution on LambdaTest's TestMu AI platform via environment-variable credentials and platform capabilities covering build name, scenario name, target platform, and video recording, for both Java through a remote WebDriver against the LambdaTest hub and JavaScript through a Selenium builder with embedded credentials in the server URL. A quick-reference table covers common commands - running all tests in Java through Maven with the JUnit platform engine, running all tests in JavaScript through cucumber-js, tagged runs, dry runs, and undefined-step snippet generation - and a companion playbook reference covers eleven deeper topics: project setup, feature-writing patterns, step definitions, dependency injection and shared state, hooks and lifecycle ordering, custom parameter types, parallel execution, reporting, CI/CD integration, a debugging quick-reference, and a best-practices checklist.

Use it when a user mentions Cucumber, Gherkin, Feature or Scenario, Given/When/Then, or BDD, and needs feature files or step definitions generated in Java, JavaScript, or Ruby.

Given a user story or test requirement, it produces a Gherkin feature file with Background, Scenarios, and Scenario Outlines where data-driven, matching step definitions in the target language, lifecycle hooks, and tag-based run configuration.

Cucumber-JVM for Java or the cucumber-js library for JavaScript, JUnit or chai for assertions, Selenium WebDriver for browser automation, and LambdaTest's TestMu AI cloud grid for remote cross-browser execution.

QA engineers and developers writing BDD test suites in Cucumber who want correct Gherkin structure, working step definitions, and cloud execution setup rather than assembling boilerplate from scratch.