You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (Jira)" <ji...@apache.org> on 2022/04/20 16:37:00 UTC

[jira] [Assigned] (JCRBENCH-3) Remove the jcr-benchmark dependency to jcr-tests

     [ https://issues.apache.org/jira/browse/JCRBENCH-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting reassigned JCRBENCH-3:
------------------------------------

    Assignee:     (was: Jukka Zitting)

> Remove the jcr-benchmark dependency to jcr-tests
> ------------------------------------------------
>
>                 Key: JCRBENCH-3
>                 URL: https://issues.apache.org/jira/browse/JCRBENCH-3
>             Project: Jackrabbit JCR Benchmark
>          Issue Type: Improvement
>            Reporter: Jukka Zitting
>            Priority: Major
>
> Currently the jackrabbit-jcr-benchmark component is designed as an extension of jackrabbit-jcr-tests. This gives the benchmark suite some setup code for free, but on the other hand makes it quite difficult to set up and use as an ad-hoc benchmark suite.
> I'd like to refactor the benchmark suite to consist of a generic test runner (with a main method so it can be run from the command line) and a set of standalone performance test classes that take an already initialized repository and have their own setup and teardown methods. The runner could take care of things like timing the test cases, measuring statistics over multiple test runs, and producing a report of the results.
> TestNG has some support for such use (much more so than JUnit), but it might be that we still need to implement at least some of the above features.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)