Tricentis NeoLoad Reviews

There was a requirement from the project itself. So when I was onboarded to the project, I learned it myself and then continued on with NeoLoad.

It is for an Agile project. 

In the application, if it's a web application, I could see so many requests will be recorded. It will be a little clumsy with many request correlations and many things that need to be handled in JMeter since it consists of sub-requests and internal requests. So many things will be recorded, actually. 

But when it comes to NeoLoad, the maintenance will be easy. Then, whatever is required, those requests will be recorded. For example, in the same flow, JMeter, I could see maybe 35 to 40 requests. In NeoLoad, I could see only 20, but it won't miss any requests. It will bundle them as a single request. And then, it's pretty much straightforward for a performance tester, basically, to go through, and it is time-saving while using NeoLoad. The interface is easy.

The most valuable feature of Tricentis NeoLoad for us has been its ability to easily monitor all the load generators and configure the dynamics and data rates. Additionally, we can monitor individual loads and data directly within NeoLoad without needing third-party tools.

The tool has improved our application performance testing process by providing a flexible analysis tool. We can easily analyze various aspects of our application, such as long-term transactions and response times. The analysis feature allows us to drill down into specific files and identify any issues directly within the tool, such as high CPU or memory utilization.

The product is easy to use and has a user-friendly interface. A new user's learning curve is around 30-45 days. It is easy to integrate with other solutions. The tool integrates seamlessly with our CI/CD pipeline, including tools like Jenkins, allowing us to execute tests through non-GUI mode.

I have been working with the product for two years.

I have used Tricentis NeoLoad in two of my S/4HANA implementation projects, focusing on Transport Management and Finance & Tax modules. The objective was to assess the performance, stability, and scalability of the applications, ensuring solution capability to handle anticipated loads under both standard and stress conditions.

Encountering performance issues during our upgrades and post-production deployment, we explored available tools in the market and pinpointed Tricentis NeoLoad as a viable solution. Conducting a Proof of Concept (POC), we scrutinized problematic jobs and critical scenarios where processing time was expected to be minimal.
After the successful POC, we seamlessly incorporated Tricentis NeoLoad into our environments. The solution proved instrumental in the early detection of integration and access issues during the POC phase itself. Currently, we are actively leveraging NeoLoad for efficient execution of technical upgrades and comprehensive testing of major releases.

Tricentis NeoLoad is a standard tool for testing from an application coverage and reporting aspect. At our company, the tool is primarily used for performance testing to calculate the user-handling capacity of a system and analyze its stability. Tricentis NeoLoad also helps in finding the response rate, for instance, if you access a page will it takes two to three seconds or more. 

Tricentis NeoLoad has a highly intuitive UI. It's a low-code testing tool. The plug-in and out-of-the-box features are very easy to use. Tricentis NeoLoad offers an impressive reporting framework, which allows quick report extraction, which can be used in a Microsoft Word document and other summary reports for sending to our organization's clients. 

Reliable support is provided for Tricentis NeoLoad. The product also easily integrates with numerous other tools, and the vendor is focused on continuously improving Tricentis NeoLoad. 

I've primarily used it on-premise, not SaaS-based. However, the most concurrent virtual users I've handled with NeoLoad were around 8,000 users.

NeoLoad, especially, I like the comparison report that it provides. That's a really awesome thing. Apart from that, we have many options to control how you ramp up, how you ramp down, and what kind of things. The customization that we have. So those kinds of things really ease how testers complete the job at the earliest.

The graphs are very good because, from a performance test perspective, I always look at any graphs to compare how the users have been ramped and where, actually, the response times have decreased. Those kinds of graphs are all really very good with NeoLoad.

NeoLoad is more of a client-based tool. We generally use integrated APM tools, like New Relic and Dynatrace, but we don't integrate Dynatrace with NeoLoad.

We have integrated it with Jenkins. Recently, we have done for GitHub actions as well, which is really very good. Continuous integration with NeoLoad. The one feature that I haven't tried is on the cloud. NeoLoad cloud. Mainly because the funding was not there. We see a huge price on the virtual user limit and other things. So that's the reason we have stopped NeoLoad, and we jumped onto StressStimulus because it's cost-efficient, and we are almost getting the same features what NeoLoad offered. 

But still, my all-time favorite is NeoLoad because of the way the UI integration works. We are doing a lot of coding factors with StressStimulus if we want to execute anything. But with NeoLoad, we didn't have that. It was very easy for the testers. Anyone can pick it up at any point in time. That's how the NeoLoad tool was.

The solution is for continuous performance validation. The important thing is that it's not just for one load test and then forgotten. I try to integrate the performance tests into our pipelines, which helps us easily find or get quick feedback on whether the last change was graceful or not regarding performance. This helps developers who want feedback about functionality, whether a test case passes or fails. Performance can also be understood as test cases, and we often forget to give developers handy feedback about these issues. 

Usually, most of the nonfunctional requirements are forgotten in real projects. Mostly, it's not the job to handle unexpected behavior by NeoLoad. It's more important for me as a performance engineer to identify unexpected behaviors in the application. Sometimes it does not crash, but I can see a degradation of performance. When I see a degradation, it makes sense to inform the software developers in real-time so they can fix it before a crash happens. It is precautionary and helps the application to keep running.

The reporting features are great. It's very easy to analyze the monitoring data and the response times of the application. Most graphs can be configured with drag-and-drop, which is handy, and you get graphs suitable for reporting issues. Even managers find it easy to understand where the problems are located. Another big feature of Tricentis NeoLoad is the very good APIs they offer.

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. 

Our primary use case for Tricentis NeoLoad is performance testing and engineering, where we test or create scripts for different web-based applications on Tricentis NeoLoad. We also do multi-user testing on the tool and server monitoring to see how the servers behave. We also hook our CI/CD pipeline with Azure and Tricentis NeoLoad to trigger the test, then collect test statistics.

Tricentis NeoLoad has improved the organization I'm in as a performance testing tool that's easy to implement. My team found that Tricentis NeoLoad had no issues regarding the learning curve, including learning and using its features, versus LoadRunner, which had a long learning curve.

The result collation feature of Tricentis NeoLoad, including pulling the load generators or different remote machines from the cloud and using those with the test machines, was also fascinating and helpful to my organization.