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
When using the JUnit reporter to output test results, failed suites are not accurately reported in the JUnit report. An entry for a failed suite in the report contains tests="0" failures="0" errors="0" skipped="0" time="0".
As a result, debugging test suite failures with our CICD is very difficult because the vitest run command fails but no information about the failure can be found in either the JUint test report or stdout and the CICD platform reports all tests as passing.
Reproduction
vitest run --reporter=junit --outputFile=./unitTestReport.xml
Hello @JR40159. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with need reproduction will be closed if they have no activity within 3 days.
Describe the bug
When using the JUnit reporter to output test results, failed suites are not accurately reported in the JUnit report. An entry for a failed suite in the report contains
tests="0" failures="0" errors="0" skipped="0" time="0"
.As a result, debugging test suite failures with our CICD is very difficult because the
vitest run
command fails but no information about the failure can be found in either the JUint test report or stdout and the CICD platform reports all tests as passing.Reproduction
vitest run --reporter=junit --outputFile=./unitTestReport.xml
System Info
Used Package Manager
npm
Validations
The text was updated successfully, but these errors were encountered: