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/02/12 09:23:13 UTC

[jira] [Created] (SLING-2729) Performance Testing suite: Modified ReportLogger to log the test case name

Antonio Sanso created SLING-2729:
------------------------------------

             Summary: Performance Testing suite: Modified ReportLogger to log the test case name 
                 Key: SLING-2729
                 URL: https://issues.apache.org/jira/browse/SLING-2729
             Project: Sling
          Issue Type: Improvement
          Components: Testing
            Reporter: Antonio Sanso
            Assignee: Antonio Sanso
            Priority: Minor
         Attachments: performance_factory.patch, performance_reportlogger.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.

2. Modified ReportLogger to log the test case name as well. Also, changed the method signatures so that it's clear what is being logged. This works with patch 1 to distinguish between different test case 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira