Powerful and user-friendly load testing tool
Updated December 30, 2022

Powerful and user-friendly load testing tool

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Tricentis NeoLoad

Tricentis NeoLoad is typically used by quality assurance (QA) teams to ensure that web applications and APIs can handle the expected traffic and usage patterns. This is especially important for applications that are critical to the business, such as e-commerce websites or customer-facing applications that need to be available and responsive at all times. The scope of use for Tricentis NeoLoad can vary depending on the specific needs of each team. Some teams may use it for periodic testing to ensure ongoing performance and scalability, while others may use it as part of a continuous integration and delivery (CI/CD) pipeline to test performance at each stage of the development process.
  • Simulating realistic user behavior: Tricentis NeoLoad allows users to define the actions that simulated users will take when accessing a website or application. This can include clicking links, filling out forms, and accessing specific pages or resources. This allows organizations to test the performance of their applications under realistic conditions.
  • Testing the performance of APIs: Tricentis NeoLoad can be used to test the performance of APIs by simulating multiple requests and measuring the response times and error rates. This can help organizations ensure that their APIs can handle the expected traffic and usage patterns.
  • Identifying performance bottlenecks: Tricentis NeoLoad can identify performance bottlenecks by measuring response times, throughput, and error rates at various points in the application. This can help organizations pinpoint the specific parts of their applications that are causing performance issues and take steps to address them.
  • Testing the scalability of applications: Tricentis NeoLoad can simulate increasing loads on an application to test its scalability and identify the point at which it starts to degrade in performance. This can help organizations ensure that their applications can handle expected traffic growth and unexpected spikes in usage.
  • Generating detailed reports: Tricentis NeoLoad generates detailed reports that provide insights into the performance of an application, including response times, throughput, error rates, and other key metrics. These reports can be used to identify performance issues and track progress over time.
  • Ease of use: Some users find certain features or aspects of the interface to be confusing or hard to use. Improving the overall usability of the tool could make it more accessible and easier for users to get up and running with it.
  • Integration with other tools: Tricentis NeoLoad does not have many integrations with other tools. Adding more integrations with popular tools and platforms could make it easier for users to work with Tricentis NeoLoad as part of their overall workflow.
  • Mobile testing: Some users wish that Tricentis NeoLoad had more robust support for testing the performance of mobile applications. This could include the ability to simulate different mobile devices and networks, as well as the ability to test the performance of native mobile apps.
  • Cloud support: Tricentis NeoLoad does not have as much support for cloud-based applications and infrastructure. Adding more support for testing the performance of applications hosted in the cloud could be a useful feature for some users.
  • Advanced scripting capabilities: While Tricentis NeoLoad does offer some scripting capabilities, it would be nice to have more advanced options for customizing and automating load testing scenarios. Adding more advanced scripting capabilities could make it easier for users to create complex load testing scenarios.
  • Improved user experience: By identifying and fixing performance issues during testing, Tricentis NeoLoad has helped improve the overall user experience of our applications. This has increased customer satisfaction and loyalty, as well as increased revenue as users are now more likely to use the application or purchase products or services as a result of a better user experience.
  • Reduced risk of downtime: By identifying and fixing performance issues before they occur in production, Tricentis NeoLoad has helped reduce the risk of downtime. Downtime can be costly in terms of lost revenue and customer dissatisfaction, so reducing the risk of downtime has had a positive impact on overall business objectives.
  • Cost savings: We have been able to identify and fix performance issues before they occur in production, avoiding the costs associated with downtime, such as lost revenue and customer dissatisfaction.
  • Faster performance testing: Tricentis NeoLoad has enabled our teams to perform performance testing more quickly by automating the process of simulating user loads and measuring response times, throughput, and error rates.
Overall, Tricentis NeoLoad can help teams implement performance testing at scale by providing automation, collaboration, integration, and customization capabilities that enable them to test the performance of their applications more efficiently and effectively.
  • Automation: Tricentis NeoLoad provides a range of automation capabilities that can help teams automate the performance testing process. This can include automating the creation and execution of load testing scenarios, as well as the analysis of results. Automation can help teams test the performance of applications more quickly and efficiently, enabling them to scale their testing efforts more easily.
  • Collaboration: Tricentis NeoLoad provides collaboration features that enable teams to work together and share load testing scenarios, results, and insights. This can help teams coordinate their testing efforts and ensure that everyone is working towards the same goals.
  • Integration with other tools: Tricentis NeoLoad integrates with a range of other tools and platforms, such as Jenkins and GitHub, which can help teams integrate performance testing into their overall development and deployment workflow. This can enable teams to test the performance of their applications more consistently and at various stages of the development process.
  • Customization: Tricentis NeoLoad provides a range of customization options that enable teams to create and customize load testing scenarios to suit their specific needs. This can help teams tailor their testing efforts to meet their specific goals and requirements, enabling them to scale their testing efforts more effectively.
Overall, Tricentis NeoLoad provides automation, visual tools, and tracking and management capabilities that enable teams to streamline the testing process and reduce the time and effort needed to set up, execute, and maintain performance tests.
  • Test design: Tricentis NeoLoad provides a range of tools and features that enable developers to quickly design performance tests. This includes visual tools for creating and modifying test scenarios, as well as the ability to reuse and share test scenarios across teams. These tools and features help developers design performance tests more efficiently and reduce the time needed to set up and configure tests.
  • Test execution: Tricentis NeoLoad provides automation capabilities that enable developers to quickly execute performance tests. This includes the ability to schedule tests to run automatically at specific intervals or trigger tests to run based on specific events. Automating the test execution process helps developers save time and reduce the effort needed to run performance tests.
  • Test maintenance: Tricentis NeoLoad provides tools and features that enable developers to quickly update and maintain performance tests as their applications evolve. This includes the ability to update test scenarios as application features or functionality change, as well as the ability to track and manage changes to test scenarios over time. These tools and features help developers maintain their performance tests more efficiently and reduce the time needed to keep tests up to date.
One major difference between the two tools is that Apache JMeter is an open-source tool, while Tricentis NeoLoad is a commercial product. Although Apache JMeter is free to use and Tricentis NeoLoad requires a license to use, Tricentis NeoLoad is more feature-rich and user-friendly than Apache JMeter, with a more intuitive interface and a wider range of tools and features for creating and executing load testing scenarios. We are also using qTest (another Tricentis product) and the integration between qTest and NeoLoad was critical for us to take advantage of. Note, however, that Apache JMeter is still used by teams who need a free, more lightweight and customizable load testing tool.

Do you think Tricentis NeoLoad delivers good value for the price?

Yes

Are you happy with Tricentis NeoLoad's feature set?

Yes

Did Tricentis NeoLoad live up to sales and marketing promises?

Yes

Did implementation of Tricentis NeoLoad go as expected?

Yes

Would you buy Tricentis NeoLoad again?

Yes

Here are some specific scenarios where Tricentis NeoLoad might be well-suited:
  • Performance testing of web applications: Tricentis NeoLoad is well-suited for testing the performance of web applications under heavy loads. It can simulate multiple users accessing the application simultaneously and measure response times, throughput, and error rates to identify bottlenecks and potential failure points.
  • Testing the scalability of APIs: Tricentis NeoLoad is well-suited for testing the scalability of APIs. It can simulate increasing loads on an API and measure the response times and error rates to identify the point at which performance starts to degrade.
  • Identifying performance bottlenecks: Tricentis NeoLoad can be used to identify performance bottlenecks in web applications and APIs by measuring response times, throughput, and error rates at various points in the application. This can help organizations pinpoint the specific parts of their applications that are causing performance issues and take steps to address them.

Here are some scenarios where Tricentis NeoLoad might be less appropriate:
  • Testing the performance of native mobile applications: Tricentis NeoLoad is primarily focused on testing the performance of web applications and APIs. It does not have as much support for testing the performance of native mobile applications.
  • Testing the performance of applications hosted in the cloud: Tricentis NeoLoad does not have as much support for testing the performance of applications hosted in the cloud. It may be less well-suited for testing the performance of cloud-based applications and infrastructure.
  • Advanced scripting and customization: While Tricentis NeoLoad does offer some scripting and customization capabilities, it is not as well-suited for users who need more advanced options for customizing and automating load testing scenarios.