[jira] [Updated] (SLING-2593) Improvement for the Sling performance tools
[ https://issues.apache.org/jira/browse/SLING-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-2593: Fix Version/s: Sling JUnit Performance 1.0.2 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 Fix For: Sling JUnit Performance 1.0.2 Attachments: performance_patch_2.patch, report_level_patch.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 was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-2593) Improvement for the Sling performance tools
[ https://issues.apache.org/jira/browse/SLING-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vazzolla-Popa Cristian-George updated SLING-2593: - Attachment: report_level_patch.patch Report level parameter at the PerformanceRunner level 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, report_level_patch.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
[jira] [Updated] (SLING-2593) Improvement for the Sling performance tools
[ https://issues.apache.org/jira/browse/SLING-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vazzolla-Popa Cristian-George updated SLING-2593: - Attachment: performance_patch_2.patch Added another parameter to the PerformanceTest annotation which tells the reporter how to write the results (class based as the legacy reporter or method based); modified the sling performance tests a little to make them run correctly with maven; added the part with method based reporting 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
[jira] [Updated] (SLING-2593) Improvement for the Sling performance tools
[ https://issues.apache.org/jira/browse/SLING-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso updated SLING-2593: - Description: 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 was: 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 4. Added the possibility to have parameters sent to test suite object, added a before suite and after suite method 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
[jira] [Updated] (SLING-2593) Improvement for the Sling performance tools
[ https://issues.apache.org/jira/browse/SLING-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cristian Vazzolla updated SLING-2593: - Attachment: sling_performance_framework_refactoring.patch The tests have been deleted from the base project as I have moved them in a separate project. Also the AbstractTest and AbstractPerformance classes have been deleted as after the refactoring they were not needed anymore. 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 Priority: Minor Attachments: sling_performance_framework_refactoring.patch, sling_performance_modification.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 -- 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
[jira] [Updated] (SLING-2593) Improvement for the Sling performance tools
[ https://issues.apache.org/jira/browse/SLING-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vazzolla-Popa Cristian-George updated SLING-2593: - Attachment: (was: sling_performance_modification.patch) 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 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 -- 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
[jira] [Updated] (SLING-2593) Improvement for the Sling performance tools
[ https://issues.apache.org/jira/browse/SLING-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vazzolla-Popa Cristian-George updated SLING-2593: - Attachment: sling_performance_modification.patch Added the SVN patch for the modification 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 Priority: Minor Attachments: sling_performance_modification.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 -- 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
