ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #cucumber
Learn how Cucumber Data Tables let you pass tabular test data to a single step definition, improving readability and type safety.
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 JVM's default formatters (pretty, json, html, JUnit) serialize step arguments, data-table cells, and scenario-outline examples verbatim into report output, including any embedded credentials, tokens, or secrets. The core runtime provides no automatic detection or masking of sensitive values, and no first-party configuration flag exists as of Cucumbe
Cucumber JVM JUnit 4 runner deprecation and JUnit 5 platform engine migration A Cucumber JVM test suite is being upgraded from version 6.x to 7.x. The goal is to keep existing feature files and step definitions running while moving off the deprecated JUnit 4 runner. Cucumber JVM 7.x assumes Java 11 or higher and marks `cucumber-junit` as deprecated in favor
Cucumber-JVM allows the definition of custom ParameterType mappings to convert Gherkin string captures into strongly typed Java objects. This mechanism simplifies step definitions by removing manual parsing logic from the method body. While ParameterType works for individual step arguments, there is uncertainty regarding its application to DataTable entries.
Goal: Execute only a subset of scenarios that match a broad tag expression (e.g., @regression) without modifying feature files or relying on external wrappers. Constraint: Cucumber’s --tags option selects all matching scenarios and provides no built‑in parameter to cap the count to a specific number (e.g., first 50). When parallel runners are used, the order
Rollback safety after a schema change in Cucumber When a scenario creates or alters tables in an @Before hook, the test framework often relies on the underlying ORM to begin a transaction and then rolls it back in an @After hook. However, many databases do not support rolling back DDL statements, leading to the documented error Failed to commit transaction w
In Cucumber 7.x and later, the transition from Regular Expressions to Cucumber Expressions has standardized how step parameters are parsed. While types like { int} and { string} improve readability, a specific behavioral challenge arises when multiple step definitions match the same Gherkin line. When a Gherkin step satisfies the criteria for two or more Cuc
Evaluating the interoperability boundary between Cucumber JVM version upgrades and the associated testing framework runtime remains ambiguous when step definitions fail to load. Glue-code compatibility between Cucumber JVM 6.x and 7.x frequently introduces silent failures and version mismatches with JUnit or TestNG can exacerbate detection gaps. The --dry-ru
java