Tricentis NeoLoad

Formerly Neotys NeoLoad

Shared features

Integration with Qtest

Test case recording

presenting the results

Strong code-free design

virtual environment

Rich Test Scenarios.

Comprehensive Performance Testing.

Detailed Reporting.

Easy to Integrate.

Cost is little high.

It is resource intensive tool.

There are Licensing restrictions.

User friendly interface.

Good HTML reporting presentation.

Integration is easy.

Cost is a little high.

Reporting needs improvement.

Application takes a lot of space.

Very simple user interface.

Very reliable open source system for testing applications.

It doesn’t provide detailed documentations.

The price is a little steep.

Application is bit too heavy.

Easy to maintenance.

Excellent HTML reporting presentation.

It is very intuitive interface

It is not a open source tool

Cost is little bit high

Lots of click

Real time tracking

Browser-based testing

Nothing else that I could identify problems with.

Report

Real-time load monitoring

Dashboards

User interface

Version control

Repository

Real time test analysis

Workspaces are useful

Performance test automation is handy

It has integration challanges

Data privacy and security during testing can be challenging

Neolaod is relatively expensive

User friendly GUI

Strong support for correlations

Minimal coding requirements

Stable, does not crash even under heavy load

Integration with third-party tools. I cannot stream NL test data to a third-party DB and then plot graphs out of it.

Keyboard shortcuts. It is tedious to use the mouse to click everywhere. I'd love to have some keyboard shortcuts

Reports and Analytics. Lacks intelligence in identifying patterns of problems

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.

Website testing

API testing

Testing automation

Problem patterns are not identified using Tricentis NeoLoad

Reporting dashboard functionalities are limited. Analyzing test results can be difficult.

Premium Free version is not available.

Recording of test cases

Reporting the results

Maintaining the scripts

Usability of the GUI

Licence polica

Neoload's tool provide an interface to reuse the existing recording which is such a big relief to users.

It is also the ability to automate technologies such as SAP, Cicatrix & web sockets.

Apart from the update of recorded response after replay; log is one of the greatest feature. It helps in partial script creation & modification.

It takes longer than expect to connect with Load Generator machine, caused in failure of test launch.

It should support others languages apart from java-script.

Code based automation is missing, which leads little frustration.

Niche experts on performance testing

Works across a wide range of technologies, including mobile

Easy script manipulation through xpath and JS

Limited capabilities on virtual environments

No autosave feature

Weak code editor for scripting

You can build automated testing flows

You can hit apis with specific data requests

You can manage variables and data sets for your tests

NeoLoad is highly customizable. If anything having a faster way to load general testing templates or choose them from pre-made libraries might be helpful.

Ability to segment a 'Type' of users in a mix of users.

Ability to throttle transaction volume at increasing rates while identifying crucial throughput/failure points.

Ability to test changes like switching to a different Database with precise throughput transaction metrics.

Building Test Plans takes time. When the input fields of page changes it breaks the previous plan. The tool would be better if it had a way to migrate an existing plan and adapt to small changes.

Documentation is fair, but would be improved with more detailed screenshot by screenshot configuration changes rather than summation using words.

NeoLoad supports performance test engineers with a strong feature set to analyse the results. The first metric you have in mind is response time of the application. The metric satisfies the stakeholder if it meets the requirements. Otherwise, the stakeholder wants to know some comments and suggestions for improvement. I rely on the data gathered by monitoring agents when I analyse test results. The monitoring agent is a service which collects different counters from an operating system, databases, web server, etc. The results can be analysed in individual composed graphs. This is a powerful feature to deliver conclusive reports to stakeholders. Even the export of reports in various formats is helpful for communication with different stakeholders.

Our customers like the flexible license model of NeoLoad. A usual performance test project starts with the development of tests and configuration of the test environment. Finally, there is a first test execution followed by a couple of additional test executions. Usually, it is hard to say how long it takes to implement the issues based on the test results. So we usually do not know how long is the period between first and last test execution. It does not matter how long the period might be. In most of our projects we prefer daily licenses of NeoLoad. If you buy e.g. a four-day license you can use NeoLoad at four different days.

As a performance test engineer, I like the impressive APIs of NeoLoad. NeoLoad is just a performance test tool and the vendor Neotys is focused on this job. Whenever you would like to add something into a test scenario which is not mainly a performance issue you can integrate these parts by APIs which are easy to handle and very powerful. They also support you in case technologies which are not supported yet by NeoLoad. Maybe there is a new device which you want to monitor. Therefore you can report the measurements of the specific counters by the data exchange API during test execution. So you can analyse the data in the usual way. In our company we developed already a couple of features based on the APIs of NeoLoad and we are very happy with this flexibility.

NeoLoad allows the user many switches and options. Sometimes it is hard to understand dependencies. But the documentation and the support helps you.

In most projects it is necessary to develop small scripts. NeoLoad only supports JavaScript and the editor is weak. There is syntax highlighting but sometimes you can not see where the cursor is located exactly. NeoLoad supports a workaround if you register .js-files in Windows to a different editor.

Neoload is good for performance measurement of memory, CPU, and network usage.

Neoload cannot be for running performance testing on Citrix applications.

NeoLoad does not require much of scripting efforts, and correlation and parameterization are quite easy.

It has some actions which are very useful like variable modifier and java scripts.

The data collection for monitors is easy and less time consuming.

The memory consumption is higher which slows down the system.

The concept of team server can be improved in such a way that every time we design a project, it doesn't need to be shared as it takes longer.

Results need to be published every time. It needs to be auto saved.

Sometimes the monitors become invisible after we check out the project in local.

Building performance testing scripts is easy. NeoLoad builds the scripts for you by recording your session as you navigate through the application under test.

NeoLoad works with mobile applications using the same recording technique.

NeoLoad has modules that permit gathering OS metrics from the target host and correlating the data with the load testing results. The modules are agentless, meaning that there no need to deploy NeoLoad code modules on the host to gather these metrics.

There is no support for VT3270 terminal emulation to support mainframe-hosted applications.

The ramp-up and ramp-down time data are not automatically excluded from the average response time calculations. Instead, you must exclude these times manually each time you run a test.

There is not a summary graphic that shows the distribution of all of the response times on a single graph. We currently export the data as a coma separated variable (CSV) file and import into Excel to generate this summary graph.

Very user friendly and easy to use.

Correlation cannot be simpler than the way NeoLoad does. You can even use XPATH.

Handling virual user in runtime such as kick out some and add them back in runtime or simply keep adding them to test the stress level of server is awesome.

The ability to manipulate the script by inserting JavaScript is also tremendous. It's one of the features few other tools have.

I am very much satisfied with this tool.