Update some step definitions to use Cucumber Expression syntax #822
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
Update some step definitions to use Cucumber Expression syntax
Details
This updates some of the step definitions in the command section to use Cucumber Expression syntax. In particalar, this uses the {string} parameter type for the expected output strings.
Motivation and Context
The main goal of this change is to allow specifying expected output that contains double qoutes.
How Has This Been Tested?
I ran some of the cucumber scenarios that seemed relevant.
Types of changes