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
I want to structure the way report is shown over report portal. The way it currently works is Browser Name -> FileName (with File Path) -> test.describe -> tests
Now since the data is shown by Spec Name (File Name in my case), I'm having trouble reviewing the reports.
My folder structure is like this:
What I want is to have the clubbing of test cases based on this folder structure. So if page verification cases are executed, the structure should be like this:
features (shows all subfolders inside report portal with passed/failed cases)
If we drill down, pageVerification should have passed/failed cases visibility, and then if I go deep it should show tests related to dateRangeHistory.spec.ts inside pageVerification.
The current structure is like this on Report Portal:
Is there a way to achieve this by playing around with the plugin implementation, or is any other way possible?
The text was updated successfully, but these errors were encountered:
Hi @venom0107 !
Thanks for the ticket!
It's label for our internal triaging processes and means that UI team will check the issue (the UI team is responsible for js agents as well as for UI).
In fact I need some time to think about your request and check what capabilities Playwright's reporter system offers to us that can be used to address your request.
Hi Folks,
I want to structure the way report is shown over report portal. The way it currently works is Browser Name -> FileName (with File Path) -> test.describe -> tests
Now since the data is shown by Spec Name (File Name in my case), I'm having trouble reviewing the reports.
My folder structure is like this:
What I want is to have the clubbing of test cases based on this folder structure. So if page verification cases are executed, the structure should be like this:
features (shows all subfolders inside report portal with passed/failed cases)
If we drill down, pageVerification should have passed/failed cases visibility, and then if I go deep it should show tests related to dateRangeHistory.spec.ts inside pageVerification.
The current structure is like this on Report Portal:
Is there a way to achieve this by playing around with the plugin implementation, or is any other way possible?
The text was updated successfully, but these errors were encountered: