jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Klimetschek <aklim...@day.com>
Subject Re: Unit tests in jackrabbit-core
Date Wed, 20 Feb 2008 11:27:25 GMT
To refine my question:

- Where to put very specific tests for those nasty bugs?

This typically includes code paths that are not covered by the TCK/JCR  
api tests (in the JCR-1197 example it's a restore() followed by a  

The two solutions I see are:

a) a test class ala "SpecificTests" that contains test methods for  
many issues (eg. testFoobarFails(), testSomethingWrong(), ...)
b) one test class for each test, aka "FoobarFailsTest" with a  
testFoobarFails() method.



Am 20.02.2008 um 11:45 schrieb Alexander Klimetschek:

> Hi all,
> I wonder where to put a new unit test for jackrabbit-core. It shall  
> test https://issues.apache.org/jira/browse/JCR-1197 (caching problem  
> in ItemStateManager). Besides that, I will write other unit tests  
> for other issues as well.
> At a first glance, a simple place would be the main directory src/ 
> test/java/org/apache/jackrabbit/core, but it's quite full of tests  
> already. And it contains lots of tests there that are not included  
> in TestAll, ie. not executed during a "mvn test" (eg.  
> Concurrent*Test.java).
> - Shouldn't all tests be included in mvn test?
> - WDYT is the best place for new tests?
> - Shall I include them in TestAll?
> Thanks,
> Alex
> --
> Alexander Klimetschek
> alexander.klimetschek@day.com

Alexander Klimetschek

View raw message