Avoid errors when elements is not present in a feature - #18
Open
lawnmowerlatte wants to merge 7 commits into
Open
Avoid errors when elements is not present in a feature#18lawnmowerlatte wants to merge 7 commits into
lawnmowerlatte wants to merge 7 commits into
Conversation
Pull from head repo
Features that don't run any scenarios still show up in the JSON, so we have to avoid making assumptions about the presence of `elements`
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If there are no tests run, the elements field is not present in the behave output which causes behave2cucumber to generate an error. This change avoids this error by checking before accessing.