forked from Klaveness-Digital/cypress-cucumber-preprocessor
-
-
Notifications
You must be signed in to change notification settings - Fork 149
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Correct an issue with string
stepDefinitions
This fixes #781.
- Loading branch information
Showing
3 changed files
with
36 additions
and
2 deletions.
There are no files selected for viewing
This file contains 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 file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
# https://github.com/badeball/cypress-cucumber-preprocessor/issues/781 | ||
|
||
Feature: non-array step definitions, not matching | ||
Scenario: non-array step definitions, not matching | ||
Given additional preprocessor configuration | ||
""" | ||
{ | ||
"stepDefinitions": "foo/bar" | ||
} | ||
""" | ||
And a file named "cypress/e2e/a.feature" with: | ||
""" | ||
Feature: a feature | ||
Scenario: a scenario | ||
Given an undefined step | ||
""" | ||
When I run cypress | ||
Then it fails | ||
And the output should contain | ||
""" | ||
Step implementation missing for "an undefined step". | ||
We tried searching for files containing step definitions using the following search pattern templates: | ||
- foo/bar | ||
These templates resolved to the following search patterns: | ||
- foo/bar | ||
These patterns matched **no files** containing step definitions. This almost certainly means that you have misconfigured `stepDefinitions`. | ||
""" |
This file contains 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