allure-js: [allure-js] Cannot start new step using v.2.0.0-beta.18 with cucumber-js
currentExecutable throws “No executable!” error when trying to execute startStep function.
Error: No executable!
at CucumberAllureInterface.get currentExecutable [as currentExecutable] (/Users/fguidobaldi/Repositorios/fury_qaautomation/node_modules/allure-cucumberjs/dist/src/CucumberAllureInterface.js:65:15)
at CucumberAllureInterface.startStep (/Users/fguidobaldi/Repositorios/fury_qaautomation/node_modules/allure-cucumberjs/dist/src/CucumberAllureInterface.js:74:33)
at attachRequestAndResponse (/Users/fguidobaldi/Repositorios/fury_qaautomation/features/steps/when.js:410:33)
at World.<anonymous> (/Users/fguidobaldi/Repositorios/fury_qaautomation/features/steps/when.js:176:7)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
I added plain Reporter code following the docs (https://github.com/allure-framework/allure-js/blob/master/packages/allure-cucumberjs/README.md), but it doesn’t work out.
const { CucumberJSAllureFormatter } = require('allure-cucumberjs');
const { AllureRuntime } = require('allure-cucumberjs');
function Reporter(options) {
return new CucumberJSAllureFormatter(
options,
new AllureRuntime({ resultsDir: './allure-results' }),
{},
);
}
Reporter.prototype = Object.create(CucumberJSAllureFormatter.prototype);
Reporter.prototype.constructor = Reporter;
exports.default = Reporter;
This code was working with v.2.0.0-beta.9 and Cucumber 6
Expected behavior I should be able to create new steps using newer versions of allure-js.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 18 (8 by maintainers)
Commits related to this issue
- introduce new cucumber allure world (fixes #475, via #491) — committed to allure-framework/allure-js by epszaw 2 years ago
Glad to know that you were able to find the problem! Let me know if I can help with anything, I’ll be looking forward for this!
Yes, I’ve reproduced the issue, still working on that. Will notify you as soon as I get any working result
Hi @lamartire! I created this repo with the minimum code to reproduce the issue. I created two branches to compare expected (with cucumber 6 and allure-cucumberjs beta.9) and actual (cucumber 8 and allure-cucumberjs beta.18) behaviors.
Please let me know if I can help you with anything else!
I’m working on PoC to reproduce this issue, I’ll send it as soon as I finish it.