We performed a comparison between Apache JMeter, OpenText LoadRunner Enterprise, 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.
"The features that I appreciate are quite basic. It is easy to ramp up the threads and start calling the application. A lot of connectors can already be found within Apache JMeter, but we are not using the entire set because the integration between the customers and platform is based on HTTP. We are just going to produce lots of HTTP sequences."
"I like the fact that JMeter integrates well with other tools."
"The most valuable feature of this solution is that it is free."
"It's a free tool."
"We are using this for performance testing and some automation."
"It is easy to set up."
"It is very quick and user-friendly."
"The most valuable feature in JMeter is the Thread Group, which helps us to see whether the performance is good."
"We haven't had an outage since we started using the solution."
"The most valuable aspect of Micro Focus LoadRunner Enterprise is the overall support it has for a lot of different applications and defined domains."
"With Performance Center, the version upgrade is easy. You just have to roll out the new patch or the new version."
"The tool's most valuable features are scripting, correlations, and parameterization. Debugging is also easy."
"You can test a huge variety of applications, not just web-based systems, but SAP, Oracle, web services, pretty much anything out in the market place, but it's mobile-based testing."
"We implemented through the vendor, who used highly-skilled professionals."
"One of the most valuable features of this solution is recording and replaying, and the fact that there are multiple options available to do this."
"Our main use case for the product was load and stress testing. It helped us put the system under stress by injecting in multiple users, such as 5,000 users."
"A single platform for functional testing, load testing security, and service actualization."
"The interface is ok and they have the ability to re-load tests so that you can reuse them."
"When we are doing API testing we have found it to be very efficient to receive results. Additionally, you are able to do tests directly from the API."
"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 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."
"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."
"It is the best solution you can get across the globe for API, test automation, and API penetration testing."
"It's easy to implement."
"The stability could be a bit better."
"At present, if the number of virtual users increases beyond 10,000 when testing, then it results in a Java heap which causes the solution to crash."
"It has some proxy-based dependencies which require specific proxies to be set up or disabled, which causes problems."
"The UI needs some work. The first time I used JMeter, I couldn't record the full scenario to mimic the user experience. Since then, they have introduced some plugins and a third-party tool called BlazeMeter."
"The interface could be made more user-friendly."
"At times when we overload the application, it gets stuck...After the solution gets stuck due to overloading, we have to restart our computers. In short, the solution keeps crashing."
"You really need a technical team in order to really utilize the product."
"Both scalability and stability could be improved in Apache JMeter."
"Sometimes, the code is not generated when we record the scripts in the backend."
"In Micro Focus LoadRunner Enterprise, I need to spend a lot of time training people, while on other low-code or no-code platforms, I need not invest that much time."
"The debugging feature needs to include graphs."
"More real-time monitoring should be available for the system under test."
"We'd like the product to include protocol identifiers whenever a tester wants to test a new application."
"Micro Focus's technical support could be more responsive."
"When we have a new application, recording the application is a pretty tough task. We have tried multiple things. We do scripting or try to record with different settings and on different machines. We try to record multiple times, but we do not know why it is recording and why it is not recording. We do the same thing on different machines. It sometimes records, and at other times, it does not. That is one of the major concerns."
"I think better or more integration with some of the monitoring tools that we're considering."
"Better compatibility or more support for the older versions would be helpful."
"Can be improved by including an inherent feature for UI automation."
"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."
"Areas for improvement include the security files, endpoints, and process sessions."
"The initial setup could be less complex."
"Many users will consider this solution expensive compared to the layout. It is more expensive than other solutions."
"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."
More OpenText LoadRunner Enterprise Pricing and Cost Advice →
