Tricentis NeoLoad

Score9.3 out of 10

44 Reviews and Ratings

What is Tricentis NeoLoad?

Tricentis NeoLoad is a solution for continuous performance testing software to automate API and application load testing. It was developed by the French company Neotys and acquired by Tricentis, along with the company, in March 2021.

Categories & Use Cases

Media

Code-less design — loops, conditions, and other drag and drop controls simplify test design creation, and JavaScript can still be used for extremely advanced cases.

CI/CD integrations — collaborate across dev, QA, operations, and business teams to create a standardized performance testing approach throughout the enterprise.

Real-time test results — analyze test results live to react to an anomaly before the test is over. And leverage in-depth test reporting when the test is completed.

Collaborate on test result as the test is running

1 / 6

Jignesh Patel

Software Engineer - Tech Lead in Information Technology at UPMC (10,001+ employees employees)

Use Cases and Deployment Scope

Earlier we use LoadNinja of smaerbear, VSTS load test solution etc. but have to spend so much time to build tool itself. Not easy to operate, manage and maintain. After get Tricentis NeoLoad in place; everyone's life easy. We spend quality time for performance tests rather than maintaining & managing tool. It's easy to use, quickly design the test, support good range of protocols. Tricentis NeoLoad have wide range of integrations and collaboration features. It has nice test as a code option and also support AI.

Pros

Test as Code Option
Integration with CI/CD and APM tools
Easy to use and maintain
Quickly design test and make changes
Scalable

Cons

AI feature for script development and improvement
Improve reporting feature with more customization
Lack of technical support
Stability issue - sometimes NeoLoad completely freeze

Return on Investment

Faster turnaround for bug validation
Should support other programming languages
Should easy to integrate with AWS, Azure pipelines
Smaller community limits on share ideas/issues/fixes

Alternatives Considered

Apache JMeter, LoadNinja, OpenText LoadRunner Professional and Azure Load Testing

Other Software Used

Splunk AppDynamics, Snowflake, Dynatrace

Verified User

Analyst in Quality Assurance (10,001+ employees employees)

Use Cases and Deployment Scope

We use Tricentis NeoLoad in our organization primarily for performance testing of web, desktop based such as SAP and API-based applications. It's become an essential part of our CI/CD pipeline, helping us ensure scalability and reliability of applications before every major release.Identified performance bottlenecks early in the development cycle.

Reduced manual effort and time spent in script maintenance

Pros

You can record a scenario once and reuse it across different test cases with minimal changes — thanks to dynamic parameterization and auto-correlation features.
Tricentis NeoLoad makes it easy to simulate real-world user behavior using its powerful GUI-based scripting interface.
We especially like the comparison feature to evaluate performance changes across builds or environments.

Cons

While Tricentis NeoLoad supports SAP GUI protocols, recording and maintaining test scripts for complex SAP transactions (like those in the OTC module) can be cumbersome.
For instance, we had challenges recording a VA01 (Sales Order Creation) transaction because of the dynamic nature of SAP screen fields and session handling. NeoLoad sometimes struggles to properly correlate or handle SAP’s SAPGUI Dynpro fields automatically.

Return on Investment

We have fully transitioned to Tricentis NeoLoad for our performance testing needs, and it has proven to be a highly reliable and effective solution.

Verified User

Engineer in Information Technology (10,001+ employees employees)

Use Cases and Deployment Scope

Tricentis NeoLoad is used extensively to load test individual applications and end to end integrated load tests. Neoload helps unearth underlying bottlenecks of the applications when tested with large volume of users, before application is presented to real users. There are multiple use cases where neoload is being leveraged. One such use case is mimicking real user navigations (Web page clicks) on high revenue generating applications and replay them with large volume to validate infrastructure capacity and to assess overall performance and behavior of applications

Pros

With Tricentis NeoLoad, we have control on the test dynamically. One can alter user count/volume even when test is in progress. This makes it a very cool tool as you can avoid running multiple tests eventually saves a lot of time.
Tricentis NeoLoad user paths are very well structured. End points can be identified and tweaked easily especially when a large list of endpoints are part of the neoload project.
Tricentis NeoLoad results comparison is one of the cool options. We can compare previous tests against the current one to see the exact delta between transaction metrics. This helps in gauging the application behaviour with changes deployed

Cons

Real Browser protocol - It is still in the budding state. Needs powerful controllers/LGs and incorporate best practices to include this in load test suite. It has a great potential to grow.
Tricentis NeoLoad dynamic infrastructure - Needs some improvement. One should be able to choose between regions/zones and no. of LG machines allocation can be handled automatically based on the script size/users
AI can be leveraged into Tricentis NeoLoad. For example, a model that can read existing APIs/user paths from publically available applications and can reproduce typical user behaviour without us having to write scripts.

Return on Investment

Right sizing of capacity before any peak sales event
Identification of bottlenecks in a stressed scenario
Failover tests during high volume on application makes the system ready for any unforeseen issues that may occur on prod

Alternatives Considered

Gatling Enterprise, Apache JMeter and OpenText LoadRunner Cloud

Other Software Used

Python IDLE, GitHub, New Relic

Verified User

Consultant in Engineering (1001-5000 employees employees)

Use Cases and Deployment Scope

Use of Tricentis NeoLoad by our customers, regular validation of the performance of their applications.GUI testing, API testing and continuous testingI test each time a new version is released, reusing the paths already recorded.Tricentis NeoLoad meets the high-load requirements of one of our customers whose applications are used very heavily over short periods.Tricentis NeoLoad can be injected locally, but also externally via the cloud.

Pros

High load testing
Coninuous testing
Rapid updating of user paths

Cons

Test on gui client
Import from other tools
Export to other tools

Return on Investment

ROI on tests that are carried out regularly
high licensing costs for short campaigns
Quick updating user path

Alternatives Considered

Tricentis Tosca and Tricentis qTest

Other Software Used

OctoPerf, Apache JMeter, Gatling Enterprise

Usability

Verified User

Contributor in Information Technology (1001-5000 employees employees)

Use Cases and Deployment Scope

I use Tricentis NeoLoad for Performance Engineering

Pros

Low Code
Future product strategy of neoload as code
SAAS Product is easy to adopt

Cons

More focus on Neoload As Code from product point of view
Integration with Opentelemetry
Quickly deliver new features to market

Return on Investment

Faster performance testing
High Reliability

BlazeMeter

Apache JMeter

OpenText LoadRunner Professional

Tricentis NeoLoad

What is Tricentis NeoLoad?

Categories & Use Cases

Media

Reviews