Package org.gradle.api.tasks.testing
Interface JUnitXmlReport
- All Superinterfaces:
- Configurable<Report>,- ConfigurableReport,- DirectoryReport,- Report
The JUnit XML files, commonly used to communicate results to CI servers.
- See Also:
- 
Nested Class SummaryNested classes/interfaces inherited from interface org.gradle.api.reporting.ReportReport.OutputType
- 
Field Summary
- 
Method SummaryModifier and TypeMethodDescriptionDecide to include or omit the system err log in the XML report.Decide to include or omit the system out log in the XML report.Whether reruns or retries of a test should be merged into a combined testcase.booleanShould the output be associated with individual test cases instead of at the suite level.voidsetOutputPerTestCase(boolean outputPerTestCase) Should the output be associated with individual test cases instead of at the suite level.Methods inherited from interface org.gradle.util.ConfigurableconfigureMethods inherited from interface org.gradle.api.reporting.ConfigurableReportsetDestinationMethods inherited from interface org.gradle.api.reporting.DirectoryReportgetEntryPoint, getOutputLocation, getOutputTypeMethods inherited from interface org.gradle.api.reporting.ReportgetDisplayName, getName, getRequired
- 
Method Details- 
isOutputPerTestCaseShould the output be associated with individual test cases instead of at the suite level.
- 
setOutputPerTestCasevoid setOutputPerTestCase(boolean outputPerTestCase) Should the output be associated with individual test cases instead of at the suite level.
- 
getMergeRerunsWhether reruns or retries of a test should be merged into a combined testcase. When enabled, the XML output will be very similar to the surefire plugin of Apache Maven™ when enabling reruns. If a test fails but is then retried and succeeds, its failures will be recorded as<flakyFailure>instead of<failure>, within one<testcase>. This can be important for build tooling that uses this XML to understand test results, and where distinguishing such passed-on-retry outcomes is important. This is the case for the Jenkins CI server and its Flaky Test Handler plugin. This value defaults tofalse, causing each test execution to be a discrete<testcase>.- Since:
- 6.8
- See Also:
 
- 
getIncludeSystemOutLogDecide to include or omit the system out log in the XML report. The default behavior is to have it.- Since:
- 8.8
 
- 
getIncludeSystemErrLogDecide to include or omit the system err log in the XML report. The default behavior is to have it.- Since:
- 8.8
 
 
-