ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Custom Parameter Type Conflict Cucumber Expressions provide a mechanism to map step arguments to Java method arguments via the ParameterTypeRegistry . This allows for domain-specific parsing that replaces traditional regular expressions. When integrating Cucumber-JVM with JUnit, developers may register multiple custom parameter types. A technical uncertainty
The goal is to maintain database schema consistency after a Cucumber scenario that includes data-definition-language statements, given that most relational databases issue an implicit commit when DDL executes. Because Cucumber-JVM's @Transactional annotation only rolls back data-manipulation operations, schema changes such as ADD COLUMN persist beyond the sc
Scenario Outline Execution Behavior Cucumber-JVM utilizes Scenario Outlines to execute a single scenario multiple times based on the rows provided in an Examples table. Each row is treated as an independent scenario for the purpose of reporting and execution. Hook Lifecycle Constraints When integrating Cucumber with external test runners like JUnit or TestNG
Cucumber JVM ↔ Cucumber for JavaScript: Shared Gherkin & Custom Parameter Types The goal is to set up a repeatable development environment where both Cucumber JVM and Cucumber for JavaScript consume the same Gherkin feature files. The primary constraint is that each runtime implements its own step‑definition glue and its own mechanisms for Cucumber Expre
Cucumber JVM's built-in JSON and HTML formatters serialize scenario names, step arguments, and table cells directly into report files without applying any masking or redaction. For teams that must keep credentials, API keys, or personal data out of version-controlled artifacts, the goal is to prevent these values from appearing in generated reports while sti
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
Cucumber JVM (7.x) scans every glue package for classes containing @Before and @After methods and registers all hooks it finds. The documentation states that execution order is undefined unless an explicit order is given. In a project that keeps scenario setup and teardown logic in several glue packages — for example, one package for database fixtures and an
junit
java