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
List of dependencies and versions used on Microsoft Windows 10 machine:
cypress: 12.9.0
shelex/cypress-allure-plugin: 2.22.0
allure-commandline: 2.13.8
cypress-multi-reporters: 1.6.3
mocha-junit-reporter: 2.0.2
Node: 16.16.0
After upgrading to Cypress 12.9.0 and node 16.16.0 allure reports are not attaching screenshots for failed tests automatically
Pre-requisites -
shelex/cypress-allure-plugin is configured as per latest documentation
allure-commandline is installed on machine
Navigate to results folder after execution is finished, and verify that screenshots are saved inside 'screenshots' folder (This is happening properly for me as well)
allure-results folder is also created inside parent project folder
Navigate to results/allure-report folder and open index.html. In failed tests no screenshots attached
(Expected behaviour - To have failed tests screenshots attached in the report)
results/allure-report/attachment folder seems to be empty (Which was not the case with earlier version which i was using)
Note: I have not used or added any additional env variables which affect allure reports within cypress configuration file
And also seeing that if I try to change or modify path for allure results folder using env allureResultsPath within Cypress.config.json file, it is always defaulting to allure-results folder
Can someone please look into this issue, or provide suggestions to resolve this.
The text was updated successfully, but these errors were encountered:
It is not clear to me: what version of cypress-allure-plugin do you have in the end? The start of your message states it is 2.22.0, which was released back in Nov 2021 and I guarantee you it will not work with cypress 10+.
Hi Shelex, do you have any sample examples which are not using Cucumber. Also I have upgraded to cypress: 12.14.0
shelex/cypress-allure-plugin: 2.40.0
allure-commandline: 2.13.8
cypress-multi-reporters: 1.6.3
mocha-junit-reporter: 2.0.2
Node: 16.16.0
Steps to reproduce issue:
Execute tests in Run mode using command
npx cypress run --env allure=true --browser chrome --headed --spec 'test file path'
Fail one or 2 tests intentionally
Navigate to results folder after execution is finished, and verify that screenshots are saved inside 'screenshots' folder (This is happening properly for me as well)
allure-results folder is also created inside parent project folder
Generate allure report using command
allure generate allure-results --clean -o results/allure-report
Navigate to results/allure-report folder and open index.html. In failed tests no screenshots attached
(Expected behaviour - To have failed tests screenshots attached in the report)
results/allure-report/attachment folder seems to be empty (Which was not the case with earlier version which i was using)
List of dependencies and versions used on Microsoft Windows 10 machine:
cypress: 12.9.0
shelex/cypress-allure-plugin: 2.22.0
allure-commandline: 2.13.8
cypress-multi-reporters: 1.6.3
mocha-junit-reporter: 2.0.2
Node: 16.16.0
After upgrading to Cypress 12.9.0 and node 16.16.0 allure reports are not attaching screenshots for failed tests automatically
Pre-requisites -
shelex/cypress-allure-plugin is configured as per latest documentation
allure-commandline is installed on machine
Steps to reproduce issue:
(Expected behaviour - To have failed tests screenshots attached in the report)
results/allure-report/attachment folder seems to be empty (Which was not the case with earlier version which i was using)
Note: I have not used or added any additional env variables which affect allure reports within cypress configuration file
And also seeing that if I try to change or modify path for allure results folder using env allureResultsPath within Cypress.config.json file, it is always defaulting to allure-results folder
Can someone please look into this issue, or provide suggestions to resolve this.
The text was updated successfully, but these errors were encountered: