You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a Feature file containing multiple Scenarios and a Background, when the Background steps include logs, the report displays all these steps under the Background section. This behaviour makes it challenging to distinguish which steps correspond to each individual Scenario.
This is an example with 7 scenarios, but it gets more complicated when the feature file has more scenarios.
✨ What's your proposed solution?
It would be nice to move the Background steps in the Cucumber report next to the executed Scenario to be able to identify them easily.
⛏ Have you considered any alternatives or workarounds?
No response
📚 Any additional context?
$ npx cucumber-js -v 11.2.0
The text was updated successfully, but these errors were encountered:
I was aware of that topic, but as it has been stuck there for some time that's why I decided to open this enhancement in case this could be changed before that big refactor
Whilst the thread on cucumber/html-formatter#283 has been a little quiet, it is actively being worked on and should be in users hands in the next few weeks. So, closing this.
🤔 What's the problem you're trying to solve?
In a Feature file containing multiple Scenarios and a Background, when the Background steps include logs, the report displays all these steps under the Background section. This behaviour makes it challenging to distinguish which steps correspond to each individual Scenario.
This is an example with 7 scenarios, but it gets more complicated when the feature file has more scenarios.
✨ What's your proposed solution?
It would be nice to move the Background steps in the Cucumber report next to the executed Scenario to be able to identify them easily.
⛏ Have you considered any alternatives or workarounds?
No response
📚 Any additional context?
$ npx cucumber-js -v 11.2.0
The text was updated successfully, but these errors were encountered: