[
https://issues.apache.org/jira/browse/SLING-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466538#comment-13466538
]
Vazzolla-Popa Cristian-George commented on SLING-2593:
------------------------------------------------------
Hi Antonio,
If we keep the old format which was class oriented we will have a log report
per class, so what happens in the new approach in the case we have
more than one test method in a class ? I think we need to add at least the
method name in the test report even if we keep the report in some way similar
to the one that was used before or maybe come with some type of report that
would be between the two .
Also I'm not sure that a user would expect the performance framework to
correctly report the results just when using the verbose flag for the case in
which he
has multiple test methods in a class, what do you think ?
Regards,
Cristian
> Improvement for the Sling performance tools
> --------------------------------------------
>
> Key: SLING-2593
> URL: https://issues.apache.org/jira/browse/SLING-2593
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Reporter: Vazzolla-Popa Cristian-George
> Assignee: Antonio Sanso
> Priority: Minor
> Attachments: sling_performance_framework_refactoring.patch
>
>
> Added a few improvements to the Sling performance testing tools:
> 1. Added the possibility to run each test method in a class as a performance
> test; until now a test was represented by a class (for each new test you had
> to add a new java class)
> 2. Added a PerformanceTest annotation that is used to discover the test
> methods in a java class
> 3. Added the possibility to provide with the PerformanceTest annotation a few
> configuration parameters for the test like the warmup time, run time , warm
> up invocations or run invocations; by default the warmuptime and runtime are
> used but a user can choose not to count on the time but to prefer setting the
> number of test invocations that he wants to be made during the test run
> 4. Created a new maven project that contains only the sling performance tests
> and left the framework(tool) related part in the base project as we would
> like to use the framework for performance testing in other projects also
> 5. Added the possibility to have parameters sent to test suite object, added
> a before suite and after suite method
--
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