JMeter script integration. This integration feature is a good approach provided by HPE. Sometimes, we need to run scripts developed in an open source tool like JMeter. Instead of spending time on creating new scripts, the scripts developed in JMeter can be uploaded and based on the protocol license because it is a DEV user protocol, it provides a valuable feature when integrated with StormRunner.
Monitoring and sample access to servers needs to be provided, so that we can explore this and keep up-to-date.
The licensed version / free edition needs to be configured with SiteScope or AppDynamics, which many customers might not have. The LoadRunner feature of Windows Resource Monitor should come in handy in such scenarios. It is not only for Windows-based monitoring but also for UNIX-based monitoring. Dependency on the other tools or HP tools (SiteScope) would be reduced.
It needs to be more mature.
The client breakdown is a separate report and is not part of the existing load test report. The client breakdown is basically the response time observed from different browsers. We need to take a snapshot and place it in the load test report and that is not available when the load test report is generated from StormRunner.
Also, for the VuGen Web protocol, it supports only 12.50 and above, which is tough and compatibility is lost.
More than a year and half
I did not encounter any issues during deployment, but there are not enough tutorials available for the TruClient protocol and also on the reporting side.
I have worked extensively on the various module supported by STRL2.1v and provided my suggestions/improvements/recommendation to the HP R&D Team
Customer Service:
Good
Technical Support:
The level of customer service / technical support is satisfactory, with a few times good.
For example, when trying to learn the monitoring feature of StormRunner, I requested access to the Web Tours application that is installed on the server so I could explore that feature in depth. However, access was denied (monitoring-only access was provided). My question was: When both the application and the tool belong to HPE, why was access denied?
The end user needs to have strong skills in any of the load testing tools, specifically if they already have experience with LoadRunner.
is there any work around for transactional grouping and Ip spoofing?