Test on Windows: Make features in section 1 pass #966
Merged
Conversation
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
This adds a Windows version of the original example that uses a bash file without extension. On Windows, an extension is needed.
mvz
force-pushed
the
run-cucumber-features-section-1-on-windows
branch
from
6fd8954 to
2ab2b5f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
This makes GitHub Actions run just the Cucumber scenarios in section 01 (getting started) on Windows, and makes them pass.
Details
This cherry-picks commits from #894 (and originally from other pull requests) that affect scenarios from section 01. The goal is to gradually activate more sections until the whole suite passes.
@requires-bashunless bash is installed.Motivation and Context
One small step toward fully testing on Windows.
How Has This Been Tested?
I ran the GitHub Action by hand.
Types of changes
Internal change (refactoring, test improvements, developer experience or update of dependencies)