Converting test reports to JUnit format

This page relates to Recording test results with the CloudBees Smart Tests CLI.

Dealing with custom test report formats

The CloudBees Smart Tests CLI typically expects test reports to use the JUnit report format when passed into the smart-tests record tests command. This is the de facto test report format that is supported by many build/test/CI tools. However, if yours does not support this format, you must convert your reports into the JUnit report format.

This page and this page are probably the best-annotated examples of the JUnit report format. CloudBees Smart Tests uses the following information:

Must have

<testsuites> , <testsuite> , <testcase> are the structural elements that matter * Their name and classname attributes are used to identify test names
For a failed/errored/skipped test case, <testcase> element must have a nested <failure> , <error> , or <skipped> child element, respectively
While not documented in the pages linked above, file or filepath attributes on structural elements that point to the test source file path are required for file-based test runner support, most notably the file profile for unsupported test runners one you will most likely use if you are on this page!
time attribute on structural elements that indicates how long a test took to run (in seconds)

Nice to have

<system-out> , <system-err> that captures output from tests, preferably at the level of <testcase>
timestamp attribute on structural elements that indicate when a test has run, preferably on <testcase>

Examples

Here’s a bare-bones example of a test report that works with CloudBees Smart Tests:

<?xml version="1.0" encoding="UTF-8"?>
<testsuite time='0.050425' name="UserTest" timestamp="2020-11-18T19:22:24+09:00">
  <testcase time='0.025175' file="test/models/user_test.rb" name="test_should_save_user_with_name">
    <error/>
  </testcase>
  <testcase time='0.025250' file="test/models/user_test.rb" name="test_should_not_save_user_without_name">
  </testcase>
</testsuite>▼

Another one from Maven+Java+JUnit. This is not a file-based test runner, so the format is slightly different:

<?xml version="1.0" encoding="UTF-8"?>
<testsuite name="foo.FooTest" time="0">
  <testcase name="foo.FooTest.test3" classname="foo.FooTest" time="0.001">
    <failure type="java.lang.RuntimeException">java.lang.RuntimeException
    at foo.FooTest.test3(FooTest.java:7)
</failure>
  </testcase>
  <testcase name="foo.FooTest.test1" classname="foo.FooTest" time="0.001"/>
  <testcase name="foo.FooTest.test2" classname="foo.FooTest" time="0.003"/>
</testsuite>▼