Cucumber & BDD Automation

A static field is one slot per class for the whole JVM, so concurrent scenarios read and write the same value. Scenarios overwrite each other's data, and the failure passes when rerun alone.

Register it in code the runner already loads with your step definitions: in Cucumber-JVM a method annotated @ParameterType, in cucumber-js a defineParameterType call in a support file. The name then becomes a placeholder that converts matched text into a domain object.

Measure per-scenario durations first, then decide what each pipeline stage must gate. Tag tiering buys speed by covering less, in-JVM parallelism buys it by demanding isolated glue, and sharding across agents buys it with infrastructure and result aggregation.

Start from the audience and the decision the report drives. Bundled formatters and tag-filtered runs cover most multi-team needs for free. Build on the message stream only when history, merging or per-team slicing survives those cheaper options.

The header selects the Gherkin dialect for that one file, changing only the keywords the parser accepts. Step text and step definitions are untouched. Without it the parser assumes English, so localized keywords fail to parse.

Cucumber-JVM runs @Before hooks in ascending order value, lowest first, and @After hooks in descending order, highest first, so teardown unwinds setup in reverse. Hooks that leave order unset share one default and have no guaranteed sequence.

AbstractTestNGCucumberTests feeds scenarios to one inherited test method through a data provider, so results arrive as repeated invocations. The command-line runner is not a test framework at all: it returns an exit code the build must interpret.

Write the content type immediately after the doc string's opening delimiter in the feature file. Cucumber-JVM pairs it with the step method's declared parameter type to select a @DocStringType transformer. With none registered, the body arrives as a plain String.

--publish uploads the run's message stream to Cucumber's hosted reports service and prints a link to the rendered report. In exchange, run data leaves your network, anyone holding the link can read it, and the run gains a network dependency.

@CucumberContextConfiguration marks the single glue class that tells cucumber-spring how to bootstrap the Spring test context. Exactly one entry point is allowed, so a second annotated class fails the run at startup. Step definition classes then become injectable Spring beans.

Parentheses make text optional and a slash alternates the words around it, so one Cucumber Expression covers several wordings. The same parentheses in a regular expression would be a capture group demanding another method argument; in an expression they capture nothing.

Reuse is two steps meaning the same action with a different value. Capture is one loose expression being the only match for a step it was never written for - Cucumber says nothing and the step passes wrongly.

Match each service to the implementation native to its language rather than mandating one estate-wide. Glue calls production code, so an out-of-stack choice buys shared tooling at the cost of a language boundary. Standardise conventions and reporting instead.