Closed pawelrochala closed 1 year ago
Thanks for the detail @pawelrochala. This is a weird one.
I'm not able to reproduce this but I think it's going to be something about one or more of your features. Would you be willing to share the filenames and/or content?
A possible way to narrow it down would be to run one feature at a time and see if any in particular yield the failure.
I'd also note that the command line args you are passing in are duplicating/conflicting what's in your config file.
Moving the feature files to the default location (./features/**
) and removing the paths
config fixed the issue for me.
This issue is stale because it has been open for 3 weeks with no activity. Remove the stale label or comment or this will be closed in another 5 days.
I've done a minimal reproducible example here: https://github.com/davidjgoss/cucumber-js-repro-2226
Essentially the issue comes from the same feature file getting loaded twice. Declaring the paths in both the config file and on the CLI looks like identical config that should be deduplicated. But your shell expands the glob, so the merged config Cucumber ends up with is:
{
paths: [ 'src/features/*.feature', 'src/features/a.feature' ]
}
Which isn't anticipated and causes the duplication.
Thanks all for your patience with this one. Fixed in https://github.com/cucumber/cucumber-js/releases/tag/v9.0.1
👓 What did you see?
Hi I have following stacktrace
I checked the logic in parseTestCaseAttempt and it seems that gherkinScenarioLocationMap keys doesn't match provided picke id.
✅ What did you expect to see?
A correct summary.
📦 Which tool/library version are you using?
Node.js v16.16.0.
🔬 How could we reproduce it?
I'm running :
"cucumber-js --config src/cucumber.json src/features/*.feature --require-module ts-node/register --require src/setup.ts"
cucumber.json:
setup.js
📚 Any additional context?
This text was originally generated from a template, then edited by hand. You can modify the template here.