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
Is your feature request related to a problem? Please describe.
We have many e2e-Tests, where each test consists of multiple nested describe-Blocks, each having several it-Blocks. This generates a report as shown in the screenshot below.
The stats in the upper right corner shows, how many tests succeeded or failed - except it counts each individual failing it-Block. Since one failing it-Block usually makes every consecutive Block in that test fail aswell, which multiplies the "failed" tests, although it's only the one test that failed.
Describe the solution you'd like
We'd like to have a stat that shows the number of succeeded and failed tests overall, to have the actual number of failing test scenarios on the report, which is of interest for he overall state of the application. Mockup added below.
Describe alternatives you've considered
We thought about implementing it ourselves, which would take quite some time as none of us really know the tool, so it would be full of hacks stuffing the information into the existing report.
Is your feature request related to a problem? Please describe.
We have many e2e-Tests, where each test consists of multiple nested describe-Blocks, each having several it-Blocks. This generates a report as shown in the screenshot below.
The stats in the upper right corner shows, how many tests succeeded or failed - except it counts each individual failing it-Block. Since one failing it-Block usually makes every consecutive Block in that test fail aswell, which multiplies the "failed" tests, although it's only the one test that failed.
Describe the solution you'd like
We'd like to have a stat that shows the number of succeeded and failed tests overall, to have the actual number of failing test scenarios on the report, which is of interest for he overall state of the application. Mockup added below.
Describe alternatives you've considered
We thought about implementing it ourselves, which would take quite some time as none of us really know the tool, so it would be full of hacks stuffing the information into the existing report.
Additional context
Current report:
Possible solution:
(Moved from adamgruber/mochawesome#350)
The text was updated successfully, but these errors were encountered: