HeadSpin is a Digital Experience AI Platform that combines a global device infrastructure, test automation, and ML-driven performance and quality of experience analytics. HeadSpin is designed to empower engineering, QA, operations, and product teams to assure optimal digital experiences across all delivery channels throughout the development lifecycle.
N/A
LoadRunner Professional
Score 9.0 out of 10
N/A
A solution simplifies performance load testing for colocated teams. With project-based capabilities, so teams can quickly identify abnormal application behavior.
N/A
Pricing
HeadSpin
OpenText LoadRunner Professional
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
HeadSpin
LoadRunner Professional
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
HeadSpin
OpenText LoadRunner Professional
Features
HeadSpin
OpenText LoadRunner Professional
Load Testing
Comparison of Load Testing features of Product A and Product B
We have been using HeadSpin for our web and mobile application testing. It is an easy-to-use solution that provides detailed and in-depth analytics from the testing results. We also get a wide range of live networks and devices to perform the testing from HeadSpin. It has an inbuilt artificial intelligence engine that helps us to get real-time scenarios simulated, which is very helpful for finding performance issues and improving the overall quality of the applications.
Micro Focus LoadRunner and its suite of tools, specifically VuGen works wonderfully for us for all web, http/https and web service calls. We've been able to build tests for near any scenario we need with relative ease. As long as we have crafted up requirements for our scenarios / scripts to managed scope, we've had high success working with scripting and data driving. Our main tests are web service calls - typically chained together to form a full scenario with transactions measuring the journey or a similar (measure along the way) journey through a browser. For web services we will use VuGen and browser we've shifted to Tru Client I have had little-to-no experience scripting against a thick client where a ui-driven test would be required. I know its possible but quite costly due to the need to run the actual desktop client to drive tests. We've been fortunate enough to leverage http calls to represent client traffic.
HP LoadRunner with new patches and releases sometimes makes no longer support older version of various protocols like Citrix, which makes the task time-consuming when using older versions of LoadRunner for some of the cases. So it should support older version as well while upgrading.
Configuring HP LoadRunner over the firewall involves lots of configuration and may be troublesome. So, there should be a script (power shell script for Windows or shell script for Linux users) to make it easy to use and with less pain.
I would like to see the RunTime Viewer of Vugen in HPLoadRunner based on the browser I selected in the run-time configuration to make it feel more realistic as a real user.
Licensing cost is very high when we need to perform a test on application for a specific group of users.
Customer service is not that great. It's difficult to get hold of someone if an issue is supposed to be addressed on an urgent basis. No online chat service readily available.
Though LambdaTest was cheaper, it did not offer the deal devices and we wanted to be 100% sure that our app offers a perfect experience to all users. Simulators and emulators are not the technology we wanted to rely on.
Simplified the approach to test the mobile application on multiple devices from different vendors. This helped us to ensure the stability of the application in different environments.
In-depth analysis to understand the loopholes in the application design function. This helped us to improve the application design and overall user experience.
The scripts created with traditional web/http protocol are not robust thus re-scripting is required after most every code drop. Troubleshooting and fixing the issue takes more time therefore in most cases we do re-scripting to keep it simple and save time.
In ideal world you would rather spend more time doing testing than scripting in that case mostly you could use an Ajax TruClient protocol. This type of script will only fail when an object in the application is removed or changed completely. This way of scripting will save you more time and helps you maintain the scripts with less re-work effort on a release basis. On the long run you will have a better ROI when you use Ajax TruClient protocol for scripting.
