[
https://issues.apache.org/jira/browse/JCR-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575007#action_12575007
]
Thomas Mueller commented on JCR-1452:
-------------------------------------
> See also my comment
Do you mean "It should be up to each test case to know how long it needs to run
to verify some behaviour."? It's not so clear with 'fuzz testing'
(http://en.wikipedia.org/wiki/Fuzz_testing). As the wikipedia article states,
such tests have a high benefit to cost ratio. That's the reason to write them.
But they are not 'typical' functional tests that test just one issue.
A good example is a parser test. Generally a parser shouldn't throw
NullPointerException and such. It's quite easy to generate random statements
and check if the parser throws weird exception. Such a test may find 85% of the
bugs if run for 1 second, and additional 10% if run for 1 minute. If we have
10 such tests, it's also 85% in 10 second and additional 10% in 10 minutes.
It's good if you run such tests quickly before each checkin; but it would slow
down development if you always run them for one minute. But the nightly build
(or other CI installations) should run such tests for a longer time.
> 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.
