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
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 runcommand 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.xmlSystem Info
Used Package Manager
npm
Validations