cucumber / cucumber/cucumber-ruby
`retry-total` conflicts with `html-formatter` when exhaustion limit hit
- Dominant language
- Ruby
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 3
Description
### 👓 What did you see?
The HTML report does not include scenarios which are skipped from being retried after exhaustion limit is hit
### ✅ What did you expect to see?
HTML formatter would show failures
### 📦 Which tool/library version are you using?
cucumber 11.1.1
html-formatter 23.1.0
### 🔬 How could we reproduce it?
Hit the exhaustion limit on a running context. So for example have a folder with 3 features and 3 scenarios. Have all 3 fail, set --retry 1 and --retry-total 2.
The third scenario won't feature in the report.
### 📚 Any additional context?
#1669 introduced it
Contributor guide
Research direction
Start by reading issue #1669, which the report identifies as the source of the behavior. Reproduce it with three failing scenarios, `--retry 1`, and `--retry-total 2`; the work is done when the HTML report includes the scenario skipped after the exhaustion limit is hit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100