📄️ Typed Data Tables
The default LISTOFOBJECT_PARAMS data-table mode — Gherkin data tables generate type-safe inner classes with typed accessors. No Cucumber dependency.
📄️ Cucumber Data Tables
The CUCUMBERDATATABLE mode — Gherkin data tables are passed as Cucumber DataTable objects, giving you the full Cucumber DataTable API for conversions and POJO mapping.
📄️ TDD Workflow
Iterative red-green development backed by failing tests generated from incomplete feature files.
📄️ Abstract Mode
Abstract mode is the default — the generator emits an abstract test class with one abstract method per step. Missing implementations are caught at compile time, not at run time.
📄️ DocStrings
Gherkin doc strings (triple-quoted blocks) become a trailing String parameter on the step method, with formatting preserved via Java text blocks.
📄️ Convention Discovery
@Gherkin2JUnit with no path argument — the processor finds feature files by convention, looking in the same package as the marker class.
📄️ Glob Patterns
A glob pattern in @Gherkin2JUnit lets a single marker class drive many feature files — one generated test class per feature, all extending the same marker.
📄️ Type Refinement
Refine the generated data-table Param classes with enums (or any custom type) to turn data drift into a compile error.
📄️ Config Inheritance
Share generation options across many marker classes via @Gherkin2JUnitOptions on a base class. Override specific options per marker as needed.
📄️ Cucumber Annotations
Two related capabilities: generating @Given / @When / @Then Cucumber annotations on step methods, and using those annotations to match steps to implementations by pattern instead of by method name.