$ show cucumber/cucumber-jvm-starter-maven-java
Starter template for Cucumber-JVM with Java and Maven. It is not a production application: the only production source file is an empty Belly class, while all meaningful code lives in the test tree. RunCucumberTest is a JUnit Platform Suite that boots the Cucumber engine, cucumber.properties supplies glue and plugin configuration, and belly.feature defines one scenario whose step definitions are bound via annotations. Running `./mvnw test` executes the suite and prints pretty output; one step passes, one is intentionally aborted with a TODO, and one is undefined. The repository's actual purpose is to demonstrate a minimal Cucumber setup and serve as a starting point for BDD projects. Architecturally this is a Maven build with test-scoped dependencies only: cucumber-java, cucumber-junit-platform-engine, junit-platform-suite, and assertj-core. Dependencies are imported through BOMs, Java 17 is configured as the release target, and the Maven wrapper pins Maven 3.10.0. The primary data flow is Gherkin -> Cucumber engine -> annotated JUnit step methods -> AssertJ assertions. There is no web server, API, or business logic. The repository includes CI that runs the tests on Ubuntu and Windows across Java 17 and 21, Renovate for dependency updates, and a Zizmor workflow for GitHub Actions security analysis, indicating active project maintenance.
The LLM identified 1 files worth highlighting for reuse:
A self-contained JUnit Platform Suite that activates Cucumber's engine by delegating package selection and configuration to @SelectPackages and @ConfigurationParametersResource("cucumber.properties"). It has no project-specific logic, so it can be copied into any Java/Maven/Gradle project with cucumber-junit-platform-engine on the classpath to provide a modern Cucumber runner. This is the recommended replacement for legacy @RunWith(Cucumber.class) runners and keeps feature and glue configuration externalized.