[TIP] skipped testcases not reported in JUnit XML

Robert Collins robertc at robertcollins.net
Mon Mar 21 12:04:45 PDT 2011

On Tue, Mar 22, 2011 at 5:43 AM, Pere Martir <pere.martir4 at gmail.com> wrote:
>> the easiest thing for jenkins is to use the java junit xml - extend it
>> tastefully as needed, and we can tweak the jenkins junit model as
>> needed. I need to update my jenkins tree though, I haven't touched it
>> since the git migration.
> Jenkin already handles this (I am using 1.401). The skipped tests are
> displayed as yellow bar.
> However, there is a bug in Jenkins. If all tests are skipped, Jenkins
> consider the build to be "failed" and displays a red icon. It
> complains "None of the test reports contained any result".
> This issue has been reported:
> http://issues.jenkins-ci.org/browse/JENKINS-7970

When we last discussed this kohusuke felt it was a good backstop
against broken configurations (no tests actually run is more likely to
indicate a broken setup than a successful test run on a brand new


More information about the testing-in-python mailing list