-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not report failures in cucumber scenario outline results #84
Comments
alexmsmartins
changed the title
Does not report failures in cucumber scenario outlines results
Does not report failures in cucumber scenario outline results
Jul 25, 2018
I am sorry but, is this project dead? |
Same happens if two Cucumber scenarios have the same name. |
gaeljw
added a commit
to KelkooGroup/theGardener
that referenced
this issue
Apr 16, 2020
Otherwise errors are not reported, see sbt/junit-interface#84
notflorian
pushed a commit
to KelkooGroup/theGardener
that referenced
this issue
Apr 26, 2021
Otherwise errors are not reported, see sbt/junit-interface#84 # Conflicts: # test/features/navigation/provide_menu.feature
Related: #95 |
For anyone coming here, this issue is now "solved" by Cucumber since few versions as they implemented a unique name for each scenario with a suffix. The underlying issue can still appear but not in Cucumber context. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Cucumber tests with Data Tables will pass with failing examples as long as the first example passes.
This happens because all the examples have the same fully qualified name that comes from the scenario outline description.
I have submitted a PR to fix this #83 .
The text was updated successfully, but these errors were encountered: