false negative return for broken feature file

[triesztui]

👓 What did you see?

test executions returned 0 (left pipeline green) even though no test ran at all due to one broken feature file

✅ What did you expect to see?

cucumber-js should return nonzero in case of feature file parsing errors

📦 Which tool/library version are you using?

$ node -v
v19.4.0
$ npm -v
9.2.0
$ node_modules/@cucumber/cucumber/bin/cucumber-js -v
This Node.js version (v19.4.0) has not been tested with this version of Cucumber; it should work normally, but please raise an issue if you see anything unexpected.
8.10.0

🔬 How could we reproduce it?

Steps:

1. put some >>>>> signs into a feature file

$ node_modules/@cucumber/cucumber/bin/cucumber-js
This Node.js version (v19.4.0) has not been tested with this version of Cucumber; it should work normally, but please raise an issue if you see anything unexpected.
Parse error in "features/xxxxxx.feature" (4:5): expected: #TagLine, #RuleLine, #Comment, #Empty, got '>>>>>>>> Scenario Outline: xxxxxxx'
...

$ echo $?
0

[davidjgoss]

Thanks for raising @triesztui. I can reproduce this too and will dig into it soon.

[davidjgoss]

Are you using the html formatter @triesztui? Initial investigation suggests it's related.

[davidjgoss]

Released in https://github.com/cucumber/cucumber-js/releases/tag/v8.11.1

[triesztui]

yes I do use the html formatter. Thank you very much for looking into this David.

[triesztui]

fix works well, thank you.