SoapUI Reviews

The main use case of SoapUI is for API testing. We use SoapUI for API testing when we want to perform a performance test of our services that we have built. We use it when we have a lot of test cases to execute because SoapUI allows us to create many test cases. We can run them in parallel or in sequential order. We can design the regression test case suite in SoapUI.

SoapUI is really great for my team because when we are trying to create test cases and the requests that we are going to send to an API, we can create one SoapUI folder which will be XML and this XML is used by SoapUI itself. If we want to share whatever request we are running on my system with another person, we can export the test suite that we are working on and give it to another person. It is shareable through file upload and download. However, we cannot share it through a link or something implemented on the cloud.

The best feature of SoapUI is that we can build a suite in SoapUI. When we build a suite, it creates a kind of directory where we can organize our tests in one place, and then we can share it. Another best feature is that we can execute the tests that we want to do on API level in a sequential fashion or in parallel, through synchronous or asynchronous calls.

For the feature where we can organize and share test suites, because we have the test suite now, there are many things that we want to check manually. This suite can be shared with a team, and then the suite can be divided into parts or we can divide the work by sharing the suite. We can update the suite and then we can make a final suite that will be useful for next iterations. This has helped us in creating a very efficient test suite and a way to organize our test cases and regression suite.

SoapUI can be improved in the UI and the way it looks. It does the work, but there are sometimes many things that we do not understand. There should be documentation or docs where we can understand what all the features of SoapUI are. Sometimes it has many features and it feels really cluttered.

The UI feels a little outdated.

I have been using SoapUI for five years now.

SoapUI is stable.

SoapUI is not that scalable.

Customer support is good for SoapUI. In terms of scalability, it is good. We do not have any relationship with the customer.

There are no such impacts. SoapUI is a good tool. It has not improved any performance or anything, but it is a good tool to have.

SoapUI does not really handle a lot of data. It is something that we pass to it and then it interacts with another system and gives us back results. There is no AI involved, and there is no governance and security to be considered when using this product.

It is pretty accurate. It hits the endpoint correctly and gives the outputs in real time. SoapUI is really good at that.

If somebody is trying to use SoapUI, they can buy the free version. If they want to utilize the licensed version, they can. I would rate this product a 9 out of 10.

We use SoapUI for testing the API requests and the authentication rules of APIs, and we also check if we are getting the output of the API correctly and if it is not bypassing the test cases.

A scenario existed where we used SoapUI to test many things in REST APIs. In one scenario, we wanted to check if a certain user wanted to update some information while two people were trying to update the information of a certain person simultaneously. In the database, we were getting deadlock issues. We tried to check it via API testing tools, but we were not able to replicate it. However, with SoapUI's parallel testing capability, we were able to find the root cause. When we hit it from parallel requests at the same time, we were able to see the deadlock. This was replicated only in SoapUI; we could not replicate this elsewhere.

SoapUI helped us in this scenario because we found a way of testing this scenario other than actually pushing the changes into production. We found a way to test it and subsequently found a way to fix it. There are certain test cases that cannot be tested in real time, but this was an asynchronous test API hit that was made possible with SoapUI. This allowed us to fix that issue and test it thoroughly.

We can create a group of test APIs and REST API requests. Second, we can give a test suite a sequence to run, enabling us to create a regression suite. Third, we can extract the XML and give it to somebody else so they can also run it.

We mostly rely on the capability where we can extract the test cases that we have written and perform them. This is a better way to delegate things when you can create a replica of your work and give it to somebody else to just run it and then observe it, allowing you to do other work.

The collaboration effort has been really successful. Previously, we used to struggle in finding ways to test the API, and everybody was trying to find one single root issue. Now there is one solution to be found and one error to be found. As a tester, we want to find as many defects in the product so that we can fix it before it goes to production. SoapUI has really made that possible for us.

SoapUI is pretty good overall.

If we could have more sharing capability within teams or its own structure, that would help. A workspace where two or three people can join and contribute on a single thing, similar to Microsoft Excel, would be beneficial.

We do not have version control established within SoapUI.

I have been using SoapUI for about five or six years.

SoapUI is pretty good and trustworthy. It is accurate most of the time, and I do not have to rethink if the results are correct.

I would tell others to try to use SoapUI more often so that they will get more familiar with it, and they can surely purchase this product as it is a great tool. I would rate this product an 8 out of 10.

We use the solution mainly for API testing.

The solution's most valuable features are the designing of API, Property Transfer feature, and Groovy plugin.

The solution should include some plug-ins to share the generated reports over email. Sometimes, Groovy can be a tricky language, and we need to focus more on that.

I have been using SoapUI for four to five years.

There is an open community and a lot of forums available where you can easily get help with the solution. SoapUI has a community where all the questions are answered proactively. They also provide awards on their community site, which is really a motivating factor for answering the questions.

I also work with the Postman tool. With SoapUI, running the suites in one go is much easier, and the reports are sorted. You need not go to different reports for each test case.

The solution's initial setup is easy and can be done within a few minutes.

SoapUI helps save time, which in turn saves money. The solution's reports are pretty useful, and we were able to figure out the issues within the API design quickly. I also use SoapUI for automation purposes, which saves almost 30% to 40% of our manual efforts.

SoapUI is a cheap tool that does not have an expensive license. It has a lot of good features with the open source itself.

You can easily design your test case with the help of SoapUI, whether SOAP or REST. I would recommend the solution to other users.

Overall, I rate the solution an eight out of ten.

I use the product to access the browser whenever it is required. 

We need to test the APIs as we build them. I use the product for API testing. You can do AWS security in SoapUI. With SoapUI, we can even perform mutual SSL authentication by incorporating certificates into the SoapUI browser. This allows us to send transactions to the backend downstream.  

The product needs to be available as an extension for the Chrome browser. 

The product is a testing tool, and I haven't encountered any issues or bugs during the testing process. 

SoapUI can handle big loads of testing. Overall, I'm satisfied with its performance.

I haven't contacted the support since I haven't faced any issues. 

For testing purposes, we utilize both SoapUI and the Postman browser. SoapUI is particularly advantageous because it allows us to upload visual files, which is not supported in Postman.

Setting up the product was a straightforward process. Typically, the organization provides the software, so I had to install it on my machine and start using it. It's similar to downloading and installing a browser on your PC. It can be completed in a few minutes. 

I would recommend the product to others. I rate it a nine out of ten. 

I use the solution for API testing when some of our clients give us the API payload for SoapUI projects.

SoapUI is a pretty simple tool. You just open a project and hit the payload, and it shows you the result. It has a book view window that shows you the payload on the left side and the response on the right side. SoapUI is straightforward compared to the other API tools I have experience with.

There are more advanced API testing tools than SoapUI, and SoapUI could be made better.

I have been using SoapUI for more than two years.

I haven’t faced any issues with the solution’s stability.

Postman is more advanced than SoapUI.

The solution's initial setup is not that complicated. You can easily download the application from SoapUI's website.

SoapUI is an open-source solution.

You can integrate the solution with proxy numbers. For instance, with Apica, you start recording, and Apica will pick up whatever you do on the SoapUI application. You can find your script there. The solution's integration is good because you can integrate it with the proxy number of your recording platform, and it just picks up whatever action you do on SoapUI. I would recommend the solution to other users.

Overall, I rate SoapUI an eight out of ten.