IBM DevOps Test Performance helps software testing teams test earlier and more frequently by shifting testing left. IBM DevOps Test Performance validates the scalability of web and server applications, identifies the presence and cause of system performance bottlenecks and reduces load testing. Software testing teams can execute performance tests that analyze the impact of load on applications.
N/A
Tricentis NeoLoad
Score 9.3 out of 10
N/A
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.
Go for IBM RPT if: 1. You're testing a Java-based Web application with HTTP protocol 2. You wanted to distribute the load across machines easily 3. Your team is in learning phase/not really introduced to a wide range of performance testing tools Do not go for IBM RPT if: 1. You wanted to test REST or any other advanced protocols 2. Your system under test demands a very high user load 3. Your application is written in .NET or any other platform except Java.
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.
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.
Memory utilization could have been improved.(Eats up system's RAM)! It may crash if a test is conducted with the heavy load if adequate RAM is not available in the VM/host machine.
Licensing could have been made simpler. IBM's licensing method is difficult to follow.
Support for protocols other than HTTP. Not really up to the current trend.
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.
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
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.
Cost/Licensing: While JMeter is an opensource testing tool from Apache, compared to IBM RPT and HP LoadRunner, RPT is much cheaper than Loadrunner. Functionality:JMeter provides basic functionalities which are adequate for performance testing, however advanced features are not available (such as load testing with GUI, reporting is very basic etc.). But when it comes to Loadrunner, it offers very broad features and supports a variety of protocols. So in this category, Loadrunner is a winner, but RPT is better than JMeter. Ease of operating:JMeter is easy compared to LoadRunner, but it has old GUI and look and feel is not that great to understand. Also, most of the things are to be done in a command line, non-GUI mode. While LoadRunner is very advanced with many options, which also confusing sometimes. But RPT, on the other hand, maintains a balance between simplicity and offering of different features. So winner: RPT.
Tricentis NeoLoad is easier to use, with simpler steps to follow to record/write test scripts and to design scenarios. It is scalable and comparatively provides overall benefits in a fair cost. Neoload also provides APIs for anyone to leverage and build on top of the existing features. This adds up as an advantage.
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.
