We changed our name from IT Central Station: Here's why
Get our free report covering Micro Focus, Micro Focus, Broadcom, and other competitors of Micro Focus LoadRunner Cloud. Updated: January 2022.
564,322 professionals have used our research since 2012.

Read reviews of Micro Focus LoadRunner Cloud alternatives and competitors

Performance Engineer at a tech services company with 10,001+ employees
Real User
Top 5
Affordable price and dynamic value capture is a valuable tool
Pros and Cons
  • "I feel that the codeless part, the dynamic value capture part is quite easy in NeoLoad compared to other tools."
  • "The SAP area could be improved."

What is our primary use case?

The primary use case is for web applications and also SAP GUI—not SAP Applications but the UI version of SAP. For both these areas, it was working fine from the NeoLoad side.

The solution has been moved to the cloud version.

How has it helped my organization?

The first benefit is that it's quite cheaper. In the market there are mainly three tools which dominate: JMeter, LoadRunner, and NeoLoad. JMeter is open source. LoadRunner is quite expensive but has quite good features. NeoLoad is competitively quite cheaper compared to LoadRunner, and it provides great features, except in some areas. For instance, it doesn't allow some SAP applications. There are some areas where it's a little bit tough but other than that, it's quite good.

What is most valuable?

I feel that the codeless part, the dynamic value capture part is quite easy in NeoLoad compared to other tools. JMeter is a little bit tough, but LoadRunner gives you many features. For any codeless value, it is easy to detect from the NeoLoad side.

What needs improvement?

The SAP area could be improved. Not the GUI applications, SAP log-on, or something like that. We can see features and use NeoLoad properly in all the normal SAP log-on areas. I haven't tried it, but I have heard that Citrix-based applications don't work properly in the SAP application. In those types of different areas, there could be more protocol flexibility.

If there is a high number of users on NeoLoad—like around 5,000 or 6,000—it sometimes feels like that might be a bottleneck for the performance. That could be improved. With more users, there shouldn't be any issues from the tool side.

With scripting in a different browser, sometimes there are compatibility issues and it doesn't generate the script properly. Those types of crashes could be removed.

For how long have I used the solution?

I was using NeoLoad six months ago because of some performance testing issues. Previous to using NeoLoad, we used LoadRunner.

What do I think about the stability of the solution?

The stability is good. It's quite reliable. Compared with a different browser, it sometimes creates problems and bugs. With the number of users increasing, sometimes the CPU and system where it was connected increases because of trade concurrency or something like that. That can be a little bit problematic. Other than that, things are fine.

Ongoing maintenance is not required. Whenever we have deployed the tools, if any version upgrade happens, we just check what the upgrade is exactly and someone on the deployment team connects the documents and everything. They check the document accordingly and update the version. It's not complicated.

We have roughly eight to nine performance testers, including the performance lead, the performance engineers, and the performance testers. Everyone will be running different projects. We'll be using the tool and running the performance testing based on the license and everything. The user count license will be ramping up the load. There are instances where multiple teams are using NeoLoad at the same time with different licenses. There has been no conflict error with each other, and we haven't seen a problem with different license things. Because we have two licenses, two tests can be executed parallel to each other.

What do I think about the scalability of the solution?

The solution is scalable. After the number of users increases to 5,000 or 6,000, we have occasionally found problems. Below that, things are fine and the response times are good.

How are customer service and support?

Tech support is okay. When we had 50 users, we reached out to the tech support team and within two to three days we received a response. The time took longer because it was a complicated problem. Response time is perfect.

Which solution did I use previously and why did I switch?

I previously used LoadRunner. One of the reasons we had to switch to Neotys was because it was quite cheaper, but I still prefer LoadRunner to NeoLoad.

How was the initial setup?

The deployment process is very straightforward. It's not complex. Only one associate deployed it, so not much effort was required.

What was our ROI?

There was no impact on the work that we used to do with performance testing when we moved to NeoLoad. Our normal performance testing was able to continue and it was going perfectly well. Return on investment was better because our deliverables were not getting impacted and it was cheaper, so return on investment increased a lot compared to LoadRunner.

What's my experience with pricing, setup cost, and licensing?

NeoLoad is cheaper compared to other solutions. There are no additional licensing fees.

What other advice do I have?

I would rate this solution 9 out of 10. I wouldn't give it a 10 because there are some issues that need to be resolved from the tool side.

Before using the tool, you need to understand the product you are going to design, the different types of performance applications that you are going to do performance testing with, and whether or not NeoLoad supports it. If yes, then go ahead. Otherwise, I would say go back to LoadRunner because whatever the application is, LoadRunner will support it.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
David Collier
Co-Founder at Nobius IT
Reseller
Top 5Leaderboard
Performance testing that should be part of your everyday application development lifecycle
Pros and Cons
  • "The most valuable part of the product is the way you can scale the basic testing easily."
  • "Third-party product integrations could be a little more slickly handled."

What is our primary use case?

The primary use case for clients is that they often have large application development teams and application development projects that they needed to scale. So, for instance, if they were developing a new banking website and they needed to check that the application that sits on that website was scalable from a few hundred concurrent users to many thousands of users, they could test the load response using LoadRunner.  

That is what LoadRunner does, it does the performance testing and measures load-bearing response.  

What is most valuable?

I think, for me, the most valuable part of the product is the way you can do the basic testing. You can create the test script and then simulate thousands of users very, very easily. Instead of having to have lots-and-lots of systems that would emulate users, you just needed a couple to emulate tens of thousands of users. So the scalability of LoadRunner while it was testing scalability is really valuable.  

What needs improvement?

To improve the product, I think the integrations could be a little bit more slick. It does handle a lot of great integrations, but then some of them can be a little bit clunky to implement. The integration with third-party tools needs to be stepped up a little bit.  

As far as other things that need to be added, it has changed quite a lot recently, and I have not had vast amounts of experience with the latest version. So I am afraid it would not be fair for me to go further in expounding on that question. Things that I talk about may already have been included.  

For how long have I used the solution?

I was a presales consultant and so I was kind of a technical consultant as well. I was working with the solution end-to-end for about seven years. My main focus was not LoadRunner for the entire time, but I gained knowledge of LoadRunner and I gave presentations about it. It has been about eight to twelve months since I last did anything serious with it. However, I am still familiar with the product.  

What do I think about the scalability of the solution?

The scalability is really very good. In some ways, it is the purpose of the product: testing by use of scaling loads.  

How was the initial setup?

The initial setup is pretty straightforward. But I have got to say, having worked on-and-off with LoadRunner over a period of time, I knew kind of instinctively how to set it up after a while. In other words, in my case, I would say it was simple. On the other hand, I think it the first time I tried to set it up it was a nightmare. After that, it was easy because I learned a lot about it. If I had to score it out of ten for initial setup with ten being the best, it would probably be seven-out-of-ten. It is not really going to be super easy for first-timers to deploy.  

What about the implementation team?

The deployment could take quite a while, even when I was used to doing it. Getting the software installed and running is pretty quick and that is not a problem. But creating the projects and creating the test scripts can take a little while. To get up and running and doing stuff within it, it is probably just around a week. Doing it professionally with the integrations and with all the correct testing scripts, it can take a month and more. It really all depends on the purpose and how you want to use it.  

What other advice do I have?

My advice to people considering LoadRunner is that if you are going to use the product, use it as part of your everyday application development lifecycle. Do not just use it right at the end, because it gives you some great insights during the development phase as well as at the end. You will end up writing cleaner application code with it. So bake the use of LoadRunner into your full application life cycle.  

On a scale from one to ten where one is the worst and ten is the best, I would rate this solution as between and eight and nine-out-of-ten. I could be slightly biased, having worked for the company that sells it. But it is a very good, professional solution. With the latest updates, it is very comprehensive and one of the best products of the sort. Let's say nine-out-of-ten because there is always room for improvement.  

Disclosure: I am a real user, and this review is based on my own experience and opinions.
QA Engineer at SSCGI
Real User
Top 20
Has good recording features but it should have the ability to customize reports
Pros and Cons
  • "I really like the recording because when I use the JMeter the scripting a lot of recording it takes me a lot of time to get used to. The BlazeMeter the recording is quick."
  • "In terms of improvement, I would like to have the ability to customize reports."

What is our primary use case?

Our primary use case is to create processes for performance. I created a one time function and implemented it for 1,000 users. 

What is most valuable?

I really like the recording because, with JMeter, the recording takes me a lot of time to get used to. With, BlazeMeter the recording is quick.

What needs improvement?

In terms of improvement, I would like it to have the ability to customize reports. 

For how long have I used the solution?

We have been using BlazeMeter for around two months. 

What do I think about the stability of the solution?

It is stable. 

What do I think about the scalability of the solution?

I implemented it for 1,000 users. 

How was the initial setup?

The initial setup was straightforward. I deployed it myself. Because I'm new to BlazeMeter it took two days to deploy because I needed to study it first also.

I deployed and also maintain it myself. 

Which other solutions did I evaluate?

I also evaluated JMeter and LoadRunner but I prefer BlazeMeter because of the speed and because it's easier to use. 

What other advice do I have?

I would rate it a seven out of ten. I would recommend it. 

I would like for it to be Windo-based. It should have the ability to be implemented into Windows applications. 

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Get our free report covering Micro Focus, Micro Focus, Broadcom, and other competitors of Micro Focus LoadRunner Cloud. Updated: January 2022.
564,322 professionals have used our research since 2012.