Test suite report renders inside another
See original GitHub issueTest suite report is incorrectly rendered inside of another.
Screenshot: here
Test run with params:
"jest ./test/e2e/ --maxWorkers=2 --no-cache --config=./test/e2e/jest.config.js --ci"
Reporters settings:
[
'default',
['../../node_modules/jest-html-reporter',
{
pageTitle: 'E2E tests Seznam Browser',
outputPath: 'coverage/report.html',
dateFormat: 'dd. mm. yyyy HH:MM:ss',
includeConsoleLog: true,
includeFailureMsg: true,
},
],
]
Backend:
- jest-html-reporter: 3.1.0
- jest: 26.0.1
- node.js: 13.8.0
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
The Convenient Way to View and Share Your Test Reports
Reports are rendered directly and can be viewed in the application once you hit the 'Show Report' button or select a report from...
Read more >Progress Report - Azure Test Plans - Microsoft Learn
View the progress each suite has made within a test plan and identify the areas ... This report is also rendered using the...
Read more >How to Test React Components: the Complete Guide
example: a component renders with the default props. integration testing: testing if different parts work or integrate with each other. Usually ...
Read more >"Test suite failed to run" does not report as a test failure in the ...
i hoped for a solution like in other junit runners or reporters: If a test run fails, because of an syntax error, the...
Read more >c# - Render a View during a Unit Test - ControllerContext ...
NET MVC 4 web application that generates large and complicated reports. I want to write Unit Tests that render a View in order...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Great catch! I will try to patch this
There is now a fix for this in v3.1.3