Allure-playwright framework creates an unexpected custom field for Suite on generating a report #2971
Unanswered
vpanfilovaexsoft
asked this question in
Questions & Support
Replies: 1 comment
-
Is there any way to access custom fields via allure-playwright? To awoid the issue we changed our structure and now this functions is not enough to keep the tree. Allure also has "component" field by default, but there is no allure.component() funtion in allure-playwright |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When a allure-framework is used and a tree is generated in the autotest code, it works as intended if you creates Suite by yourself or when Suite is not next step in the tree:

E.g. you have the tree Feature > Story > Epic > Suite or leaves only Feature > Story in the code the folder tree would be generated as explained in the code
but the issue arises when you create a Feature > Story > Epic tree in the code. When the report is generated, it automatically creates an additional custom field for Suite named by your repository path for the file with tests (regress/header/header_3dot_menu.spec.ts)
Here is the video how it works:
https://share.zight.com/JruYLR9K
I'm not sure if this is a feature or not but Allure support tells it's the issue on framework side and only affects Suite
Beta Was this translation helpful? Give feedback.
All reactions