Cucumber Scenario Outline Hook Lifecycle Behavior

Scenario Outline iteration and @Before/@After hook lifecycle

0 reputation · 14 Jul 2021, 02:29 UTC

92.7K views0

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, the lifecycle of @Before and @After hooks must align with each iteration of the Examples table to ensure test isolation. However, the precise interaction between these hooks and the iteration cycle can vary depending on the runner configuration.

What is the guaranteed execution order of hooks when a Scenario Outline is processed across multiple rows? Does the framework ensure a clean state by triggering the full hook lifecycle for every individual row in the Examples table regardless of the runner used?

Keep exploring this topic

AmbiguousStepDefinitionsException and Regex Overlap Limits

Exploring the limitations of Cucumber-JVM's step matching and the lack of a priority system when facing AmbiguousStepDefinitionsException.

Cucumber JVM JUnit 4 runner deprecation and JUnit 5 platform engine migration

Cucumber JVM 7.x deprecates the JUnit 4 runner in favor of the JUnit 5 platform engine; migration scope is unclear.

Tag-filtered Cucumber JVM scenarios run in different order across repeated executions

Diagnosing unstable execution order and cross-scenario state in tag-filtered Cucumber JVM suites.

Cucumber JVM JSON and HTML formatters emit step arguments without built-in secret redaction

Cucumber JVM formatters write step arguments verbatim into JSON and HTML reports with no built-in redaction. Explore the configuration gap for keeping secrets out of test artifacts.

To clarify the lifecycle: Cucumber-JVM treats every row in an Examples table as a standalone scenario. Consequently, the @Before and @After hooks are guaranteed to execute for every individual row, regardless of whether you are using JUnit or TestNG. The sequence is strictly @Before → Steps → @After for each iteration.

However, it is important to distinguish these from suite-level hooks. If you are using @BeforeAll or @AfterAll (available in newer versions), these trigger only once per test suite execution, not per row. Additionally, while the hook lifecycle resets, any state stored in static variables will persist across iterations. To verify isolation, you can implement a @Before hook that logs a unique identifier or increments a counter to confirm it triggers exactly once per example row.

Scenario Outline iteration and @Before/@After hook lifecycle

Scenario Outline Execution Behavior

Hook Lifecycle Constraints

0 answers

Your perspective belongs here.

1 question comment