Tricentis NeoLoad Reviews

• Graphical test creation
• Centralized test and results repository
• License management

With the simplicity of the test design interface, little domain knowledge is required for each scripted application, so we are able to generalize all of the performance testers to the point that any tester can update and execute any script instead of having individual domain experts who may be unavailable or busy. This has allowed us to keep more scripts updated easier than ever and keep a constant flow of performance tests in the pipeline, removing some dependence on human interaction.

If there was ever a way to bring the same level of ease to advanced scripting with Javascript to make it as easy as a regular test in NeoLoad, I would love to see it.

Some type of global test scheduler where different tests could be arranged on a calendar to automatically execute would help scheduling and provide visibility into the test environment.

Tighter integration with NeoSense and perhaps TFS integration to open defects for performance issues would also be nice.

I've used it for 12 months.

We've had no issues with deployment.

There have been no stability issues.

Running very large populations on one machine would max out NIC-level capacity far before CPU/memory would provide indication of bottlenecks, but running a distributed test alleviated this issue.

8/10

8/10

We previously used HP LoadRunner, and we switched due to cost, support competence, and the scripting interface.

It's straightforward to install and configure, but complex to convert scripts from a previous product to work in NeoLoad.

We implemented it in-house.

We've gotten 20% increase in tests-per-sprint and 35% decrease in time taken to create a script. We also have cost savings of over one million dollars annually.

Purchase a few extra licenses to allow for flexibility, utilizing the team server as much as possible.

• HP LoadRunner
• JMeter
• Appvance
• Rational Performance Tester

Take the time to see what NeoLoad can do when scripted from scratch and remember that it takes a bit of time to become an expert with the advanced features. Some complex actions may require written code, but there is very little that is actually impossible to test with NeoLoad. The limit is usually a function of experience with the software.

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.

Wasted time in low-end work (scripting) is greatly reduced with NeoLoad. It enables my team to record and modify test scripts very quickly. This reduces the effort for testing and enables the team to do more high-value work like analysis of results. We use external data analytics tools (Tableau) for result analysis. The export raw data feature in NeoLoad provides the extension with Tableau.

Performance testing is done by testing frameworks in which NeoLoad is the driver of load. The ability to extend the tool is crucial for organisations. Our test framework is composed out of NeoLoad as a centralised component surrounded by Tableau for analytics and AppDynamics for deep-dive diagnostics. This load test framework enables the team to more quickly test, find and resolve issues and system bottlenecks.

The weakest feature of most of the load test tools is result analysis. It is important we can customise graphs to visualise results in such a way that stakeholders can understand the outcome of testing. To be able to visualise results better, we extended NeoLoad with Tableau Software.

With Tableau, you can centralize performance related data in a database. Data can come from any tool, from log files or RUM tools and system utilities. Tableau provides you with the ability to connect to any data source, analyse patters and find bottlenecks more easily.  NeoLoad has made huge improvements over the last few years and finally has the ability to view the raw data (and not only aggregated results). This is fundamental for any type of performance engineering.  Aggregated results hide bottlenecks. 

Customer support is very good.

The price of the tool is competitive.

The features introduced in the recently released new version of NeoLoad fit really well into the DevOps way of working, further reducing the time for rescripting. This enables rapid delivery and lean ways of working.

It gives us the ability to quickly create a script.

We are able to create load test scripts quickly in a fast paced environment, which in turn helps us identify performance issues.

The support needs to be improved, especially when you are looking for a quick turnaround because of the fast-paced environment we work in.

We've used it for five years.

We've had no issues with deployment.

It's rare, but sometimes the application will shut down.

We've had no issues with scalability. You just have to add additional hardware as you increase the number of users.

8/10.

We have a very good partnership. They are always willing to work with us and help resolve any issues or concerns we have. They keep us updated on new releases and features that will be delivered.

7/10.

We previously used HP LoadRunner, but it was not easy to create scripts for a flex application.

The initial setup was very easy.

We implemented it with our in-house team.

As you add more protocols and monitoring it does get expensive.

We looked at HP LoadRunner, SmartBear LoadComplete, and Appvance.

It is very easy to implement and you can start using it fairly quickly.

There are several key features, including Jenkins integration, infrastructure monitoring, and results analysis.

Implementing this product has allowed us to increase the number of projects that get load testing, and the frequency by which we re-test our performance.

It needs improvements in the UI. It's currently not as friendly as it should be.

We've used it for seven years.

We haven't had any issues with deployment.

We have never experienced any isuses with stability.

The product has scaled very well up until this point.

The support from Neotys is very good. Responses are timely and come from experienced, knowledgeable load testing professionals.

We previously, and still use JMeter for some projects, in addition to Neoload.

The initial setup is straightforward for basic usage. The setup for higher volume load testing is more involved, but I wouldn't say complex, as should be expected for an enterprise class load testing tool.

We implemented it with our in-house team.

It's priced based on the numbers of VUs, virtual users, that your needs require. The free edition gives you 50 VUs. The pricing is fair for high-volume licensing. Cloud VUs can be rented on-demand for bursts of higher capacity testing needs without permanent purchase.

We looked at JMeter and Webload.

I highly recommend understanding load testing concepts before using any automation tool.

It is convenient to be able to keep up the pace in which the application code was delivered to us. Since we manage nearly 500-600 applications and we need to make sure they are tested, we wanted something robust with an option to check against previous baselines with minimal human intervention without sacrificing criteria.

We wanted something with less risk when incorporating or shifting scripts.

The fact that it loads from an external cloud is a plus as well.

It took just a few minutes to set up Neotys Cloud, as opposed to a few days with other solutions.

They are coming out soon with NeoSense. It's a hybrid between app management tools and a testing tool. This will be helpful for us because we'll be able to monitor applications within various different environments. This is precisely what we have wanted.

We've been using it for a year.

We had no issues with deployment.

We used to have only 50 online users. Later we moved to where we are.

We have used their gold support option. Yes, we have been happy. They usually answer between 36 and 48 hours for non-critical issues, and with critical issues they hold your hand.

We did it in-house.

We didn't negotiate the price. To give perspective, we went from spending three million dollars to 160 thousand dollars, which is a huge saving and good value.

One of our goals was to find a platform that would have the functionalities that we were used to while incorporating in other ones. ProLoad was a competitor, and one other (can't make out name).

We wanted it to support agile and devops, while being able to upgrade to a number of releases over the course of a day, so it was a fit.

The company really strives on experience, always making sure that I as a customer am happy. For example, my team at Dell had an issue with our new version, which we had just updated to. Another team used a different version which required different protocols, and there were discrepancies between the versions. The company found out that our errors were user errors, and helped us fix the problem.

I helped them in terms of product development since we at Dell told them requirements and they added that to product life cycles. So we are a customer, but told them some requirements we'd like to see.

We use Tricentis NeoLoad for performance testing purposes, like load testing and stress testing.

Tricentis NeoLoad is quite easy to use as compared to JMeter. The other valuable features of Tricentis NeoLoad include correlation, parameterization, load testing, and file parsing.

Tricentis NeoLoad crashes if an application contains more than 1,000 scripts. Tricentis needs to improve in this area, and the solution should run smoothly even if thousands of scripts are imported into it.

I have been using Tricentis NeoLoad for one and a half years.

I rate Tricentis NeoLoad a nine out of ten for stability.

Around 10 to 12 users are using Tricentis NeoLoad in our organization.

I rate Tricentis NeoLoad an eight out of ten for scalability.

The solution’s initial setup was easy.

Tricentis NeoLoad can be installed in ten minutes.

Tricentis NeoLoad is not an expensive solution, but it can be quite expensive if we need a license for load testing, depending on the organization level.

On a scale from one to ten, where one is expensive, and ten is cheap, I rate Tricentis NeoLoad's pricing a seven out of ten.

I would recommend Tricentis NeoLoad to other users.

Overall, I rate Tricentis NeoLoad a nine out of ten.

Used for performance testing of applications on QA environments as well as production environments. NeoLoad is best tool for testing in production without making many changes to the script or solution.

It helped in achieving the testing of on-premise applications, as well as cloud-based applications, without much difficulty.

• Integration of all components in one place.
• GUI-based requests
• Ease of use compared with other performance tools.

NeoLoad does not support Citrix-based applications. Neotys should take a look into this protocol.

No issues.

No issues. As far as Neotys NeoLoad, it is excellent in scalability.

The support is good. 

We started with NeoLoad.

The initial setup is easy.

The implementation was done in-house.

Our ROI is 100%.

The licensing cost is less compared to other licensing performance testing tools.

We tried JMeter, but due to its support (which we found subpar), we had to switch to NeoLoad.

You will love NeoLoad moving from open source and code-based performance tools.