We performed a comparison between Eggplant Performance, OpenText LoadRunner Cloud, and ReadyAPI based on real PeerSpot user reviews.
Find out what your peers are saying about Apache, OpenText, Tricentis and others in Performance Testing Tools.
"We find the solution stable and scalable."
"It is not a conventional test automation tool. It uses optical character recognition (OCR) to identify objects. It makes it the best in the class."
"We don't have a big team of people that can watch the dials and check that everything is okay. We're doing a lot of the monitoring of our website and our product at the side of the desk. We need a solution that does a lot for us, and that's what Eggplant does."
"The usability and ability to integrate with other solutions is quite good. When I use it in on Azure, then Red Hat is the most likely solution I use. When I use AWS, then I tend to use Lambda functions. In either case, it works well and you can use it either way."
"The initial setup was straightforward."
"The most valuable feature is that you can create an infrastructure on-demand and do performance testing with it."
"The TruClient feature is the most valuable for us. An application with testing can only be scripted using TruClient, so it's part web-based, but it also has its own protocol combined with HTTP and HTML. So many other tools do not recognize this specific proprietary protocol. Using TruClient, we can still create scripts that cover everything that we need to cover."
"The TCO has been optimized along with the total ROI."
"The reports are very relevant to the customers’ expectations."
"The fact that the solution supports multiple protocols such as open source, VuGen, TruWeb, TruClient, and SAP is very important because these protocols help us to concentrate on what is really needed to produce performance tests. If something is not supported, you have to use other tools or find other ways of assimilating loads."
"The product supports a wide variety of technology compared to any other tool."
"The dashboards are very good and consolidate all of the tests that you are performing with the client."
"It's easy to automate for more data-driven testing."
"The two most valuable features we use are the functional test and the security test."
"The great thing about ReadyAPI is that it has a wide variety of functions. You can test any API that you come across. You are not limited to one type of API. It supports many APIs."
"The most valuable feature is being able to run each version for test suites."
"The most valuable features of ReadyAPI are its robust functionality and collaboration capabilities."
"Reporting is more robust than other products because test reports can be exported in multiple ways."
"The initial setup is straightforward."
"I'd like to see the ability to integrate the user experience through device forms like AWS device forms or source labs."
"Performance is one key area for improvement. It can be slower compared to other tools I've used."
"Its scripting features need improvement."
"The product price could be more affordable."
"I would like for there to be better integration with other tools so that when you do load testing you can also do a security check."
"It should have a feature to report with a 99.9 percentile success rate."
"An area for improvement is analytics on why response times are slow from certain countries."
"CI/CD integration could be a little bit better. When there's a test and if you see that there are high response times in the test itself, it would be great to be able to send an alert. It would give a heads-up to the architect community or ops community."
"We encounter hurdles while running the professional version for on-premise setup."
"There are three modules in the system that are different products packaged into one, and they can sometimes be difficult to figure out, so they should be better integrated with each other."
"The initial setup could be less complex."
"ReadyAPI could improve by adding a conversion tool from one file type to another. Import support for multiple file types would be beneficial."
"In terms of features, I have already raised different change requests on the ReadyAPI side. One of the largest functions I've requested is the validation of the payload for the REST APIs."
"Sometimes, if I changed something in ReadyAPI, it would not quickly pick up the change. It used to give me the same error repeatedly, and when I closed the application completely and restarted it, it would pick up that change."
"The overall scope of this solution is limited and could be improved."
"ReadyAPI could improve by having dynamic validation information."
"Can be improved by including an inherent feature for UI automation."
"ReadyAPI can improve because it is limited to only SOAP and REST services. They should update the solution to include more protocols so that other people are not limited to SOAP and REST services. Other than would be able to utilize it."
