kotlin-cucumber-tests

Plan and review Kotlin Cucumber test suites with readable feature files and decoupled step definitions.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/rotilho/skills --skill kotlin-cucumber-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kotlin-cucumber-tests
Source: https://github.com/rotilho/skills/tree/main/kotlin-cucumber-tests
Command: npx skills add https://github.com/rotilho/skills --skill kotlin-cucumber-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan, review, or improve Kotlin Cucumber / BDD tests: decide when Cucumber fits, structure feature files, step definitions, hooks, fixtures, and Kotlin helpers, and keep domain language readable without coupling steps to implementation details. Use when the request explicitly centers on Kotlin Cucumber, Kotlin BDD, feature files, step definitions, hooks, or executable-specification tests and reviews.

Core Features & Use Cases

  • Plan, structure, and review Kotlin Cucumber tests to ensure readability, maintainability, and proper separation of concerns between business rules and implementation.
  • Organize hooks, shared fixtures, and scenario state with explicit scoping to avoid cross-scenario leakage.
  • Provide Kotlin-specific guidance that improves glue code while keeping feature files in a business-readable language.

Quick Start

Plan and review Kotlin Cucumber tests by keeping domain language readable, defining clear step definitions, and organizing hooks and fixtures per scenario.

Frequently Asked Questions about kotlin-cucumber-tests

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

FAQPage Schema
How do I structure Kotlin Cucumber feature files to keep them business-readable?

Keep Kotlin Cucumber feature files business-readable by aligning scenarios with domain language, organizing scenario flows logically, and decoupling step definitions from implementation details for maintainable executable specifications.

When should I use Cucumber for Kotlin BDD testing instead of standard unit tests?

Use Cucumber for Kotlin BDD testing when executable specifications and collaboration with non-technical stakeholders are required. Evaluate if behavior-driven development fits your project needs better than standard unit testing before implementation.

How do I organize Cucumber hooks and shared fixtures in Kotlin to avoid cross-scenario leakage?

Organize Cucumber hooks and shared fixtures in Kotlin by applying explicit scoping to scenario state. This prevents cross-scenario leakage and ensures each behavior-driven development test remains isolated and reliable.

What is the best way to write thin step definitions in Kotlin Cucumber tests?

Write thin step definitions in Kotlin Cucumber tests by delegating implementation logic to Kotlin helper classes. Keep glue code minimal to ensure feature files stay decoupled from details and maintain readability.

Does Cucumber JVM work well with Kotlin for behavior-driven development?

Cucumber JVM works well with Kotlin for behavior-driven development when paired with Kotlin-compatible tooling and clear helper structures. It supports thin step definitions and domain-aligned scenario organization effectively.

Why are my Kotlin Cucumber step definitions tightly coupled to implementation details?

Kotlin Cucumber step definitions become tightly coupled when glue code contains business logic instead of delegating to Kotlin helpers. Move logic out of step definitions to keep scenarios decoupled and maintainable.