Skip to content
Latchkey

CircleCI "Test results path not found" / store_test_results

A store_test_results step pointed at a path with no test report. The runner never wrote JUnit XML there, the path is wrong, or the report landed somewhere else - so CircleCI has no test data.

What this error means

The step warns that the test results path does not exist or contains no results, and the Tests tab stays empty. Test splitting by timings also degrades because there is no timing data to use.

circleci
Storing test results
Error: could not find any test results at path "test-results"
No test report files were found.

Common causes

Runner did not emit JUnit XML

The test command was not configured to write a JUnit-format report, so the path stays empty even though tests ran.

Wrong results path

The path: in store_test_results does not match where the runner actually wrote the report.

How to fix it

Emit JUnit XML and point the step at it

.circleci/config.yml
- run:
    name: Run tests
    command: npx jest --ci --reporters=jest-junit
    environment:
      JEST_JUNIT_OUTPUT_DIR: ./test-results
- store_test_results:
    path: ./test-results

Verify the report was written

  1. Add a run step to ls the results directory before storing.
  2. Confirm the runner's JUnit reporter output path matches store_test_results.path.
  3. Make sure tests actually ran and produced a report (not skipped).

How to prevent it

  • Configure a JUnit reporter for the test runner.
  • Keep the reporter output path and store_test_results.path identical.
  • List the results directory in CI to catch empty reports early.

Related guides

Tired of flaky CI? Latchkey auto-heals failed jobs and retries them for you. Start free →