Senior Quality Assurance Test Engineer at Dormakaba
Real User
Jan 12, 2024
ReadyAPI Test needs to improve its reporting. While reports provide essential information when issues arise, or tests fail, having more graphical representations directly within the reports would be beneficial. It needs to improve stability and scalability as well. The tool's support is slow, and takes months to reach a solution.
Digital Transformation Specialist at Jordan Kuwait Bank
Real User
Dec 22, 2023
The current interface is unsatisfactory. Imagine a scenario where, without an improved interface, testing the API becomes challenging. If I request a specific address through the API, it's difficult to ascertain whether it accurately retrieves the information I need. Without a clearer interface, I won't be able to confirm if the API meets my goal of retrieving the required information. Reading the API documentation alone may not provide sufficient insight. Therefore, having a more intuitive interface is crucial for effective testing and validation of the API's functionality. An additional feature that would be beneficial involves scheduling automated tests and defining scenarios based on the results of specific requests.
Software Test Engineer at Deutsche Rentenversicherung Bund
Real User
Jun 21, 2022
I find that I'm fighting with the opportunities to order requests. There's a view where you can add several requests to a URL and if I have a list of several requests I'm not able to sort those requests which is a problem. I'm still not sure whether there is some kind of a test runner for the API of the installed command.
Technical Product Manager at a tech vendor with 10,001+ employees
Real User
May 8, 2022
SoapUI Pro is a little heavy due to the number of features. Previously it was not that heavy. Now the tool is too heavy, they should work on fixing this issue because until your system has lots of resources, you won't be able to use it seamlessly. The performance of the application itself could improve.
In the beginning—I think it may have been the prior version—there was a lot of lag, but as the version updated, the lag decreased. SoapUI would also benefit from some more customization abilities. It's a good interface, but it would be nice if they added the ability to build custom dashboards where the user can do their own bar graphs and pie charts. It would be helpful from a management point of view. That way, the user can easily be able to know the status of the project.
It is limited to scope and risk services only. It does have some support for JMS, but it is not out-of-the-box; you have to do some tweaks here and there. They should improve the scope, and the message should not be limited to SOAP and REST services but also include other protocols and message formats so that people who have other requirements, other than SOAP and REST services, can also think of the solution. Otherwise, if you have 15 to 20% of automation other than SOAP and REST services, you would have to go to some other tools because it is not fully covered by SoapUI Pro. As for pain points, reporting is one. It's a bit difficult to filter out or to customize the report. It will be an either everything or nothing kind of report. Reporting also should have a flexible customization option. When I do a 10,000 testing execution, I don't have the option to filter out the report that is generated. This makes it even impossible on a Windows system to open that report because of the size of the file. It will capture each and every request and each and every SQL period, as a result of the SQL period. So, it is too heavy for Windows to handle it.
QA Team Lead at a tech services company with 1,001-5,000 employees
Real User
Top 10
Aug 24, 2021
It is helpful for individuals, however for a big team, for example, if I change any code in my project, for my colleague, it's difficult for them to use the same. This is the drawback. It's not ideal for teams and works best for individuals. If someone makes edits, it needs to be shared. We would like it to be possible to share code in order to effectively work together. Occasionally, when you are saving, the solution can hang. You might have to close it down and start again.
Middleware Technical Analyst at a comms service provider with 10,001+ employees
Real User
Nov 17, 2020
I think their user-information sites should be better defined by SoapUI. For example, if I want to hit that virtualize server, let's say, with a 100K load — what is the bare minimum requirement? That kind of definition is not available anywhere. If that level of measurement could be given, that would be really helpful. Tool-wise, I find no technical limitations as such. It's all as expected. It all depends on how much memory and how much you want to allocate. That's pretty typical for this type of solution. I suppose the GUI could be slightly improved. Right now, we don't have a way to capture the JVM stacks either for the virtualization or for the service when using SoapUI Pro for load testing.
Senior Test Manager at a logistics company with 5,001-10,000 employees
Real User
Jun 18, 2020
Stability has been an issue for us. It needs to be looked at and made a bit better. The load testing performance needs to be adjusted. It could work much more effectively, in my opinion. They should work on the pricing of the solution. Right now, we find it to be overly expensive.
The documentation needs to be improved because the interface is not easy for a first-time user. It would be better if the price of this solution was lowered.
Digital Bank-QA and DevOps Lead at a financial services firm with 1,001-5,000 employees
Real User
Dec 30, 2019
The automation needs improvement. We tried automation but it's not easy to integrate with the synching and some of the mission tools that we use for automated testing of APIs. That is the main section that we use and it needs to improve a lot. They could include extra trial sessions with the extended license for critical types because they have trial versions that are provided for one month. For corporate companies, it is not enough time to explore and access it and give feedback on whether they are proceeding with it or not. They should include a trial session for at least three months. That would be very good. In the next release, I would like integration with other tools to support software development, for example, Go! Zilla for defect management, so that I am able to test it, connect it, and trace it back to my requirement and log my defects seamlessly. I would like seamless connectivity with other software development tools.
Senior Software Consultant at a tech services company with 1,001-5,000 employees
Real User
Mar 6, 2019
The tools that are stated by SmartBear speaks for itself, but when it comes to improvements, there could be a release which only aims for the development of beginners in terms of understanding the tools that are laid by SmartBear.
The UI should be improved a little. It would be great to integrate the graphing module for load testing, so that we could analyze the timings of the responses and how that changes over time with changes in the API implementation logic.
ReadyAPI Test is a versatile solution for API testing, known for its flexibility, automation, and ease of setup. It efficiently handles SOAP, REST, and JDBC testing, with a user-friendly interface that supports both technical and non-technical teams.ReadyAPI Test offers robust capabilities in API testing, including functional, load, and security testing. Features such as Groovy scripting, mock services, and data-driven testing enhance workflow efficiency. It integrates well with project...
ReadyAPI Test needs to improve its reporting. While reports provide essential information when issues arise, or tests fail, having more graphical representations directly within the reports would be beneficial. It needs to improve stability and scalability as well. The tool's support is slow, and takes months to reach a solution.
The current interface is unsatisfactory. Imagine a scenario where, without an improved interface, testing the API becomes challenging. If I request a specific address through the API, it's difficult to ascertain whether it accurately retrieves the information I need. Without a clearer interface, I won't be able to confirm if the API meets my goal of retrieving the required information. Reading the API documentation alone may not provide sufficient insight. Therefore, having a more intuitive interface is crucial for effective testing and validation of the API's functionality. An additional feature that would be beneficial involves scheduling automated tests and defining scenarios based on the results of specific requests.
Automation features are not user-friendly.
The UI could be a bit more flexible.
I find that I'm fighting with the opportunities to order requests. There's a view where you can add several requests to a URL and if I have a list of several requests I'm not able to sort those requests which is a problem. I'm still not sure whether there is some kind of a test runner for the API of the installed command.
SoapUI Pro is a little heavy due to the number of features. Previously it was not that heavy. Now the tool is too heavy, they should work on fixing this issue because until your system has lots of resources, you won't be able to use it seamlessly. The performance of the application itself could improve.
SoapUI Pro could improve by having dashboards.
In the beginning—I think it may have been the prior version—there was a lot of lag, but as the version updated, the lag decreased. SoapUI would also benefit from some more customization abilities. It's a good interface, but it would be nice if they added the ability to build custom dashboards where the user can do their own bar graphs and pie charts. It would be helpful from a management point of view. That way, the user can easily be able to know the status of the project.
It is limited to scope and risk services only. It does have some support for JMS, but it is not out-of-the-box; you have to do some tweaks here and there. They should improve the scope, and the message should not be limited to SOAP and REST services but also include other protocols and message formats so that people who have other requirements, other than SOAP and REST services, can also think of the solution. Otherwise, if you have 15 to 20% of automation other than SOAP and REST services, you would have to go to some other tools because it is not fully covered by SoapUI Pro. As for pain points, reporting is one. It's a bit difficult to filter out or to customize the report. It will be an either everything or nothing kind of report. Reporting also should have a flexible customization option. When I do a 10,000 testing execution, I don't have the option to filter out the report that is generated. This makes it even impossible on a Windows system to open that report because of the size of the file. It will capture each and every request and each and every SQL period, as a result of the SQL period. So, it is too heavy for Windows to handle it.
It is helpful for individuals, however for a big team, for example, if I change any code in my project, for my colleague, it's difficult for them to use the same. This is the drawback. It's not ideal for teams and works best for individuals. If someone makes edits, it needs to be shared. We would like it to be possible to share code in order to effectively work together. Occasionally, when you are saving, the solution can hang. You might have to close it down and start again.
I think their user-information sites should be better defined by SoapUI. For example, if I want to hit that virtualize server, let's say, with a 100K load — what is the bare minimum requirement? That kind of definition is not available anywhere. If that level of measurement could be given, that would be really helpful. Tool-wise, I find no technical limitations as such. It's all as expected. It all depends on how much memory and how much you want to allocate. That's pretty typical for this type of solution. I suppose the GUI could be slightly improved. Right now, we don't have a way to capture the JVM stacks either for the virtualization or for the service when using SoapUI Pro for load testing.
Stability has been an issue for us. It needs to be looked at and made a bit better. The load testing performance needs to be adjusted. It could work much more effectively, in my opinion. They should work on the pricing of the solution. Right now, we find it to be overly expensive.
The documentation needs to be improved because the interface is not easy for a first-time user. It would be better if the price of this solution was lowered.
The automation needs improvement. We tried automation but it's not easy to integrate with the synching and some of the mission tools that we use for automated testing of APIs. That is the main section that we use and it needs to improve a lot. They could include extra trial sessions with the extended license for critical types because they have trial versions that are provided for one month. For corporate companies, it is not enough time to explore and access it and give feedback on whether they are proceeding with it or not. They should include a trial session for at least three months. That would be very good. In the next release, I would like integration with other tools to support software development, for example, Go! Zilla for defect management, so that I am able to test it, connect it, and trace it back to my requirement and log my defects seamlessly. I would like seamless connectivity with other software development tools.
The tools that are stated by SmartBear speaks for itself, but when it comes to improvements, there could be a release which only aims for the development of beginners in terms of understanding the tools that are laid by SmartBear.
The UI should be improved a little. It would be great to integrate the graphing module for load testing, so that we could analyze the timings of the responses and how that changes over time with changes in the API implementation logic.