We performed a comparison between Eggplant Performance, OpenText LoadRunner Professional, 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."
"It provides clients with an understanding of application and system performance."
"It is actually a very good tool because it will support almost all, if not all, industry-standard protocols, and it is also equipped with very nice reporting capabilities, which is why I like it."
"When designing a workload model offers a good range of possibilities for creating goal-oriented scenarios, which helps us understand and meet SLAs."
"It has good protocol coverage."
"The stability of Micro Focus LoadRunner Professional is very high. It is the leading tool for stability."
"The capabilities and flexibility of the Controller, the ability to monitor the systems under test, and the comprehensive results Analysis which saves a great deal of time."
"Its variety of testing tools for different applications is of great benefit, as well as its integration capabilities with other testing and monitoring solutions."
"Enables us to test most of the products and projects that we have across all the different technologies, without having to look at other tools."
"It's easy to learn how to use it."
"When you are working in sprints, you need to have continuous feedback. ReadyAPI definitely helps in automating very fast and rapidly. We have less coding, and we can more easily define our assertions. We don't use it for full-blown performance testing, but normally if you are doing your functional testing, it gives you the request and response time. Anybody who is doing functional testing can see what the request and response times are and raise a flag based upon their business affiliates, that is, whether it is meeting their affiliates. You can identify this during functional testing."
"ReadyAPI's best features are user-friendliness, smooth integration with Postman, the speed of creating test cases, and integration with customer data."
"The most valuable feature has been the assertion as a test step as this has allowed us to increase the scope of testing and validation."
"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."
"The most valuable features are the integration with Jira and the test management tools."
"One of the features of ReadyAPI that's worth mentioning is that it allows you to parameterize. I'm working with more than two hundred resources, so I don't have to go and make a small change at each point every time. I have the option to just parameterize in one place for the changes to reflect everywhere. Another valuable feature of ReadyAPI is that it provides a customized environment. In my company, you work in different environments, such as QA, UAT, and LT, so the URLs for every environment are different. In ReadyAPI, you can customize your environment, set it up, then start working on it. Another feature worth mentioning that's offered in ReadyAPI is automating your test value as the tool allows Groovy scripting. In your test case, you can use a Groovy script that says that in a particular test case, you have ten resources, but you just want to exhibit five and that you don't want to exhibit the remaining five. You can write a small Groovy script that lets you execute just five resources out of the ten resources. I also like that ReadyAPI allows you to read the data from CFC and Excel. It also allows you to create or customize your data, but that only works at a certain point because every application has its specific data. ReadyAPI cannot generate every data, but when I'm posting and I want to generate a random name, such as a first name, I can do it in ReadyAPI. The tool also has many different features which I find valuable, including Git integration."
"The interface is ok and they have the ability to re-load tests so that you can reuse them."
"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."
"The tool needs to work on capture script feature."
"I also use the TrueClient feature for browser-based testing. I found the TrueClient feature to be a bit difficult to use and not very user-friendly for automating scripts."
"There should be more integration with more open-source platforms."
"The solution lacks some form of integration."
"The only scenario we see a complexity is when we have single-page applications where JavaScript is talking to the server and coming back. That's the only scenario where we find some difficulties."
"I would like to have better support for adding more users per load generator."
"The solution uses a lot of memory and then it dies. It's difficult to work with the solution sometimes when you run a scenario it dies. They need to make the solution lighter somehow."
"We still have some issues with integration with things like SiteScope which, obviously, being another HPE product should be very straightforward, but there are always issues around that."
"I don't like how they don't have a clear way to manage tests between multiple projects."
"It doesn't have connectors to the NoSQL database. This is one of the things where they do not have a very solid strategy today. Other solutions have an in-built mechanism where I can directly and easily connect. An API is more around a user submitting a request on the frontend. It then hits the backend, puts the data, and responds back. If I am hitting MongoDB or NoSQL databases, I do not have ready-made inbuilt solutions in ReadyAPI that can easily help me in automating it faster. In our organization, we deal with NoSQL databases, and therefore, we need Groovy. We just cannot have a connector from ReadyAPI to do that. I have to write Groovy scripts. If you have themes that are predominantly using MongoDB, it leads to more maintenance and support activity because we are introducing more code into our commission. In terms of additional features, it can have cloud support. This is one of the things where we are getting into cloud support. We'll see how it works, but it is one of the doubts that we still have."
"Can be improved by including an inherent feature for UI automation."
"Performance and memory management both need to be improved because other solutions use less memory for the same amount of data."
"There is room for improvement in ReadyAPI, particularly in the user interface."
"What needs improvement in ReadyAPI is its load testing feature because there was a hiccup when my team performed some load testing on the tool. My team had meetings with the ReadyAPI team and tried to get that issue fixed, but it still hasn't improved. This is a shortcoming of the tool, especially when you compare it with HP LoadRunner."
"The UI should be flexible. Currently, the UI isn't."
"ReadyAPI could improve by adding a conversion tool from one file type to another. Import support for multiple file types would be beneficial."
More OpenText LoadRunner Professional Pricing and Cost Advice →