My project requires usage of DevTest for performance testing. As of now, i am aware of virtualization for web services using DevTest. Could any one please share some detailed document on how to harness DevTest features for performance testing?
Just to be clear here , are you trying to use VS for performance purpose or DevTest as performance testing tool ?
if you want to use your VS for performance testing purpose.. then you should have performance VSE else functional VSE will limit the number of parallel threads it processes ..
I am willing to use DevTest as performance testing tool.
Performance testing is one of the core use cases for DevTest. I’m not sure how familiar you are with Service Virtualization. Here are some resources to get you started.
Performance Testing Solution Brief – This also includes APM but still a good overview of how SV works for performance testing whether you are looking at APM or not. You can download the doc here - Next-Generation Performance Testing with Service Virtualization and Application Performance Management - CA Technologies
Recent Webcast Recording and FAQ we did on API Performance Testing. This is posted on the this site –https://communities.ca.com/community/ca-devtest-community/blog/2016/04/29/qa-from-recent-webcast-on-performance-testing-with-ca-service-virtualization
Thanks for the info, but these links are more about integrating Service virtualization with performance testing. However, my purpose is to use DevTest for Performance/Stress testing (so far we were doing using HP LoadRunner).
It would be helpful, if anyone could share any doc or any such information for harnessing the features of DevTest for Load testing.
Hi Aman, unfortunately there is no deep and specific performance testing information published in the documentation. I would argue that it would be extremely difficult to provide specific guidance due to the high number of variables that exist within any single DevTest implementation.
Having said that, the basic concept from a Test Automation view is that one spins up Coordinator and Simulator servers under a Registry to execute the tests and generate the desired number of concurrent virtual users (the load). As a general rule, one Simulator can support up to 250 virtual users. The actual number supported by a Simulator is driven by the environmental factors (OS, RAM, CPU, etc) as well as the design and complexity of the test case. Multiple Simulators can communicate with a single Coordinator.
The number of virtual users, the spread of these users across the available Simulators, the length of time that the test executes, ramp patterns, and all the performance characteristics can be specified in the Staging Document. And, the test case or suites provide the actual test case execution steps.
The user's guide does offer some discussion about load and performance server sizing
System Requirements - DevTest Solutions - 9.1 - CA Technologies Documentation
Load and Performance Server Sizing - DevTest Solutions - 9.1 - CA Technologies Documentation
it is NOT a good idea to performance test using the OOTB Derby database. Follow the documentation and connect to an enterprise database.
As the documentation states, once you get the environment setup, run several load tests to find the optimum configuration.
You can do load/performance test in Devtest, by creating Staging doc where you can give your load pattern details in Basic tab. Apart from this, there are several options defined in staging doc which will help you in doing load test.
More details about staging document is available in below URL:
Building Staging Documents - DevTest Solutions - 9.1 - CA Technologies Documentation
Please go through System requirement and Load and performance server sizing documents shared by Joel and proceed with load test.