-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Expose the max number of retries to formatters #71
Comments
Moved this to the main repo, as I think it would only be practically achievable by adding to the standard messages - the test cases that can be retried could be a subset because of —retry-tag-filter so a global setting would seem off to me. I think this would need to live on the TestCase message as eg “maximum_attempts”. Balanced against that, it’d have impact across implementations and is perhaps a bit niche. |
Again I've not dived into the protobuf stuff much, but what I would think is that if a specific scenario failed once but passed 2nd time around, that wouldn't affect another scenario. As such to save weight (And possibly time), couldn't this be something that wraps the whole message structure at the top level? |
@luke-hill the issue with putting something like |
As in it only applies if the original test failed? Or if the param was input? Because if the param is input then you can hard-code the value to |
Hey @davidjgoss and @charlierudolph!
Would it be possible to make the information about the max number of retries specified via
--retry
parameter available to Cucumber formatters?At the moment Cucumber messages provide information about the current
attempt
number, for example:However, they don't tell how many attempts there are left, which makes reporting a bit inconvenient.
Perhaps this information could be added to
IFormatterOptions
either to the mainoptions
object itself or underparsedArgvOptions
. I think the behaviour could be similar to how theRerunFormatter
works.Is this a feature you'd be willing to add / review a PR for?
The text was updated successfully, but these errors were encountered: