Skip to content
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

Update some step definitions to use Cucumber Expression syntax #822

Merged
merged 1 commit into from
Jun 21, 2021

Conversation

mvz
Copy link
Contributor

@mvz mvz commented Jun 20, 2021

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

  • Internal change (refactoring, test improvements, developer experience or update of dependencies)

@mvz mvz force-pushed the update-gherkin-syntax branch 2 times, most recently from fc14d67 to c227c35 Compare June 21, 2021 06:23
The main goal of this change is to allow specifying expected output that
contains double qoutes. To that end, the existing regular expression is
replaced by the {string} parameter type.
@mvz mvz force-pushed the update-gherkin-syntax branch from c227c35 to 4f9d664 Compare June 21, 2021 06:24
@mvz mvz merged commit ff7626e into main Jun 21, 2021
@mvz mvz deleted the update-gherkin-syntax branch June 21, 2021 06:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant