From its initial versions, the JUnit testing framework introduced an XML file format to report the execution of test suites. Over the years, this XML format has become a de facto standard for reporting test results, broadly adopted in the xUnit family.
These XML can be processed by different programs to display the results in a human-friendly format. This is for example what build servers do. For example, Jenkins implements a tool called JUnitResultArchiver, which parses to HTML the XML files resulting from the test execution of a job.
Despite the fact that this XML format has become pervasive, there is no universal formal definition for it. JUnit test executors (for example, Maven, Gradle, and so on) usually use its own XSD (XML Schema Definition). For instance, the structure of this XML report in Maven (http://maven.apache.org/surefire/maven-surefire-plugin/)...
