You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for your work. It seems we have a stange behaviour with Allure Report Generation.
If I understand your explanation about https://github.com/Tallyb/cucumber-playwright/blob/master/README.md#to-choose-a-reporter, we can have only one reporter.
In dev mode, it is nice to have the progress execution in the console but to do that we need to disable Allure reporter.
In production mode (headless) we can agree it is not mandatory.
Is the workaround to use "npm run build" to check feature syntax and use linter ?
It seems an old issue exists here : allure-framework/allure-js#82
The workaround will be to uncomment the allure reporter and add a temp file OUTPUT.txt
What do you think about it ? Is it a right way to process ?
Not perfect because we can generate the execution flow display but not all information are easy to be readed at screen. Too man logs. I will investigate to reduce allure report logs.
export default {
requireModule: ['ts-node/register'],
require: ['src/**/*.ts'],
format: [
// 'message:e2e/reports/cucumber-report.ndjson',
'json:reports/cucumber-report.json',
'html:reports/report.html',
'summary',
'progress-bar',
'@cucumber/pretty-formatter',
'./src/support/reporters/allure-reporter.ts:OUTPUT.txt'
],
formatOptions: { snippetInterface: 'async-await' },
worldParameters: getWorldParams(),
publishQuiet: true,
};
```
Thanks for you work !
Best regards
Nicolas
The text was updated successfully, but these errors were encountered:
zepouet
changed the title
Allure Report Generation is disable by default
Allure Report Generation is disabled by default
May 31, 2022
Hello Tally,
Thanks for your work. It seems we have a stange behaviour with Allure Report Generation.
If I understand your explanation about
https://github.com/Tallyb/cucumber-playwright/blob/master/README.md#to-choose-a-reporter
, we can have only one reporter.In dev mode, it is nice to have the progress execution in the console but to do that we need to disable Allure reporter.
In production mode (headless) we can agree it is not mandatory.
Is the workaround to use "npm run build" to check feature syntax and use linter ?
It seems an old issue exists here : allure-framework/allure-js#82
The workaround will be to uncomment the allure reporter and add a temp file
OUTPUT.txt
What do you think about it ? Is it a right way to process ?
Not perfect because we can generate the execution flow display but not all information are easy to be readed at screen. Too man logs. I will investigate to reduce allure report logs.
The text was updated successfully, but these errors were encountered: