jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1452) Make use of jackrabbit.test.scale in test cases
Date Tue, 04 Mar 2008 16:15:41 GMT

    [ https://issues.apache.org/jira/browse/JCR-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575040#action_12575040

Jukka Zitting commented on JCR-1452:

> But why not run the same test with 50 KB or so when using 'mvn package'.

There's probably a reason why the test needs to run with 500MB blobs, otherwise it could just
as well always run with 50kB blobs. In many cases such a the test inherently needs lots of
time to produce meaningful results, and it doesn't make sense to scale them down just to make
them runnable.

> Maybe a maven specialist can tell me what I did wrong?

Maven forks the JVM when running the test cases, so you need to specify any system properties
in the <systemProperties/> configuration of maven-surefire-plugin.

> 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.

View raw message