Tricentis NeoLoad Reviews

We used it for putting the load on the system. For example, for a big sale of an online marketplace, we created the scripts with performance testing tools such as Neotys and LoadRunner. We used to search for a product and add it to the cart. We used to capture all this traffic through these tools, and then, we used to do the real-time testing. So, we used to simulate the real-world user scenario. For example, if the company was expecting around 20,000 users on a specific day, we used to simulate the volume of 20,000 users on the application. 

The deployment model depends on a client's requirements and licensing. If we have a sufficient budget, we always go for the SaaS model. If we have a limitation of licensing, then we prefer to go for on-premises deployment. We usually need to get support from the admin team to set up everything. We used to take care of this aspect so that the support team will be able to do things on our behalf, such as setting up things in their environment.

We can quickly do scripting with NeoLoad, which makes it easier to give timelines and meet them. We can easily tell a client that within this much time, we can provide the end-to-end scripts, and we'll be able to do the execution along with all the activities. 

The licensing cost is very less for NeoLoad. It is user-friendly and easy to understand because they have created so many useful functionalities. When I started working with this tool, we just had to do the initial assessment about whether this tool will be able to support our daily work or not. I could easily understand it. I didn't have to search Google or watch YouTube videos. In just 15 to 20 minutes, I was able to understand the tool.

We can easily do scripting with NeoLoad. We just have to understand the basic functionality to create a script. There is not that much effort that we have to put in. If I have to transfer knowledge to a new person or a beginner, he will also be able to pick it up quickly. 

LoadRunner supports multiple protocols, whereas NeoLoad supports only three protocols. With NeoLoad, we can go for the SAP technology, web-based HTTP, and Remote Desktop Protocol (RDP). If I have to simulate .NET application-based traffic, I won't be able to do that. So, protocol support is a limitation for NeoLoad. It should support more protocols.

One issue that we faced was that multiple users weren't able to work on the same application. We used to create multiple scripts based on the application and based on the projects, and then we used to integrate all of them in a single place. With NeoLoad, if you have to do this activity, to import a script, one user has to log off, and the second user has to copy the script and improve it, which is a time-consuming activity. These are the things that can block any further activity.

I have been working with this solution for 18 months.

I would rate it a nine out of 10 in terms of scalability. It is currently being used extensively. My organization is huge, and we have an employee count of more than 300,000. I wouldn't be able to provide the exact count, but for my project, 20 people are using this tool.

They usually clarify any queries or issues within three hours. They usually come back to us within three hours, which is as per our SLA, so that's good. I would rate them an eight out of 10.

Previously, we were using Micro Focus LoadRunner Enterprise. It is still in use. We haven't completely removed it. We switched because of the licensing and the time taken to create a script.

Neotys has taken some references from LoadRunner to create NeoLoad. So, in terms of functionality, NeoLoad and LoadRunner are quite the same.

The licensing cost of NeoLoad is lesser than LoadRunner. LoadRunner supports a higher number of protocols than NeoLoad. LoadRunner has more protocols for interacting with the application than NeoLoad. So, there are multiple things that we can simulate with LoadRunner, such as a desktop application or traffic for a banking domain.

If I have to create a script in LoadRunner, it usually takes around six hours, but if I do the same thing in Neotys, it usually takes around one and a half hours to complete everything. So, we can provide a deadline for deploying a script. Time is money, so NeoLoad is better in terms of time.

It is straightforward. You don't need much understanding from the installation perspective. You just need to download the .exe and install it. You just need the license, and if you are going for the trial version, you just upload the license. If you are going for a business license, you just have to tie up with them and reach an agreement. That's it. 

It is a one-day thing. One day is enough to complete the installation and the setup.

It was an in-house job. In terms of maintenance, we usually have an admin team and a security team to put patches, etc.

Its licensing cost is very less.

If you are dealing only with web HTTP, you can definitely go ahead with this solution because time is money. 

I would rate NeoLoad an eight out of 10.

One of our use cases, it was Oracle E-Business Suite (Oracle EBS) application testing. The other one was a migration project for SAP HANA. In those two use cases, we needed to perform benchmarking and increase the coverage from an end-to-end point of view rather than just focusing on the API endpoints. 

We had to automate some of the Oracle form-specific transactions using NeoLoad, as we wanted to expand the coverage. So, I used NeoLoad as a hybrid solution alongside JMeter. Initially, the majority of the volume was on JMeter, but for the Oracle forms usage, which was low, we utilized a low-volume license from NeoLoad.

NeoLoad is actually really good, mainly because they have a world-class support service.

NeoLoad can improve the correlation templates, which are specific to frameworks. There's room for improvement in that area.

In future releases, I think they definitely need a full UI revamp because I believe it's built on Java technology, which feels a bit outdated. I would like to see that being improved. Additionally, increasing the coverage of the correlation templates capabilities would be very useful.

I've used it across around three projects mainly because we provide the best options for our clients. We combine open-source tools with commercial ones. So, in two cases, we encountered limitations with JMeter, mainly because it doesn't offer off-the-shelf support for Oracle forms and SAP GUI. That's when we decided to introduce NeoLoad.

It is a stable solution. When I worked with this tool, the main pain point was finding solutions. They have some good documentation, but it could be improved because sometimes the feature I was looking for was already there, but it took me a while to find it due to the documentation. 

So, NeoLoad can improve the documentation. Otherwise, the tool itself is stable. For our purposes, using it with around 100 users, it was very stable.

It is a scalable solution. I have integrated NeoLoad three times in your personal projects. I would say the main feature that might lag for enterprise usage is the capability to manage scripts in a team environment. You should be able to maintain scripts across multiple users through a source code repository. I'm not sure whether NeoLoad fully supports managing Java programming-like stuff with ease through a source code repository. That might be one aspect that could make it more qualified for enterprise use. 

Other than that,  NeoLoad can support enterprise needs, but I'm not sure about the team environment support with a source code repository. But as for the tool itself, because we are using it at kind of an enterprise level, not extensively, but it caters to most of the requirements.

The customer service and support were good. The initial support I received from them was world-class. They treated the issues as their own, and I would rate it eleven out of ten. It was that good.

Positive

The initial setup is not that complex unless you try to use it against a complex application like Oracle Forms. Oracle always tries to encourage the use of its own proprietary performance testing tool. They make it harder for the clients to use other tools, pushing them to buy their own. That's when the complexity arises. Other than that, it's straightforward and very intuitive. 

As long as you have a basic understanding, it's not that hard to get started. Personally, I came from a JMeter open-source background, so transitioning to NeoLoad wasn't too hard for me.

Initially, we faced some configuration issues, and the documentation was a little lacking, but the support team was very helpful in resolving the problems and guiding me through the setup. After that, using the tool became a walk in the park. However,  NeoLoad can still improve certain aspects.

NeoLoad has a cloud solution, mainly for executing tasks, but the tool itself is an on-premises one. The main issue with these cloud providers is that they should come up with CNA, which is the security certification. Otherwise, people, especially in the government sector, don't want to use them. They are very conservative about security in New Zealand, so they prefer everything to be on-premises mostly. Cloud solutions, like Platform as a Service, are not easily embraced there; they prefer on-premises solutions. So, everything is on-premises.

NeoLoad now has a much more flexible licensing process. Earlier, it was hectic with people. Nowadays, licensing itself is a killer for most products.

For example, we purchased the Tableau license, and they had this on-premise licensing server setup, which is not working at all. So we had to ask them to give us a cloud license, and the discussion is still going on. They are trying to charge us additional stuff for Tableau. So our clients are now in a situation where they might abandon the product due to licensing issues, making it complex. People don't want to go through this. Really, it's easier to use the tool, but licensing itself takes a lot of unwanted complications.

So, with NeoLoad, we gave feedback and asked them to simplify the licensing model, and they came back with a better proposal.

If it weren't for the limitations in supporting Oracle forms and SAP GUI, I would never choose any other tool over JMeter. As for SAP GUI, we shouldn't fix anything unless it's broken, so I prefer sticking with JMeter. These commercial load test tools are insanely priced, especially the load test tools. 

That's why I appreciate that NeoLoad has come down with better, smaller licenses now. It's a good improvement. But I still think they are overpriced. This applies to all these tools, not just NeoLoad. If you look at them, they sometimes charge for virtual user hours, which I don't understand. When you buy a tool and a certain number of virtual users, you shouldn't be charged for hours of virtual use. Instead, you should be charged based on the number of virtual users, and the clients should be able to use it for the period they purchased the license.

Overall, I would rate the solution an eight out of ten. There are certain areas that need improvements in NeoLoad, like UI, correlation templates, and more.

We use Tricentis NeoLoad to test risk with API calls and make some small automation with the API calls using small Java scripts to take data from the file.

The solution is on-premises and we use a web dashboard which is SaaS but we use on-premise because we mostly work with the clients in its sensitive data that's required, like, only on-premise usage.

The solution is on-premises and we use a web dashboard which is Software as a Service. We prefer on-premise usage because we mostly work with clients dealing with sensitive data that requires on-premise usage.

The scalability, support protocols, and features of Tricentis NeoLoad made it easy and straightforward for us to complete the same tasks for our customers in the server cloud. We had to verify the certificate and attach the file within a protocol, which was a challenge in the server cloud.

From a functional perspective, the range of tools provided with Tricentis NeoLoad is perhaps the widest.

There is room for improvement with the support and community documentation as it can be difficult to find answers to questions quickly. 

I have been using the solution for six months.

The solution is stable. In the past six months, I have only encountered a few issues or bugs when the program crashed. I believe this may have been due to my own configuration settings.

The solution is scalable.

The technical support is not very good.

I previously used Cisco SMARTnet but the generators for reports were difficult to configure on the backend so we switched to Tricentis NeoLoad because it is more user-friendly.

The initial setup is straightforward. We deployed using the manual and did not integrate the solution with anything, such as the CID tool; it was only for small projects.

We used a 60-day trial with ten hours of work per month. The cost is increasing each year.

I give the solution an eight out of ten.

We have three people using the solution in our organization.

As long as the organization's requirements are met, I recommend Tricentis NeoLoad.

The support is very good. They have excellent community support.

The pricing is pretty good.

The stability is okay. 

There are still some glitches that they need to improve. We have given support feedback as well when we have some issues. They're very responsive and they do work to fix and improve issues. 

LoadRunner offers a full protocol, whereas, with this product, only a few of the protocols are supported - not all.

I've used the solution for five years.

We do occasionally deal with glitches. The previous versions are very stable. The newer versions have some glitches and sometimes it hangs, however, for the most part, it's okay.

There are issues around some protocol settings, like when we use encryption. When a person uses the banking application, the user and password are encrypted. We have issues with the encryption protocol. Lately, some settings may have changed and it seems to be working.

While it's a good solution, I cannot speak to the scalability.

The community support is good. Whenever we have an issue, they provide support to resolve it. If we need information about features, they help. Support is very good.

We use the solution as projects demand. We are a consulting company. Whatever the client has already purchased, we will use that. We work with all kinds of tools.

I don't have any details related to ROI.

I'm not exactly sure what the pricing is as it differs from client to client.

That said, LoadRunner is expensive and NeoLoad is less expensive whereas JMeter is free.

I'm familiar, for example, with LoadRunner. When you compare this with Load Runner, Load Runner is the best tool as it, number one, is very user-friendly when compared with the NeoLoad. It also supports the protocols. It is very mature, so people are very comfortable with it. The monitoring is good, and it has a lot of good features.

NeoLoad will not support all the protocols and it's not as user-friendly as LoadRunner. I use LoadRunner more than NeoLoad, and therefore am more comfortable with it.

I also am familiar with JMeter, which is an open-source option and therefore a free tool. In comparison, NeoLoad is a big tool and JMeter is quite small. With NeoLoad, you can get all kinds of reports, flexible reports and you can customize the reports as well. We can drill down on the reports if we want. That's not possible in JMeter.

NeoLoad is a good tool for banking or telecom applications. When compared with the LoadRunner, NeoLoad will support almost all necessary features including reporting. It is a good tool.

Overall, I would rate the solution at a six out of ten.

• Easy correlations
• User-friendly GUI
• All components in one place

It helped us to improve the performance of all our applications.

Almost everything about NewLoad looks good, but I would like to have an indication of the variables for error messages appearing in the error tab. This would help us identify the users triggering the errors.

I've been using it for a year.

We've had no deployment issues.

There have been no issues with the stability.

We have had no issues scaling it for our needs.

In my experience, customer service is good.

The times that I've contacted technical support have been good experiences.

I worked with HP LoadRunner in my previous projects. I started using NeoLoad when I joined a project that was already utilizing it.

I wasn't involved, but my colleagues have said that the initial setup is straightforward.

An in-house team implemented NeoLoad for the current project.

Compared to HP LoadRunner, NeoLoad is cheaper.

It's a good tool to use if you are not willing to spend lots of money on HP LoadRunner licenses.

It's got a number of valuable features, the best of which I think are the mobile testing capabilities. It allows for load testing to make sure users can experience apps properly and checks for performance issues on the server side.

I particularly like Neoload’s ease of use, built in monitoring and their extensive library of wireless devices and protocols. We are able to simulate various wireless communication standards such as 3G, 4G etc. with ease.

A lot of our customers are now using mobile technology, so it's provided us the platform and ability to do mobile testing, which in turn enhances their experience in our store.

NeoLoad’s lack of support for a complete protocol suite is somewhat limiting. While they do offer some protocols (Kronos, GWT V2.6) that others do not, they are not a one stop shop for protocol testing. Neotys is considered a forward looking company in the software performance testing world and legacy protocols such as RTE, SAP GUI and RDP are not included in their suite of protocols. I would like to see a more comprehensive offering of protocols with future releases.

I've used it for a little over a year.

No, not at all. This was probably the easiest part of it. iIt’s working out really well as it is not taking up much resource and it was very easy to install.

We didn't encounter any issues with stability.

No, but to be fair, we don’t have a very large license right now, so this hasn’t become an issue for us. If I plan accordingly, this shouldn’t be an issue over time either.

The questions that we’ve had for them, they have answered very quickly. The team here is very skilled and we've managed to resolve any issues we've encountered ourselves. But when we have reached out to them they have been very responsive and they've solved our issues quickly.

We haven’t completely switched over yet. We are also using HP Performance Center. We are starting to slowly migrate. The mobile capabilities and the cloud testing capabilities, HP are lacking. I think in the next three to five years we will totally migrate to Neoload.

We did it in-house.

We certainly have an ROI, but it is hard to put in to numbers. If I don’t do the testing, how much sales do I lose? Millions of dollars. I can definitely tell you it would be significant.

They have been very responsive. They have even made an on-site visit. It’s been very good, they have had recent turnover but they are managing the transition well and they have even had a top team member reach out to us.

In my company, we use the product on the cloud by just filling out and taking the subscription and then starting the application in our environment. In general, I am not aware of the technical areas associated with the product.

In Tricentis NeoLoad, there are some good options similar to what Apica offers. If you are planning extraction for eight or ten hours, NeoLoad can extract data from that particular time frame, which is something you can't do in Apica but is present as a good feature in Tricentis NeoLoad. With the tool, it is possible to compare NeoLoad test results against baseline and benchmark, and we can make the comparisons in the same window.

The debugging part of Tricentis NeoLoad takes time. Fixing the scripts takes time due to the problem with the debugging part. The debugging part of the product is an area that requires improvement.

I have been using Tricentis NeoLoad for a year.

My company uses the product on the cloud, so we have no issues with the tool.

At the moment, no one in my company uses the product. I used the tool when I worked with Vodafone's account, but at the moment, our company is not handling it anymore.

I have not contacted the support team of the product since I have not faced any issues with the solution.

The debugging part of Tricentis NeoLoad takes time. Fixing the scripts takes time due to the problem with the debugging part. The debugging part of the product is an area that requires improvement.

The solution is deployed on the cloud services managed by NeoLoad. Apache JMeter was also deployed on the cloud.

Not only for Tricentis NeoLoad but also any other tool would require some time to be installed.

Anyone can use the product, but it is important to create templates to focus on, especially if someone wants the business transactions to be easily captured in NeoLoad.

I rate the tool an eight out of ten.

We use Tricentis NeoLoad for performance testing across our product lines.

My company has a good experience with Tricentis NeoLoad, and what I like best about it is that it lets you generate loads from different geographies. The load generation agents getting placed on different geographies is a very good feature of the solution.

I also like that you can scale up Tricentis NeoLoad very quickly.

The general feedback on performance testing with Tricentis NeoLoad for all product lines within my company is good.

An area for improvement in Tricentis NeoLoad is its price, as it has a hefty price tag.

We've been using Tricentis NeoLoad for about three years.

Tricentis NeoLoad is a stable solution, and my company didn't have any problems with its stability.

Tricentis NeoLoad is a scalable solution. It tests performance, so it has to be scalable.

Technical support for Tricentis NeoLoad is good. My company hasn't had many issues with support. If I were to rate support from one to five, my rating would be four out of five.

Tricentis NeoLoad is a solution that's easy to set up. Deploying it wouldn't take much time, as deployment could be completed within just a few days.

Pricing for Tricentis NeoLoad could be cheaper because, at the moment, it's expensive. For a year, the solution cost us a lot of money, in particular, more than $50,000.

I'm using the latest version of Tricentis NeoLoad.

In my company, two people from the performance testing department use Tricentis NeoLoad.

My rating for Tricentis NeoLoad is eight out of ten.

My advice to others looking to start using Tricentis NeoLoad is that it's a good product, and it would be money well spent.

My company is into product development, and it's a user or a customer of Tricentis NeoLoad.