Tricentis NeoLoad is an excellent performance testing tool. It provides developers and testers with:
- Automatic test design
- Test maintenance
- Realistic simulation of user behavior
- Fast root cause analysis
- Built-in integrations with the entire SDLC toolchain
Users like the solution’s many benefits, including:
- Plugins: With NeoLoad’s plugins, teams can reuse and share test assets and results from functional testing tools, analytics, metrics, and APM tools in order to catch performance issues early.
- Full tech stack support: The solution’s full tech stack support enables users to test mobile, web, and desktop apps.
- User-friendly: Users find Tricentis NeoLoad to be very easy to use and understand because the product has so many useful functionalities. It is very easy to use the front end and the UI is very good.
- Easy deployment: The deployment of the solution is simple, straightforward, and is not time-consuming. Installation is not complex at all. It only takes a few hours.
- Cheaper than competitors: Compared to other solutions, Tricentis NeoLoad is less expensive.
- Low-code: Tricentis NeoLoad offers users a low-code option for end-to-end performance testing, which is helpful for users who do not have a technical background.
- Mobile testing: The solution provides 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.
- Suitable for complex testing scenarios: With Tricentis NeoLoad, users have the ability to quickly script a load test scenario and to develop complex testing scenarios.
- Useful data insights: The data generates valuable information which provides a huge level of comfort in the given application at peak periods, and drives direction for future performance-oriented projects and goals.
- Great method for checking outcomes: When reviewing test results, it allows the stakeholder to understand them and to make changes based on comments or recommendations.
The solution’s design was built intentionally with 4 different components, each with a specific dedicated purpose:
- User part: Where users can create and enhance scripts while implementing things like pacing, think time, and error handling concepts.
- Servers: This is meant for service testing of API testing.
- Population: This allows users to plug scripts, create multiple populations, and perform bandwidth testing.
- Monitors. This is a server-side where credentials can be added to a database or server via SSH details.
Another valuable aspect of the solution is that compared to other performance testing tools, the codeless part (the dynamic value capture part of Tricentis NeoLoad_ is quite easy.
Users also like the solution’s runtime, which allows them to create scenarios, populations, low variation policies, load generators, and custom load profiles. Other functions include graphs, templates, check alerts, set alerts, check response time, etc.
Moreover, Tricentis NeoLoad develops the scripts to log your session when browsing test requests. It makes it really easy to build sample output scripts, as it provides the capability to speed up transactions at higher rates while recognizing main performance points. Also, NeoLoad has units that allow OS metrics to be collected from the location host and correlate the data to stack test results, and as the code modules are not used to collect these metrics on the host, it doesn't take much scripting work.
In terms of scalability, the solution can be used for smaller companies, but can extensively scale to also support very large ones with thousands of employees.
Tricentis NeoLoad helps users identify bottlenecks and memory leaks, which, in turn, helps increase hardware capacity and makes it possible to look at things on the software end, including scalability, reliability testing, and failure testing.
In addition, users report that the customer service and support are knowledgeable and fast. They have excellent community support as well. Tricentis NeoLoad provides great documentation and collaboration.
The solution’s API support is also good. It includes:
- Support for SOAP/REST
- Assisted design with Swagger/Open API import
- Highly efficient extractors for quick test design and fewer errors in scripting.
- Ability to test as code or GUI-based productivity.
Additionally, it has automated testing of API performance that offers:
- CI/CD automated API testing, dynamic load generation infrastructure, and auto pass/fail based on SLAs.
- Real-time test results for fast dev feedback loop if bottleneck is found.
- Non-regression API performance trends.
Its API-based applications allow users to:
- Test stand-alone APIs
- Test APIs within end-to-end tests.
- Dev, PO, QA, Ops share a common view of API performance.
- Have confidence in API and application speed and reliability.
Some of the features users like are:
- Excellent HTML reporting presentation.
- Effortless integration with other tools, like Jenkins.
- Script creation and management is very easy with their inbuilt components.
- Robust and reliable platform
- Great performance
- Simple GUI
While Tricentis NeoLoad has a great set of features and benefits, users still have some issues, including:
- Protocol limitation: Tricentis NeoLoad only supports three protocols: SAP technology, web-based HTTP, and Remote Desktop Protocol (RDP). What this means is If users have to simulate .NET application-based traffic, they won't be able to.
- Multiple users can’t work on the same application: With Tricentis NeoLoad, it is not possible to create multiple scripts based on the application and based on the projects, and then integrate them all into a single place. Instead, users have to import a script, one user has to log off, and the second user has to copy the script and improve it, which is time-consuming.
- Performance: If there is a high number of users on NeoLoad (around 6,000+), it may create some bottlenecks in the solution’s performance.
- Browser usage: With scripting in a different browser, sometimes there are compatibility issues and it doesn't generate the script properly.
- Application is heavy: Because of this, sometimes there can be some compatibility issues with computers that tend to have less RAM.
In summary, users are quite happy with this solution, which is one of the most popular systems for testing applications.