Apache JMeter vs. Tricentis NeoLoad

JMeter is well suited for Java applications where the user can script the scenario once and make changes to accommodate for as many numbers of users for load test execution. The image and selection of any files or exporting files scenario is handled well.

It is less appropriate to test Ajax applications where it is required to script click per use.

Incentivized

Our testing environment has found NeoLoad to be an invaluable tool. It was mostly utilized for web load testing. Its upkeep and the way various features were implemented were excellent. Because of the test results and actions in various items, the majority of institutions use this program. Additionally, by investigating various load types, it enables developers to test heavy load applications and assist in analyzing the strength and performance of such apps.

Incentivized

• Easy of use - in generate load like HTTP requests, and processing/analyzing the responses. No coding is necessary at the basic level, just need to understand load testing and the infrastructure being tested.
• Automatic management of things like cookies to help with session state support - so you don't specifically have to worry about it or handle it
• Lots of testing/configuration options to suit your needs in making the right load generation (sampling requests), and analyzing the results, including any pre and post processing of the results first. Things like the Beanshell/BSF pre/post processors, response assertion, regular expression extractor, XPath extractor, CSV data set config
• There is a JMeter cloud service called BlazeMeter that I think would be useful for those that need to scale up high load without provisioning their own systems. I've not personally tried it though, but I recently attended a meetup presentation that highlighted nice useful features that BlazeMeter provides. One should evaluate the service if they are considering JMeter and need to expand beyond existing hardware resources.

• 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.

Incentivized

• Jmeter requires many tweaks with respect to its configuration file and thread properties. users need to edit theses files themselves. There could be some interface where we can edit this fields.
• Jmeter cannot handle more threads and hangs up when we increase the number of threads. This causes lot of inconvenience. In these situations, user can be notified that such change would be lead to slow performance so that user can do as required. The same appears when we try to view huge files on graph listener.
• Jmeter should optimize the read and write access to output csv since it acts as overhead to the I/O performance. This affects our test results for the application which we are testing.

• 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

Incentivized

Price, Wiki and user sharing. Having access to the information provided by the developers and other open source providers is key for me. The ability to share information and get answers directly is very important to success in software testing. And the price of this product currently is amazing. Too many companies charge way too much money for products that are far behind in their value and pertinence

We find NeoLoad easy to use compared to their competitors. It requires minimal coding knowledge, also it is easy to train newcomers with NeoLoad. It also offers good integration and automation capability where with less code you can automate your testing process

Incentivized

I can jump right into a new test plan and start building from scratch. The natural progression from test plan to thread group and then designing the basic format of the process is very streamlined and smooth. With only slight modifications I can build out a very complex model from a very basic beginning.

In being flexible to meet all needs, it is very bare bones by design, but this could be a considered a feature and not a bug.

I have been using JMeter for the last year. By using this tool, you can make sure the system will work under varied loads. It helps us to simulate real time scenarios by creating required virtual users and make sure the application will work under load. Perform load, stress, and stability testing using JMeter.

Incentivized

This is the only area where we strongly feel Tricentis needs to improve. Their support process is inadequate, representatives are not so capable of providing solutions at one shot without consulting their internal engineering teams. Most importantly, the time they take to resolve simple issues is huge and at many times hampered our work.

Incentivized

1. Their documentation is scattered over many places like GitHub read me files, their internal website etc;
2. Support team takes huge time just to acknowledge our ticket
3. No support to automatically migrate scripts from competetor tool into

Incentivized

I have used LoadRunner and Silkperformer, and so far Jmeter turns out be the easiest to use of all these. While each of them have their own ROI, Jmeter can be picked by anyone in hours and start testing within a day. While with other tools, we need to get license, install them (takes a while) and setup tests and firewalls, etc.

There is a learning curve for those who are new to cross-browser testing or the Lambda Test platform to comprehend the features, capabilities, and how to put up tests successfully. There can be resource restrictions, such how many parallel tests you can perform at once, depending on your subscription plan. This may reduce the effectiveness of testing for complicated projects. Neoload on the other side is easy to use and restriction free tool.

Incentivized

• Good ROI on improving the performance of the application.
• Finding issues in the performance.
• Benchmark the performance results.
• CON: Need skillset to create and maintain the scripts in Java.
• Scripts are reusable and it is executed by any user.
• Need Client and Server setup to execute the scripts.

Incentivized

• Performance testing is like an insurance. An online store which is not available causes a loss of sales. Without a performance test you do not know if it might happen. The invest into performance tests reduces the risk of loosing sales. The flexible license model of NeoLoad allows or customers to choose reasonable and suiteable rate.

Incentivized