← ClaudeAtlas

cucumber-testinglisted

Use for any question or task about Cucumber or Gherkin in Java, Kotlin, JavaScript or Ruby, including quick how-to questions: setting up Cucumber-JVM with JUnit 5, Cucumber-JS or Cucumber-Ruby, writing .feature files and step definitions, undefined or ambiguous steps and Cucumber expression mismatches, tags, and JUnit XML reports.
testland/qa · ★ 13 · Testing & QA · score 80
Install: claude install-skill testland/qa
# cucumber-testing ## Overview Per [cucumber-install][ci]: [ci]: https://cucumber.io/docs/installation/ > "Cucumber is available for most mainstream programming > languages." Cucumber implementations split into tiers ([cucumber-install][ci]): > - **Official**: Hosted under the main Cucumber organization > (JavaScript, Java, Ruby, Android, Kotlin, Scala, C++) > - **Semi-official**: Developed elsewhere but use Cucumber > components (PHP's Behat, Python's Behave, .NET's Reqnroll) This skill covers the three most-used official implementations: **Cucumber-JVM** (Java + Kotlin), **Cucumber-JS** (Node), and **Cucumber-Ruby**. For Python, see `behave-testing`. For .NET, see `reqnroll-testing`. ## When to use - The team uses BDD with Gherkin features. - Cross-stakeholder collaboration is the value (Gherkin scenarios read by non-engineers). - Acceptance criteria authored as Gherkin scenarios per `gherkin-from-stories`. If only engineers will read the tests, BDD's collaboration value is wasted - plain xUnit-style tests are simpler. Not sure which runner fits the repo, or whether BDD is worth adopting at all? See [references/runner-selection.md](references/runner-selection.md) - the runner decision table, per-runner first-run commands, the SpecFlow end-of-life note, and the "when BDD is not worth it" test. ## Step 1 - Install (Cucumber-JVM) Maven: ```xml <dependency> <groupId>io.cucumber</groupId> <artifactId>cucumber-java</artifactId> <version>7.20.0</version>