mikepenz/action-junit-report "No test report files were found"

By Daniel Zoghalchali·Latchkey

action-junit-report parses JUnit XML produced by your test runner. If tests did not emit reports, the path glob is wrong, or tests were skipped, there is nothing to parse.

What this error means

The junit-report step fails or warns with "No test report files were found" matching the report_paths glob.

Error: No test report files were found matching: '**/junit.xml'
##[error]No test report files were found

Common causes

Report path glob wrong

report_paths does not match where the runner wrote the XML.

Tests produced no reports

Tests failed to start or the reporter was not enabled, so no XML exists.

How to fix it

Emit JUnit XML and match the glob

1. Configure the test runner to write JUnit XML to a known path.
2. Set report_paths to that exact glob.
3. Run the report step with if: always() so it runs even when tests fail.

- run: npm test -- --reporters=jest-junit
- if: ${{ always() }}
  uses: mikepenz/action-junit-report@v5
  with:
    report_paths: 'junit.xml'

How to prevent it

• Confirm the test runner writes JUnit XML and point report_paths at it.
• Use if: always() so reporting runs on test failures too.

Frequently asked questions

Related guides

References

• GitHub Actions documentation
• Workflow syntax for GitHub Actions