...

Text file src/github.com/joshdk/go-junit/testdata/cubic.xml

Documentation: github.com/joshdk/go-junit/testdata

     1<?xml version="1.0" encoding="UTF-8"?>
     2<!-- a description of the JUnit XML format and how Jenkins parses it. See also junit.xsd -->
     3
     4<!-- if only a single testsuite element is present, the testsuites
     5     element can be omitted. All attributes are optional. -->
     6<testsuites disabled=""
     7            errors=""
     8            failures=""
     9            name=""
    10            tests=""
    11            time=""
    12	    >
    13
    14  <!-- testsuite can appear multiple times, if contained in a testsuites element.
    15       It can also be the root element. -->
    16  <testsuite name=""
    17	     tests=""
    18	     disabled=""
    19             errors=""
    20             failures=""
    21             hostname=""
    22	     id=""
    23	     package=""
    24	     skipped=""
    25	     time=""
    26	     timestamp=""
    27	     >
    28
    29    <!-- Properties (e.g., environment settings) set during test
    30	 execution. The properties element can appear 0 or once. -->
    31    <properties>
    32      <!-- property can appear multiple times. The name and value attributres are required. -->
    33      <property name="" value=""/>
    34    </properties>
    35
    36    <!-- testcase can appear multiple times, see /testsuites/testsuite@tests -->
    37    <testcase name=""
    38	      assertions=""
    39	      classname=""
    40	      status=""
    41	      time=""
    42	      >
    43
    44      <!-- If the test was not executed or failed, you can specify one
    45           the skipped, error or failure elements. -->
    46
    47      <!-- skipped can appear 0 or once. optional -->
    48      <skipped message=""
    49	  />
    50
    51      <!-- Indicates that the test errored. An errored test is one
    52           that had an unanticipated problem. For example an unchecked
    53           throwable or a problem with the implementation of the
    54           test. Contains as a text node relevant data for the error,
    55           for example a stack trace. optional -->
    56      <error message=""
    57	     type=""
    58	     ></error>
    59
    60      <!-- Indicates that the test failed. A failure is a test which
    61	   the code has explicitly failed by using the mechanisms for
    62	   that purpose. For example via an assertEquals. Contains as
    63	   a text node relevant data for the failure, e.g., a stack
    64	   trace. optional -->
    65      <failure message=""
    66	       type=""
    67	       ></failure>
    68
    69      <!-- Data that was written to standard out while the test was executed. optional -->
    70      <system-out>STDOUT text</system-out>
    71
    72      <!-- Data that was written to standard error while the test was executed. optional -->
    73      <system-err>STDERR text</system-err>
    74    </testcase>
    75
    76    <!-- Data that was written to standard out while the test suite was executed. optional -->
    77    <system-out>STDOUT text</system-out>
    78    <!-- Data that was written to standard error while the test suite was executed. optional -->
    79    <system-err>STDERR text</system-err>
    80  </testsuite>
    81</testsuites>

View as plain text