Bug #38569 for TAP-Harness-JUnit: Missing module failure not noted in XML output

Mon Aug 18 19:14:41 2008 ritter [...] strands.com - Ticket created

Subject:	Missing module failure not noted in XML output
Date:	Mon, 18 Aug 2008 16:14:08 -0700
To:	bug-TAP-Harness-JUnit [...] rt.cpan.org
From:	David Ritter <ritter [...] strands.com>

Hello, I'm not certain that this is a bug (it certainly could be user error). When I run a test where there is a module missing the Perl code fails to "compile". TAP correctly notes that error 255 has been returned and notes an overall result of FAIL, but this status does not seem to be propagated to the XML document generated by the JUnit TAP Harness. Is this a bug or is there a different way I should be initializing the test harness? Thank you for your help, Dave Ritter

Tue Aug 19 03:46:05 2008 lubo.rintel [...] gooddata.com - Correspondence added

On Mon Aug 18 19:14:41 2008, ritter@strands.com wrote: Show quoted text

> Is this a bug or is there a different way I should be initializing the > test harness?

Thanks for your report. This is definitely a bug. Similar issue is that when your test doesn't match the plan, the missing tests are silently ignored. I'll work on these two issues later this week, which will be followed by new release.

Tue Aug 19 03:46:06 2008 The RT System itself - Status changed from 'new' to 'open'

Fri Jan 02 18:35:46 2009 lubo.rintel [...] gooddata.com - Fixed in 0.25 added

Fri Jan 02 18:35:46 2009 lubo.rintel [...] gooddata.com - Correspondence added

This should have been addressed by certain changes in 0.25.

Fri Jan 02 18:35:47 2009 lubo.rintel [...] gooddata.com - Status changed from 'open' to 'resolved'