[TIP] skipped testcases not reported in JUnit XML

Robert Collins robertc at robertcollins.net
Tue Mar 22 16:11:52 PDT 2011

On Wed, Mar 23, 2011 at 4:35 AM, Pere Martir <pere.martir4 at gmail.com> wrote:
>> 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
>> project).
> Good point. However, if each test case is executed in a separated
> downstream job of a matrix job, the build result of the parent matrix
> job will be considered "failed"  if any of the downstream job/test
> case is skipped. This is actually what is happening to me.

One way to solve that is to aggregate the test results into the
parent; another would be to disable the 'find test results' in the
parent (which is appropriate if you don't expect it to run anything

More information about the testing-in-python mailing list