[
https://issues.apache.org/jira/browse/SLING-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467582#comment-13467582
]
Vazzolla-Popa Cristian-George commented on SLING-2593:
------------------------------------------------------
Hi Justin,
You were right I will use System.getProperty instead of getEnv and pass the
testsuitename from the Maven command line; thanks for this.
Regarding the use case, here is how I want to use the Sling performance
framework for our product performance tests.
- from the maven command line I set the testsuite name, I just download (not
build) a specific product release (for example version 1.0.0) and run all the
performance tests against it
- after that I store the performance results
- do this for different versions of the product(1.1.0, 1.2.0 and so on) that
are released during a time interval for ex. during the last 1 year (so the
product is not the same - similar case as with Sling jcr tests);
so be doing this I will be able to observe the performance results from the
version 1.0.0 to version 1.9.0 for example
- the only difference that I see comparing with the Sling jcr performance tests
is that by using the option to just download a specific version of the product
instead of building them, I do not need a new project for each test suite like
in the Sling tests where there is a project for jcr.resource-2.0.10, another
one for jcr.resource-2.1.0
- one more thing the performance tests that we are using are not unit tests,
are tests that will be run by having http requests so we can easily use the
same tests for different versions;
we will have some network latency but the team is ok with this approach and
they want us to have these kind of tests; also because of these variables I
would like to be
able to run the tests at a specific moment on various product releases
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: performance_patch_2.patch,
> 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
