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 14:22:40 GMT

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

Jukka Zitting commented on JCR-1452:

My point is that the "reasonable time" should be the standard time that the test runs.

These kinds of test cases typically verify the statement "issue X does not occur when operations
Z are executed N times (or for N seconds) in M concurrent threads", not the more absolute
statement "issue X does not occur". We can parametrize the test case for variables N and M,
but those selections should IMHO be up to the people who write the test, not to the users
of the test.

I'd be fine having different test suites that take different amounts of time (we're already
going to that direction by separating unit tests from integration tests), but it would IMHO
be much better if the parametrizations of those tests were consciously selected to match known
use cases instead of being based on an abstract scale parameter that has no direct relationship
to any of the tests.

> 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