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.
Summary
Instead of using string constants, use an enum for the result status
(passed, failed, ...).
Motivation and Context
Based on a review comment on the upgrade to a newer Gherkin version, that pointed to the problem of using string constants for result status (the result class in Gherkin2 did not have a string constant for the pending status, making matter more complicated), I have introduced an enum in the Result class for the possible result statuses
How Has This Been Tested?
The test suites has been updated and amended to, so it covers the change from strings to enum constants for result statuses.
Types of changes
Checklist: