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
To Reproduce
Run this spec with allure reporting enabled:
it('root-level test',()=>{cy.log('root-level test')})context('somecontext',()=>{before(()=>{cy.log('nested before hook')thrownewError('failure in a nested before hook')})it('nested test',()=>{cy.log('nested test')})})
Note how the resulting report only contains nested test, but that test contains the log step of root-level test (?) as well as the error message from the before hook. Commenting the throw line results in a report that correctly contains both tests
Expected behavior
I would expect to find root-level test in the report marked Passed, and nested test marked Broken/Defect
Environment (please complete the following information):
Cypress version: 12.14.0
OS: Windows 10
cypress-allure-plugin version: 2.40.0
allure2 version: 2.19.0
The text was updated successfully, but these errors were encountered:
I think the problem here is caused by test which is not attached to any suite and works just because cypress wraps everything in some "global" suite per file, however due to possible edge-cases I am not sure a proper solution could be found for such "hanging" tests without parent suite.
To Reproduce
Run this spec with allure reporting enabled:
Note how the resulting report only contains
nested test
, but that test contains the log step ofroot-level test
(?) as well as the error message from thebefore
hook. Commenting thethrow
line results in a report that correctly contains both testsExpected behavior
I would expect to find
root-level test
in the report marked Passed, andnested test
marked Broken/DefectEnvironment (please complete the following information):
The text was updated successfully, but these errors were encountered: