Test Summary Troubleshooting

Test Summary

The test summary in the UI is a place where we display some basic information about tests such as which tests failed, or what the slowest tests were. For basic configuration to set up the test summary you can view our docs. This document will outline some caveats, limitations, and common issues people run into when trying to get the test summary working.

Ensure Test Reports are in Supported Format

Currently, we support JUnit XML.

To note, there is not one official schema or standard for JUnit. Each test reporting tool may output its JUnit XML reports differently. This can cause some issues, in particular with our test-splitting feature.

To split tests by timing, each <testcase> element in the JUnit XML report should include the following attributes:

  • file : file path of the test file which the test case can be found in
  • name : name of the test case
  • time : time taken for the test case to complete
  • classname : class name of the test case 

Report Files Must be in a Subfolder

Test data must be inside a subfolder of whatever path is provided to store_test_results

If their path is set to test-results then the test report file or files must be in a subfolder of test-results, and not directly within it. For example: test-results/somefolder/report.xml


Subfolders Cannot be Hidden Folders

Test data subfolders cannot be hidden folders. test-results/.somefolder/report.xml would be ignored by our system.


Compressed Test Results Should not be Larger than 100 MB



Was this article helpful?
9 out of 34 found this helpful


1 comment
  • Thanks for this! Very useful article got me through some pain.

    I have one question: is it possible to display skipped and successful tests in the CircleCI test summary from a JUnit xml?

    Thanks again!


Article is closed for comments.