There aren't any plugins for UI automation. You need to make a custom code and download a job to put into the libraries. If it were panelized, then it would be straightforward. It should be in a panel of the tools, so you can add those tools as your test step in your test cases.

For example, it would be nice to have a Selenium plugin available from the menu, where I can select "open browser" and provide the URL.  That URL would be immediately open in the browser. This is like a keyword, and then the Selenium plugin should be there.

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.

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. 

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. 

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.

Grouping of the cases is not possible in SoapUI, to my knowledge. When working with critical cases or the, we were not able to group them properly. We can definitely create a suite and add them there, but within a whole suite, we have to identify them, which was not easy.

When we ran a batch of test cases, we were not able to initiate the next batch automatically. When one suite was completed, we had to trigger another the next test suite manually. That means something from one test suite to another. Suppose, there are 10 test cases in the first suite and another 10 in the second. We have to initiate the first 10 cases and then the second. When we were triggering from the project level, it failed to move from the first suite to the second, and I'm not sure why. But that was something maybe related to the code, not the tool.

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.

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. 

Automation features are not user-friendly.

The UI could be a bit more flexible. 

There are no bugs or glitches, but a few features available only in the Pro version could be made available in the open-source version. Some of the features do not necessarily need to be only available to Pro users. The data generator would be really useful for the open-source version users.

The Pro version can be expensive for some companies.

For automation commands, it should be able to do what SmartBear is doing with ReadyAPI. They could filter on few things and pass on few things to SoapUI. The user database of SoapUI is bigger than ReadyAPI software.

As far as scripting is concerned, there should be consistency. For example, to declare a namespace, different syntaxes are used. Such things should be made consistent across SoapUI.

I would like more documentation, training, tutorials, etc. Also, I don't particularly appreciate that I have to save everything. It takes up a lot of space on my laptop, but I have to install the WSDL again If I don't save it. 

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.

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.

Better integration capabiliites with a range of Test Management Systems (not that it is not possible using the API) where a range of aspects are considered such as housing of the project, sharing (some capabilities here), versioning of projects, automatic saving of run information  and results (again this can be done in test suite setup but would be great to view in a test management system). There are some tools out there that do provide this but it would be ideal if this came as part of SoapUI NG Pro 

Working with Git needs to be improved. SoapUI 1.8.0 has this annoying habit of touching/changing many files that are unrelated to a test developer's actual change. This habit complicates working with Git, since Git thinks that the user has made hundreds of changes.

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.

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.

I cannot attest to the Ready Pro version, as I'm not really a fan of that version even though I am sure it offers a lot. I downgraded from that version after I installed it. I liked the earlier versions for what I do in the tool.

It would be nice to have an easier way to determine operation in the test case itself.

SoapUI Pro could improve by having dashboards.

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.

I have not been able to use this tool a lot of time, so I don't consider myself in a position to say what can really be improved. However, I would like to see some IDE plugins for Soap UI NG Pro. I don't know if you have it already implemented but, for example, an Eclipse Plugin would be great.

The licenses could be more flexible with regards to floating licenses.

In the case that a user changes a workstation, then the license locked to a certain workstation cannot be easily changed to another workstation. It would be more flexible if a license could be linked with the user personally.

Compared to i.e., Telerik Test Studio, you have a license that is connected with your email and password. So if a user changes machine he can release the license on the old machine, go to the new machine, and hook in the license there with his email and password, and he is up and running again.

With SmartBear, you have to contact the company to tell them that you have changed machine, etc.

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.

There are a lot of bugs and it can sometimes be 'quirky.'

• Improve bug fixing
• Stability
• Memory consumption
• Exclude test results out of projects (xml file)
• Improve composite project mode (tried version 1.2,1.3 but after short time refused)

It would be nice if you could organize the tests in more levels. Would like to add my own error message when using the Message Content Assertion (this is for the PRO version). This could be useful when running the tests from Jenkins.

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.

The application has to be restarted after being used for an hour or so as it stops working after that.

In the LoadUI companion the scripts are not user friendly, and it also has a slow startup time.

A better integration with IDE would be nice, but the main issue here is do not break what works well, as so many others have done.