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 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."
"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 find the solution stable and scalable."
"This solution is SaaS based so we can utilize cloud technology, which is less time consuming and saves a lot of of money."
"OpenText LoadRunner Cloud eliminates the need for our own testing infrastructure when running tests."
"Both the professional and cloud versions of Micro Focus LoadRunner use the same scripting or programming to execute performance modeling operations. This feature allows users to use various programming languages such as Java, C, or C++, which can run within either of the two environments. This flexibility in the programming language is a strong point of the software."
"One of LoadRunner's standout features is its extensive support for various TechStacks and protocols."
"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 record and playback feature is the most valuable feature. It's all driven by the script, so it's a script-based tool where the background tracing starts. Java's background process does a lot of tracing. The process starts in the background. It sees what peaks of volumes that the process can handle. It's easy to use because it's script based, record, and playback. I"
"The TCO has been optimized along with the total ROI."
"The solution can scale."
"The two most valuable features we use are the functional test and the security test."
"The most valuable features of ReadyAPI are the scripting tools and the connectivity to external data sources, such as Excel and PDF files. There are plenty of useful features that are useful, such as automating flexibility and usability. Overall, the solution is easy to use."
"For anyone who does not have experience with automation, ReadyAPI provides a sense of comfort, especially for testers who find it hard to go directly into coding."
"It's easy to automate for more data-driven testing."
"The initial setup of ReadyAPI is straightforward."
"The initial setup is straightforward."
"The performance testing capabilities are very good."
"The dashboards are very good and consolidate all of the tests that you are performing with the client."
"Performance is one key area for improvement. It can be slower compared to other tools I've used."
"I'd like to see the ability to integrate the user experience through device forms like AWS device forms or source labs."
"In terms of new features, they can natively integrate with Chaos engineering tools such as Chaos Monkey and AWS FIS. With LoadRunner, we can generate load, and if Chaos tools are also supported natively, it will help to get everything together."
"Its scripting features need improvement."
"It doesn't provide custom reports. You can only use the default reports which contain irrelevant data or is missing data that we need."
"Their documentation is not technical enough for us. We would like to have much deeper technical documentation so that we can self-serve without constantly having to go back to them and ask."
"The support team provides delayed responses."
"One area of improvement in the software's support is the replaying of captured data within the development environment. It would be beneficial if the replay feature could accurately mimic what the actual application is doing for better analysis and testing."
"I don't know of any features that should be added. The solution isn't lacking anything at this point."
"Improvements to the reporting would be good."
"The overall scope of this solution is limited and could be improved."
"I don't like how they don't have a clear way to manage tests between multiple projects."
"Version control does not work well."
"To generate a test suite in API, I had to create a separate one each time because otherwise it was just override the test. Each API had to be added separately. I thought I could just have one and then create different methods, but I had to add each API separately to create the test for that. That is an area that could be improved."
"There is a lot of room for improvement, mainly from the point of view of integrating ReadyAPI into the CI pipelines, and also the scripting aspect into Bitbucket."
"Performance and memory management both need to be improved because other solutions use less memory for the same amount of data."
"There are lots of options within the solution, however they are not upfront or user-friendly."
"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."