A solution simplifies performance load testing for colocated teams. With project-based capabilities, so teams can quickly identify abnormal application behavior.
N/A
Parasoft SOAtest
Score 4.8 out of 10
N/A
SOAtest, from Parasoft headquartered near Los Angeles, California, is a load and performance testing tool.
N/A
Pricing
OpenText LoadRunner Professional
Parasoft SOAtest
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
LoadRunner Professional
Parasoft SOAtest
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
OpenText LoadRunner Professional
Parasoft SOAtest
Features
OpenText LoadRunner Professional
Parasoft SOAtest
Load Testing
Comparison of Load Testing features of Product A and Product B
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.
This is the go to tool for all the web service testing needs. You can do functional testing, regression testing, automate the testing and drive the data from external sources like a Excel spread sheet or an xml document and finally performance testing. It can get better in scenarios where the response is to be compared with UI, with more automation. The license cost needs to be considered when there are many open source tools out there in the market.
Fast and efficient execution of automated testing.
Built in Javascript that can be used to run test cases with a repository tool such as HP Quality Center. This will show the test results and allow the QA engineer to pass, fail, or set a test case to N/A.
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.
As always, this is not a free tool and you have to pay for license. There are many open source tools which can perform similar job with no cost albeit with less functionality and more head work.
There is still some more room for improving the automation which can include more UI level components to make life lot easier when comparing the response vs UI.
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.
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.
It has been of tremendous help as the ONE STOP TOOL to test the APIs end to end. Ease of use is great and their support staff is excellent. They always conduct brown bag sessions for us to learn about new features. Overall it has given us a great ROI considering how fast we can test and deliver to market.
