Cucumber Tag‑Based Scenario Selection with Hooks: An Architecture Note
Learn how to use Cucumber JVM tags and hooks to run selective tests while keeping setup logic isolated and thread‑safe.
Loading…
ReadMeFeed / Community knowledge
Cucumber
Real questions. Useful conversations. Find the people who know your stack.
Cucumber
Frameworks & web · #cucumber
Streamlining Step Definition Maintenance in Java with Cucumber Expressions
Cucumber Expressions let Java developers replace regex‑heavy step definitions with readable placeholders like {int} and {string}. This post explains the problem, shows a concrete example, discusses trade‑offs, and gives a practical rollout plan.
javaManaging Step Parameters with Cucumber Data Tables
Stop bloating your feature files. Learn how to use Cucumber Data Tables to pass multiple parameters to a single step, reducing redundancy and improving test speed.
Using Cucumber Data Tables to Parameterize Tabular Test Data
Learn how Cucumber Data Tables let you pass tabular test data to a single step definition, improving readability and type safety.
How can I establish a reliable deployment procedure for Cucumber JVM tests in a Java project?
Establishing a reliable deployment procedure for Cucumber JVM tests involves ensuring that the test framework is correctly integrated into the build system, that feature files and step definitions are version‑controlled alongside application code, and that test execution produces consistent results across development, staging and production environments. The
Cucumber 7.0 default plugin shift impacts alert clarity when using pretty and json together
Goal: Configure Cucumber to emit step‑level alerts via the pretty plugin while simultaneously generating JSON output for downstream alerting, keeping console noise low. Constraint: Starting with Cucumber 7.0 the default plugin list changed to ['progress']; adding both 'pretty' and 'json' plugins does not guarantee a deterministic order, which can cause inter
"Text '2023-07-15 14:30' could not be parsed at index 0" – ZonedDateTime conversion failure in Cucumber step definitions
Error condition When a Cucumber step definition expects a ZonedDateTime parameter and the step passes a date‑time string without time‑zone information (e.g., "2023-07-15 14:30"), the built‑in parameter converter throws a DateTimeParseException with the message "Text '2023-07-15 14:30' could not be parsed at index 0". The framework does not apply the JVM defa
AmbiguousStepDefinitionsException and Regex Overlap Limits
Cucumber-JVM maps Gherkin steps to Java methods using Cucumber Expressions or regular expressions. When a single step matches multiple definitions, the framework triggers an AmbiguousStepDefinitionsException to prevent non-deterministic execution. Currently, the framework lacks a native priority or weighting mechanism to designate a primary match when overla