You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Antonio Sanso (JIRA)" <ji...@apache.org> on 2013/12/16 16:29:07 UTC

[jira] [Commented] (SLING-2727) Allow PerformanceRunner to run tests provided by a factory method

    [ https://issues.apache.org/jira/browse/SLING-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849231#comment-13849231 ] 

Antonio Sanso commented on SLING-2727:
--------------------------------------

[~andrei.dulvac] sorry to bother you again but I have (finally ) tried to apply the patch but something seems to be missing e.g. IdentifiableTestCase et al

> Allow PerformanceRunner to run tests provided by a factory method
> -----------------------------------------------------------------
>
>                 Key: SLING-2727
>                 URL: https://issues.apache.org/jira/browse/SLING-2727
>             Project: Sling
>          Issue Type: Improvement
>          Components: Testing
>            Reporter: Andrei Dulvac
>            Assignee: Antonio Sanso
>            Priority: Minor
>              Labels: PatchAvailable
>         Attachments: performance_factory.patch, performance_factory.svn.patch, performance_reportlogger.patch, performance_reportlogger.svn.patch
>
>
> 1. I have modified PerformanceRunner to be able to run tests provided through a factory method annotated with @PerformanceTestFactory, when used with @PerformanceTestSuites. The method can be used (this is optional) on a "test case" object that is added to the ParameterizedTestList returned by the @PerformanceTestSuite method. If there is no @PerformanceTestFactory method, the behaviour stays the same as before. If a @PerformanceTestFactory exists, the PerformanceRunner adds all the test case instances returned by the factory to the testObjects list, instead of the test case itself. 
> Optionally, the test cases can implement an IdentifiableTestCase interface, which gives the ability to have custom names for tests running on different instances.
> The motivation behind this is that a suite can contain test cases that are different logically, but the test case should be able to be parameterized.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)