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.
What I found best in Tricentis NeoLoad is that it's better with scripting and load test execution in the load testing environment compared to its competitors. The tool has a better design, scenarios, and model, which I find helpful.
I also found the Result Manager a fascinating part of Tricentis NeoLoad because of the way it collates results and presents reports.
The straightforward implementation of Tricentis NeoLoad, including ease of use, is also valuable to my team.
Learning-wise, it's pretty straightforward and flexible because if the person has little knowledge of performance testing and the process, they can definitely easily grab the knowledge from NeoLoad.
I didn't like much of the support that you get from the Tricentis group unless it was after it integrated with Tricentis; the support is not that good.
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.
An area for improvement in Tricentis NeoLoad is its integration with third-party tools because, at the moment, it's a bit complicated. Per Tricentis, you can integrate Tricentis NeoLoad with different monitoring tools such as Dynatrace and New Relic, but that requires installing an additional tool to make that integration happen, rather than being able to pull in Tricentis NeoLoad from the different tools and servers, and make integration simpler and easier.
Connecting with the solution's technical support can be time-consuming. The turnaround time for a ticket raised is around 72 hours, which becomes an issue when working on a huge project in our company.
There were some features that were lacking in Tricentis NeoLoad, e.g. those were more into Citrix and other complicated protocols, which were supported easily by a competitor: Micro Focus LoadRunner.
We also need to look into how it integrates with other Tricentis products, because Tricentis did not have a good performance testing tool until now.
