ReadyAPI (formerly SoapUI Pro, LoadUI Pro, and ServiceV Pro) is a REST and SOAP API functional testing tool that enables software developers, QA engineers, and manual testers to work together to create, maintain, and execute complex end-to-end API tests in their CI/CD pipelines without needing to code.
N/A
Tricentis NeoLoad
Score 8.1 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.
NeoLoad is more SAP-centric and offers use cases a lot closer to what we experiment on a daily basis. The main competition in the space would be loadrunner but it lacks the flexibility of NeoLoad, and also comes at a much higher price in a way that would have hurt our …
As stated, we do a LOT of API testing, the swaggerhub import makes it easy to add APIs. This is very well-suited, as well as easy management of the steps/cases/suites inside of ReadyAPI. The one thing I do wish ReadyAPI was better suited for is changes to data, we have a lot of test cases in ReadyAPI and if we make a change to how the backend data is structured, one-by-one adjustments need to be made to the steps. Less appropriate, UI testing.
Here are some specific scenarios where Tricentis NeoLoad might be well-suited:
Performance testing of web applications: Tricentis NeoLoad is well-suited for testing the performance of web applications under heavy loads. It can simulate multiple users accessing the application simultaneously and measure response times, throughput, and error rates to identify bottlenecks and potential failure points.
Testing the scalability of APIs: Tricentis NeoLoad is well-suited for testing the scalability of APIs. It can simulate increasing loads on an API and measure the response times and error rates to identify the point at which performance starts to degrade.
Identifying performance bottlenecks: Tricentis NeoLoad can be used to identify performance bottlenecks in web applications and APIs 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.
Here are some scenarios where Tricentis NeoLoad might be less appropriate:
Testing the performance of native mobile applications: Tricentis NeoLoad is primarily focused on testing the performance of web applications and APIs. It does not have as much support for testing the performance of native mobile applications.
Testing the performance of applications hosted in the cloud: Tricentis NeoLoad does not have as much support for testing the performance of applications hosted in the cloud. It may be less well-suited for testing the performance of cloud-based applications and infrastructure.
Advanced scripting and customization: While Tricentis NeoLoad does offer some scripting and customization capabilities, it is not as well-suited for users who need more advanced options for customizing and automating load testing scenarios.
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.
The only reason this isn't a '10' is because of the cost. This product is definitely meant for organizations who are serious about making sure they invest in the full ecosystem of API design, development, maintenance. But there is a significant cost associated with this investment. and because of this cost (and the non-tangible output for executives), it is a difficult line-item to justify in this post-pandemic environment.
SoapUI allows us to combine multiple tests and adhere to the sequence that they need to run in order to complete successfully. It has an excellent GUI design and the reporting mechanism is also very good. It does consume a lot of memory though during concurrent testing
Soap UI has managed to continuously build on it's solid foundation and keep improving by each release. It is by far the most dependable and accurate testing tool out there of its kind. Available via connecting to VM's created as SoapUI test machines give access to it anytime, anywhere practically.
To be honest, we didnt had much issues with the support, as there is already plenty of online communities available for help. But if ever there were some minor issues with the membership or the certificates, the tech support was always quick and efficient enough to resolve the issue ASAP
ReadyAPI provides intuitive GUI capabilities compared to their own open source product. When compared to Postman, ReadyAPI also supports SOAP based services, which is a saver especially when integrating with legacy or other third party systems.
We used Jenkins for manual performance testing and had big efforts to script and evaluate the test results. Furthermore, the effort of maintaining and editing the scripts was very high. To generate a report, many tables must be analyzed. The efforts of these tasks are minimized since we used the great tool NeoLoad.
It has an excellent GUI design and the reporting mechanism is also very good. It does consume a lot of memory though during concurrent testing. However, I have read that added monitoring tools have been added, which if so the 7 could possibly go to a 8 or 9.
