|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
There are 3 options
1) fail any scenario outlines if a result isn't present. (any jobs with these will then be marked as failed)
2) pass any scenario outlines if a result isn't present. (any failures will be silently passed which is not good)
3) barf like we do now - and get fixed upstream.
3 is the only viable solution in my eyes and this should be fixed upstream in the ruby cucumber implementation.
This would be marked as wont-fix as this is not a bug - we have been supplied with malformed input - but leaving open incase anyone else hits this so they can see where the real cause is. (will close when upstream is fixed).