Closed karol719 closed 1 year ago
The error is because there should be a result for a step and it's not there. We could make the code more defensive but I'd like to understand how this can happen. Are you able to post a minimum reproducible example repo that this happens with? Can you reproduce locally? Can you switch to use the message
formatter and post that output somewhere?
There was issue with config we had something like this
module.exports = {
default: {
paths: ['test/e2e/feature/x/**/*.feature'],
require: [
'test/e2e/step-definitions/x/**/*.ts',
'test/e2e/step-definitions/http.step-definition.ts',
],
requireModule: ['ts-node/register'],
publishQuiet: true,
parallel: 1,
},
};
When parallel is set to 1 then there was an issue, but if I removed parallel everything works fine.
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.
This issue was closed because it has been stalled for 5 days with no activity.
👓 What did you see?
I am using CircleCI and Cucumber, my workflow contains setup step and then steps with cucumber tests, after successful tests there is type error which looks like this:
✅ What did you expect to see?
success message
📦 Which tool/library version are you using?
I'm using
🔬 How could we reproduce it?
Circle Ci setup tests so it runs
npm install
, and then it should run in parallel 4 jobs which performs tests from 4 different cucumber configurations.