We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According to https://github.com/cucumber/cucumber-js/blob/main/docs/configuration.md#finding-your-features cucumber-js somewhere-else/**/*.feature should work just like { paths: ['somewhere-else/**/*.feature'] } in the config. But it does not, the CLI glob only expands one folder deep, where as the glob in the configfile expands multiple levels (as expected).
cucumber-js somewhere-else/**/*.feature
{ paths: ['somewhere-else/**/*.feature'] }
Feature-file glob behaves the same way in config and CLI
node v22.11.0 cucumber-js v11.1.0
Example folder: johenning/cucumber-js-examples@9e5a2c0
~/examples/esm-node(main)$ ./node_modules/.bin/cucumber-js --dry-run ./features/**/*.feature ---- 2 scenarios (2 skipped) 4 steps (4 skipped) 0m00.006s (executing steps: 0m00.000s)
vs
~/examples/esm-node(main)$ ./node_modules/.bin/cucumber-js --dry-run ./features/deep/greeting.feature ./features/deep/greeting2.feature features/deep/deeper/greeting.feature ------ 3 scenarios (3 skipped) 6 steps (6 skipped) 0m00.006s (executing steps: 0m00.000s)
and with paths: ["./features/**/*.feature"],
paths: ["./features/**/*.feature"],
~/examples/esm-node(main)$ ./node_modules/.bin/cucumber-js --dry-run ------ 3 scenarios (3 skipped) 6 steps (6 skipped) 0m00.006s (executing steps: 0m00.000s)
Potentially relevant: My bash version is GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu).
GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
👓 What did you see?
According to https://github.com/cucumber/cucumber-js/blob/main/docs/configuration.md#finding-your-features
cucumber-js somewhere-else/**/*.feature
should work just like{ paths: ['somewhere-else/**/*.feature'] }
in the config. But it does not, the CLI glob only expands one folder deep, where as the glob in the configfile expands multiple levels (as expected).✅ What did you expect to see?
Feature-file glob behaves the same way in config and CLI
📦 Which tool/library version are you using?
node v22.11.0 cucumber-js v11.1.0
🔬 How could we reproduce it?
Example folder: johenning/cucumber-js-examples@9e5a2c0
vs
~/examples/esm-node(main)$ ./node_modules/.bin/cucumber-js --dry-run ./features/deep/greeting.feature ./features/deep/greeting2.feature features/deep/deeper/greeting.feature ------ 3 scenarios (3 skipped) 6 steps (6 skipped) 0m00.006s (executing steps: 0m00.000s)
and with
paths: ["./features/**/*.feature"],
~/examples/esm-node(main)$ ./node_modules/.bin/cucumber-js --dry-run ------ 3 scenarios (3 skipped) 6 steps (6 skipped) 0m00.006s (executing steps: 0m00.000s)
📚 Any additional context?
Potentially relevant: My bash version is
GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)
.The text was updated successfully, but these errors were encountered: