Submit a Feature Request
If you're unsure of which feedback category to select, please reference our guide in the changelog or use the "uncategorized" bucket so we can get your feedback to the right team.
1
XUnit test report schema support
Various flavors of junit xml are supported today (maven/gradle/etc) but one very common schema can not be imported by circle. https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/xunit/types/model/xsd/junit-10.xsd Currently circleci only handles a subset of this schema and inconsistently imports test results when it encounters elements it isn't expecting. Archiving the following test results * /home/circleci/test-results/a4fa6610-e512-40fa-8f8c-050be7289598.xml Failed uploading test results Error File: home/circleci/test-results/a4fa6610-e512-40fa-8f8c-050be7289598.xml had the following problems: * theNameOfSomeTest, invalid testcase element: rerunFailure * invalid top level element: rerunFailure * invalid top level element: rerunFailure * invalid top level element: rerunFailure * invalid top level end element: testcase * theNameOfSomeOtherTest, invalid testcase element: rerunFailure * invalid top level element: rerunFailure (there were a further 15 problems. Marathon for example outputs junit xml in this xunit style schema. https://marathonlabs.github.io/marathon/ It looks like the maven surefire plugin which CircleCi claims to support in the "Collecting test data" documentation will use similar xml outputs when necessary. surefire-test-report-3.0.xsd maven-surefire-plugin: rerun-failing-tests Gradle appears to use a slight variation of the surefire format when retries are enabled as well. They give a basic explanation to it in the docblocks of the reporter implementation code.
0
Load More