You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2015/05/26 17:31:18 UTC
[jira] [Updated] (OAK-2908) infrastructure for running longevity
tests
[ https://issues.apache.org/jira/browse/OAK-2908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davide Giannella updated OAK-2908:
----------------------------------
Attachment: OAK-2908-annotation.diff
In [^OAK-2908-annotation.diff] an attempt to accomplish the task by
making use of the JUnit @Category and annotation.
You can mark any class or method with the new interface and then
run/enable all the longevity test by using a new profile: longevity.
Unfortunately it adds a considerable amount of time to all the builds,
doesn't matter what profile you choose, for analysing the compiled
test classes identifying what classes/methods have the annotation in
place.
> infrastructure for running longevity tests
> ------------------------------------------
>
> Key: OAK-2908
> URL: https://issues.apache.org/jira/browse/OAK-2908
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Davide Giannella
> Attachments: OAK-2908-annotation.diff
>
>
> Longevity tests could last days and should not run by default.
> Set up an infrastructure for keeping them in place but not running.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)