[
https://issues.apache.org/jira/browse/SLING-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari updated SLING-3762:
----------------------------------
Attachment: SLING-3762-002.patch
This patch should solve the errors you experienced. The additional changes are:
- I avoided to use some internal classes of JUnit which were not exported by
org.apache.sling.junit.core.
- I added org.apache.sling.junit.performance to the module containing
integration tests as a bundle to be installed before tests could be executed.
> Add annotation support to the PerformanceRunner
> -----------------------------------------------
>
> Key: SLING-3762
> URL: https://issues.apache.org/jira/browse/SLING-3762
> Project: Sling
> Issue Type: Bug
> Reporter: Francesco Mari
> Priority: Minor
> Attachments: SLING-3762-001.patch, SLING-3762-002.patch
>
>
> I added support for annotations for tests executed with the
> PerformanceRunner. These annotations allow you to define some methods in the
> test to be run before or after warm up or performance iterations of the
> performance test.
> This mechanism allow a user to write workflow control code directly in the
> test, instead of relying on a Listener to perform appropriate initialization
> and cleanup of test data.
> At the same time, the annotations I added play nice with the rest of the
> standard JUnit annotations. You can always use standard before and after
> annotations, and rules too. The patch contains a test which proves how the
> new annotations fit with the performance listeners and with standard JUnit
> annotations.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
