[
https://issues.apache.org/jira/browse/JCR-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575035#action_12575035
]
Thomas Mueller commented on JCR-1452:
-------------------------------------
> the test writer ... defines .. the reasonable parameter values
Sure. Regular regression tests and functional tests are usually quick and don't
need the 'scale' anyway. Slow tests (for example a 500 MB blob test) shouldn't
be run by default with 'mvn package', even if only this ensures the blob is not
fully loaded in memory. But why not run the same test with 50 KB or so when
using 'mvn package'.
> Maven build profile.
Yes, we probably need to do that anyway, to set the scale. I had no luck
convincing maven to set a system property. I have added the following line to a
TestAll.suite() method: System.out.println("### PROPERTY " +
System.getProperty("bla", "-")); and then run the test using "mvn -Dbla=xy
test" the result is "### PROPERTY -". Maybe a maven specialist can tell me what
I did wrong?
I think two scale settings are enough for now: 1) mvn package & install and 2)
daily CI build.
> 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.
