-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Rerun formatter output does not include failing scenario outline examples #57
Comments
Nor does the progress formatter. |
That's not true actually: you can use the line number of the row in the examples table and only that example will be run. |
+1 |
I don't suppose there has been any progress on or so much as a glance shot at this issue yet? It may not be deal-breaking, but it's quite annoying that you have to avoid scenario outlines when you're using the rerun formatter. |
I will personally not have time to look at this for several weeks, but I would be more than happy to support someone else in learning how to fix it for themselves. A while ago I re-wrote the formatting API, and as a result had to re-write several of the formatters. I was annoyed by them having only crude end-to-end feature tests, so I wrote detailed specs for most of them. They're really good (if I do say so myself) and make hacking on formatters surprisingly easy. I notice the rerun formatter doesn't have any specs yet, so this bugfix could be the first one! Take a look at the specs for the HTML and JUnit formatter for some pointers: |
I've fixed it in https://github.com/Jimdo/cucumber/tree/issue-57. Please review, |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Moved from Lighthouse ticket #701
The output file created by the rerun formatter does not include the failures encountered while running scenario outline examples
If one scenario fails, and two scenario outline examples fail, the output file will only include the scenario failure.
I would expect the output file to include the line number of the entire scenario outline, since line numbers of specific examples are not supported.
Feature file and step definition that reproduces this: https://gist.github.com/834214
The text was updated successfully, but these errors were encountered: