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
Describe the bug
cy.screenshot() captured screenshot successfully but when generated to allure-result, it got error (with size of 1KB).
The API function cy.allure().fileAttachment() worked well with same screenshot taken from cy.screenshot() (from path 'cypress/screenshots/specs/fileImg.png')
To Reproduce
Steps to reproduce the behavior:
Use cy.screenshot() to capture and automatically attach to report
Use cy.screenshot() to capture, get screenshot path, and attach to report with cy.allure().fileAttachment()
Expected behavior
Screenshot taken from cy.screenshot() should be generated successfully to allure-result and able to see in report view
Environment (please complete the following information):
Cypress version: 8.4.1
OS: Windows 10
Cypress Allure Plugin version: 2.18.0
Allure CLI: 2.13.8
The text was updated successfully, but these errors were encountered:
…ress #96, #101
feat: support nested mocha suites and properly handle error in hooks, address #99
feat: use cypress after:spec api to create sample suite and test with error, address #98
I could not exactly reproduce it, but anyway in v2.22.0 I have reworked attachments and it should be much reliable as utilize cypress after:spec event which now provides paths of screenshots. Could you please check it on your end?
Describe the bug
cy.screenshot() captured screenshot successfully but when generated to allure-result, it got error (with size of 1KB).
The API function cy.allure().fileAttachment() worked well with same screenshot taken from cy.screenshot() (from path 'cypress/screenshots/specs/fileImg.png')
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Screenshot taken from cy.screenshot() should be generated successfully to allure-result and able to see in report view
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: