jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting" <jukka.zitt...@gmail.com>
Subject Re: Unit tests for known issues
Date Wed, 19 Jul 2006 20:45:35 GMT
Hi,

On 7/7/06, Jukka Zitting <jukka.zitting@gmail.com> wrote:
> 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?

Thanks for all the comments! I ended up solving the issue with system
properties set through the maven.junit.sysproperties settins.

Relevant parts in project.properties:

    maven.junit.sysproperties=JCR-320 JCR-325
    JCR-320=false
    JCR-325=false

And in DocumentViewTest:

    if (!Boolean.getBoolean("JCR-325")) {
        return;
    }
    // failing test case for JCR-325

This will disable the normally failing test cases for the known issues
JCR-320 and JCR-325, allowing the Jackrabbit test suite to return
success unless the known issue tests are explicitly enabled. This
makes the test suite more efficient in detecting problems caused by
recent changes. With this change we should be able to get back to
having zero test failures in svn trunk.

A developer who is working on fixing a known issue, can enable the
test case either by running "maven -DJCR-nnn=true test" or by setting
the JCR-nnn property to "true" in project.properties or a local
build.properties.

BR,

Jukka Zitting

-- 
Yukatan - http://yukatan.fi/ - info@yukatan.fi
Software craftsmanship, JCR consulting, and Java development

Mime
View raw message