cucumber / cucumber/godog

Option StopOnFailure not working since 15.0

Open
#768 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
2.7k
Forks
280
Avg merge
2d 20h
Merged PRs (30d)
2

Description

### 👓 What did you see?

Give I set the StopOnFailure option
When a step fails in a scenario
Then the test stops immediatly without evaluating any more steps
And the suite stops without evaluating any more scenarios.

Currently it will evaluate all the steps and report failures on all subsequint steps.
This makes it hard to debug and if you are using interpolation in the steps they can/do break.

### ✅ What did you expect to see?

The scenario should always stop on the first failed step. The suite should stop on the first failed scenario if the StopOnFailure is set.

I am currently working on a fix + a test.

### 📦 Which tool/library version are you using?

godog 16.0

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the StopOnFailure behavior in godog 16.0 with a failing step and multiple scenarios. Trace the option's execution path and add the regression test mentioned in the issue; done means later steps are not evaluated after a failure and the suite stops after the first failed scenario when enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.