jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-1452) Make use of jackrabbit.test.scale in test cases
Date Tue, 04 Mar 2008 13:44:40 GMT

     [ https://issues.apache.org/jira/browse/JCR-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marcel Reutegger resolved JCR-1452.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5

Adapted various test cases to take test scale into account.

Moved MassiveRangeTest, MassiveWildcardTest to integration package. Those two test cases need
about 20s each to execute and scaling them down does not make sense.

ConcurrentQueryTest is now enabled when unit tests are run.

There still seems to be an issue with concurrently modifying a node using multiple sessions,
therefore I disabled ConcurrentNodeModificationTest.

> Make use of jackrabbit.test.scale in test cases
> -----------------------------------------------
>
>                 Key: JCR-1452
>                 URL: https://issues.apache.org/jira/browse/JCR-1452
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.5
>
>
> There are already a number of longer running test cases in jackrabbit-core, but they
are all disabled because they otherwise make building jackrabbit-core a very long task.
> Those tests should make use of the jackrabbit.test.scale property and per default (scale
= 1) run within a short time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message