-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Cucumber Tags Not Running Features without Background Defined #2432
Comments
What happened before this past week? What changed? |
Can you paste the output here where you see |
The QA developers said that they had changed the tags so that they are at the Feature level rather than at the Scenario level, but according to the Cucumber docs the tag inheritance would basically ensure there is not a change in functionality, and since there are working tests that would not seem to be the problem. Here is the output for Resolved configuration on a test run that did not run any scenarios vs. the configuration for a run when scenarios ran, the output is similar. Not running scenarios:
vs. Resolved configuration when it proceeds to run scenarios:
|
👓 What did you see?
For the past week, we have been unable to use the cucumber-js CLI --tags flag to run Scenarios in Features that do not contain the "Background" keyword. The command we are using is
cucumber-js $(node playwright-parallel.js ./features) --retry 1 --parallel 3 --tags \"@example-tag and not @broken and not @known-issue and not @scopeChanged and not @local\" -f json:reports/cucumber-report-$INDEX.json -f html:reports/cucumber-report.html
. Playwright-parallel.js provides paths to our feature files. Even though the DEBUG logs show that cucumber found 86 scenarios based on the tag provided, no scenarios are run, and we see the output as "0 scenarios; 0 steps". We are not seeing any errors, just that there are no scenarios run despite the fact that the array for "Found feature files based on configuration: []" consist of 86 accurate paths to files. It does not make logical sense given the purpose of the "Background" keyword that we see this result when Features do not contain "Background", and that scenarios run as expected when Features do contain "Background".✅ What did you expect to see?
We expect to see that all of the scenarios from the selected features listed in the DEBUG logs will be run, or that we will at least encounter an error that indicates why the scenarios are not running.
📦 Which tool/library version are you using?
node v18.17.0, cucumber ^9.4.0
🔬 How could we reproduce it?
📚 Any additional context?
No response
The text was updated successfully, but these errors were encountered: