jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin van den Bemt <mll...@mvdb.net>
Subject Re: Unit tests for known issues
Date Fri, 07 Jul 2006 10:44:40 GMT
Create a seperate testcase class and skip that. Add in the issue that there is a testcase that
needs 
to be reenable if someone is going to fix that issue.

Mvgr,
Martin

Jukka Zitting wrote:
> Hi,
> 
> Question to any JUnit gurus out there: Is there a standard way or a
> best practice for creating unit tests for known issues for which no
> immediate fix is expected? There are currently a few such tests in the
> Jackrabbit test suite, but because they just report as "FAILED", it is
> difficult to see whether the failures were caused by a recent change
> or if they are just known issues.
> 
> I think it is very valuable to have those known issue tests included
> in the test suite, but it would make more sense if they'd be reported
> as TODOs or just skipped unless explicitly asked for.
> 
> The TODO: blocks in Perl's Test::More handle this very nicely, but I
> don't know of any similar feature in JUnit except explicitly skipping
> the tests based on a system property setting.
> 
> BR,
> 
> Jukka Zitting
> 

Mime
View raw message