Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'Failed Suites' are not recorded as having errored or failed in JUnit test report #3423

Closed
6 tasks done
JR40159 opened this issue May 22, 2023 · 1 comment · Fixed by #3997
Closed
6 tasks done

'Failed Suites' are not recorded as having errored or failed in JUnit test report #3423

JR40159 opened this issue May 22, 2023 · 1 comment · Fixed by #3997

Comments

@JR40159
Copy link

JR40159 commented May 22, 2023

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

N/A

Used Package Manager

npm

Validations

@github-actions
Copy link

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.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 26, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Jun 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants