Note that there are some explanatory texts on larger screens.

plurals
  1. POproducing a correct and complete xml unit testing report (for Hudson)
    primarykey
    data
    text
    <p>I'm extending <a href="http://r-forge.r-project.org/scm/viewvc.php/pkg/svUnit/?root=sciviews" rel="nofollow noreferrer">svUnit</a> (a unit testing suite for R, part of <a href="http://www.sciviews.org/SciViews-R/" rel="nofollow noreferrer">sciViews</a>) so that it produces also output that can be read by Hudson. actually I already have something that does this, but it does not handle 'deactivated' tests.</p> <p>to see what I mean, have a look at the <code>protocol_junit.svTestData</code> method in the <a href="http://r-forge.r-project.org/scm/viewvc.php/pkg/svUnit/R/svTestData.R?view=markup&amp;root=sciviews" rel="nofollow noreferrer">svTestData.R</a> file.</p> <p>the problem is that I did not manage to find any definition of the schema accepted by Hudson and I did manage to convince a Java project to fail and error, so that its test suite would add a <code>&lt;failure/&gt;</code> and <code>&lt;error/&gt;</code> element inside of a few <code>&lt;testcase/&gt;</code> elements, but I did not manage to see what happens with a <code>@Ignore @Test</code> decoration.</p> <p>many others have asked this same question, for example <a href="https://stackoverflow.com/questions/442556">here too</a>, but in the end one gets to <a href="http://ant.1045680.n5.nabble.com/schema-for-junit-xml-output-td1375274.html" rel="nofollow noreferrer">this page</a> which is a good starting point but is not complete. for example, it does not mention the <code>&lt;error/&gt;</code> element I discovered by trial and error.</p> <p>I tried to read the source read by Hudson, but I did not find where to start.</p> <p>any hints?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload