JUnit Report Path Not Found - "No test report files were found"

By Kaveh Alemi·Latchkey

A test-results publisher (GitHub Actions, GitLab, Jenkins JUnit plugin) found no XML matching its path. Either the runner never wrote the JUnit report, or the publish glob points at the wrong directory.

What this error means

The report step fails or warns "No test report files were found" / "No files were found with the provided path" for the JUnit glob, even though tests ran. The XML was not produced or is somewhere else.

Error: No test report files were found matching
'**/junit*.xml'. Make sure your test runner is configured to
output a JUnit XML report.

Common causes

JUnit reporter not configured

The runner ran with its default reporter and never emitted JUnit XML, so the publish step has nothing to match.

Publish glob does not match the output path

The reporter wrote to one directory (e.g. reports/) but the publish step looks elsewhere (test-results/), or the run failed before writing.

How to fix it

Enable a JUnit reporter at a known path

# Jest
jest --reporters=default --reporters=jest-junit
# (jest-junit writes ./junit.xml by default)
# Playwright: reporter: [['junit', { outputFile: 'results/junit.xml' }]]

Match the publish glob to the output

# GitHub Actions
- uses: actions/upload-artifact@v4
  if: always()
  with:
    name: junit
    path: '**/junit*.xml'

How to prevent it

• Pin the JUnit reporter's outputFile and reuse it in the publish glob.
• Publish reports with if: always() so failures still report.
• List the output directory in CI to confirm the XML was written.

Frequently asked questions

Related guides

References

• GitHub Actions documentation