Tricentis NeoLoad Reviews

We are primarily testing APIs but also testing the UI in some cases. In my last job, I also developed a plugin to enable NeoLoad to measure the end-user experience. If you have a modern web application, you usually only exchange JSON files between the client and the server. On the client side, you will render the JSON information to an HTML side or a dynamic DOM structure.

NeoLoad is used for testing the response time, which is not the same as the time it takes for the user to see the page. When the JSON document arrives on the client side, the client has to render the information. If you are considering the user experience from the end user's perspective, you are not interested in how long it takes to get the JSON. You want to know how long it will take to get the JSON and see the information on the page.

NeoLoad can't do this because it does not render the data from the server. The browser engine uses considerable RAM, so we cannot simulate many users simultaneously. We enabled NeoLoad to control a typical test. For example, a QF Test like Robot Framework tests the web UI. It starts and renders the application to measure how long it takes to see some special information on the page. 

These response times are fed into NeoLoad through a data exchange API, enabling us to visualize the actual user experience inside NeoLoad. That's NeoLoad's primary advantage. It has incredible APIs to implement special additional features or plugins you need for special applications.

NeoLoad helped us to transition from load testing to continuous performance measurement. It is integrated into our CI/CD pipeline. We implemented performance testing like you would have unit or functional tests. Every day, we get information if something happens in our application that affects the performance in a negative way.

NeoLoad offers better reporting than most competing tools. It is effortless to analyze and measure the reported data. It's also simple to generate a report that most people can read and management can understand. NeoLoad helps you figure out the main issues inside the application. 

Some users may find NeoLoad too technical, while other users may prefer a scripting language instead of a UI with figures and forms they have to fill in.

I began using NeoLoad when Neotys still owned the product. In total, I have about 13 years of experience working with the solution. 

Setting up NeoLoad is straightforward.

We deployed NeoLoad in-house. I already had experience with the solution from my previous job, so we didn't need Tricentis to send a consultant to help us. However, it's helpful to take advantage of their consultants if you need them. Tricentis has a network of freelancers, so it's easy to find a consultant near you, and you can usually find somebody who speaks your mother tongue.

We were customers of NeoLoad and I'm an automation test engineer and team lead.

I do like this tool, it's very easy to use the front end and the UI is very good. It's also simple for anyone who doesn't have a technical or coding background. I liked that we could record the script and use it multiple times. 

Our issues with the solution were related to the license and the support. We had a technical issue related to our software and they weren't able to solve the problem. 

We used this solution for 18 months. 

I don't find this to be such a stable product because our requirements mean we need to be able to change the script on a monthly and sometimes weekly basis.

The support is not great - they don't respond in a timely way. 

We purchased a two-year license but broke the contract after 18 months. 

We're currently looking for a NeoLoad alternative. I prefer dynamic tools because we should be able to change the script and NeoLoad didn't allow us to do that. I'm looking for a tool that will allow for a weekly or monthly script change and provide us with the ability to update whatever has been recorded. 

I would rate this solution a seven out of 10. 

We primarily use the solution for load testing. Our focus is not so much performance testing. We focus more on load testing, which does inadvertently include performance testing, however. 

The test cases are quite easy to build and to maintain. This is the most valuable aspect of the solution for us. It's the reason why they changed from JMeter to NeoLoad.

Overall, we're quite satisfied with the product.

Sometimes it's complicated to maintain the test cases. It's much easier than in JMeter, however. I'm not sure if this depends so much on NeoLoad, or is more based on the environment that we are testing.

I've been using the solution for about a year now.

The stability of the solution has been good, or at least good enough for our purposes. We haven't experienced any bugs or glitches so far. We also haven't had any crashes that would lead us to believe the solution isn't sound.

The scalability has so far fit our needs. We haven't had any issues expanding as required.

We currently have three people actively working on the solution. They are all testers.

The technical support is very good. Whenever we have needed something, they've provided support without us having to worry or wonder about if we'd get a response. Either they would send someone or help us remotely or the partner that they recommended to us (during the implementation process) helped us very quickly. The support has met our expectations so far and we're satisfied with their level of support.

We previously used Apache JMeter. We switched because test cases were easier to build on this solution.

The initial setup was straightforward for us. However, we did have assistance with the process, and that made it easier.

We got someone from Neotys to help us find someone to help assist us. They recommended a partner to help us to set it up right very quickly. We ordered the assistance suggested and we signed the contract on a Friday evening. We got the first report from NeoLoad the following Tuesday evening. We were quite satisfied with the assistance we received. It made the setup process quite easy.

We have pretty close to the latest version of the solution but are currently trying to make an upgrade.

I can recommend that product. I'd also recommend that new or potential users do some training. It's a good idea to use experienced partners or consultants to assist with the initial setup.

I'd rate the solution nine out of ten.

We use NetLoad for two different types of testing. We use it for load testing and automation testing. We use it test out the user experience. 

NeoLoad can be integrated with Selenium for testing the user interface and user experience.

The scripting is really user-friendly and the reporting is very good. It supports regular expressions that help us to correlate things.

NeoLoad integrates well with other solutions.

I would like to see support for auto-correlations.

I have been using Neotys NeoLoad for three years.

This is a stable solution from what I know. The frequency in which it is used depends on the project and the client.

We have 50 people who are licensed and using this solution.

The technical support is good.

I also have experience with Apache JMeter.

The implementation is easy. It is just about downloading the application and there are three modules to install and configure, including the monitoring, the agents, and the controller.

This is definitely a solution that I recommend. 

I would rate this solution a nine out of ten.

We use this solution because we want to know the difference between two different tools to suggest for our clients.

As we are a services company, we have used NeoLoad also as part of our exercise.

I like the scripting and parameterization features.

While importing the scripts from backup it should not create the new variables because it has created some issues for us.

Used for performance testing of applications on QA environments as well as production environments. NeoLoad is best tool for testing in production without making many changes to the script or solution.

It helped in achieving the testing of on-premise applications, as well as cloud-based applications, without much difficulty.

• Integration of all components in one place.
• GUI-based requests
• Ease of use compared with other performance tools.

NeoLoad does not support Citrix-based applications. Neotys should take a look into this protocol.

No issues.

No issues. As far as Neotys NeoLoad, it is excellent in scalability.

The support is good. 

We started with NeoLoad.

The initial setup is easy.

The implementation was done in-house.

Our ROI is 100%.

The licensing cost is less compared to other licensing performance testing tools.

We tried JMeter, but due to its support (which we found subpar), we had to switch to NeoLoad.

You will love NeoLoad moving from open source and code-based performance tools.

It is primarily used for load testing, stress testing and performance testing. It is a very good product.

It is a bit easier compared to our LoadRunner, and it is cheaper. It can select to upload and it is based on cloud services. It is really easy to learn and to use. 

It needs improvement with post-production. 

It has good support. 

It is cheaper than other solutions.

There are several key features, including Jenkins integration, infrastructure monitoring, and results analysis.

Implementing this product has allowed us to increase the number of projects that get load testing, and the frequency by which we re-test our performance.

It needs improvements in the UI. It's currently not as friendly as it should be.

We've used it for seven years.

We haven't had any issues with deployment.

We have never experienced any isuses with stability.

The product has scaled very well up until this point.

The support from Neotys is very good. Responses are timely and come from experienced, knowledgeable load testing professionals.

We previously, and still use JMeter for some projects, in addition to Neoload.

The initial setup is straightforward for basic usage. The setup for higher volume load testing is more involved, but I wouldn't say complex, as should be expected for an enterprise class load testing tool.

We implemented it with our in-house team.

It's priced based on the numbers of VUs, virtual users, that your needs require. The free edition gives you 50 VUs. The pricing is fair for high-volume licensing. Cloud VUs can be rented on-demand for bursts of higher capacity testing needs without permanent purchase.

We looked at JMeter and Webload.

I highly recommend understanding load testing concepts before using any automation tool.