Successful scenario after the "The test doesn't have an implementation" error #1358
Description
A Cucumber scenario is reported as passed in Allure when the step has no matching step definition (undefined), instead of being marked as failed/broken or at least skipped according to Cucumber semantics.
Repository to reproduce
https://github.com/bionikokex/allure
Steps to reproduce
Clone the repository and use the minimal setup with Allure Cucumber.js reporter enabled.
Ensure at least one earlier step is implemented and the final Then step is intentionally left without a step definition.
Install dependencies with yarn install and run yarn test.
Open the generated Allure report and observe the scenario status shown as passed.
Expected behavior
Cucumber marks a step with no matching definition as undefined, and subsequent steps are skipped; in strict mode undefined/pending should fail the build.
Allure should map this to a non‑passed status (failed/broken or skipped), not green passed.
Actual behavior
The scenario appears as passed in the Allure report when the final step is undefined, contradicting Cucumber’s step result semantics.
Environment
Node 18+, Yarn 1.x, @cucumber/cucumber 12.x, allure-cucumberjs 3.4.x, allure-js-commons 3.4.x, Playwright 1.53.x.
Reproduced on Windows desktop; behavior expected to be toolchain‑dependent rather than OS‑specific.