SoapUI despite the name is not a slipery tool that one always has problems grasping. In fact, it's the opposite!!
Updated October 16, 2015
SoapUI despite the name is not a slipery tool that one always has problems grasping. In fact, it's the opposite!!
Score 9 out of 10
Vetted Review
Verified User
Software Version
SoapUI Pro New license
Modules Used
- We began utilizing just about every module in SoapUI and, and even created database that exported the test reports for archiving and searching. The only thing we used in a limited basis was the LoadUI which technicaly is a seperate tool anyway, but it is well integrated with SopaUI
- SoapUI continually has been improved with each release since SmartBear. SoapUI was already a versatile, user friendly UI testing tool and very accurate results and consistently effective.
- We managed to be able to work with the SoapUI support team to resolve some memory issues that were really linked more to the SQL database than SoapUI, but a lot of improvements was made in that aspect as well.
- In my opinion, SoapUI is and will remain the first option and tool of choice for API and back end testing, and currently nothing comes close to match all the features and modules that SoapUI has. The other part of it is the maturity of this tool. It has been around for a while, so it sits on a very stable foundation, and yet more and more updates and upgrades are provided to meet the changing demand of software testing.
Overall Satisfaction with SoapUI Pro
As a major hosting and Cloud company, we have thousands upon thousand of API that make calls across several programs, usually in very complex variations that involves coordinating not only testing back end of applications and API calls, but how they work and integrate with one another as we simulate a live production environment
So, SoapUI, after examining several different tools was the best candidate with all the modules and feature we needed to complete our testing. We did take a few steps further, due to the amount of tests that needed to run concurrently most of the time. But at the end, we managed to get maximum coverage of testing with a high degree of accuracy as we put in place redundant validation points.
So, SoapUI, after examining several different tools was the best candidate with all the modules and feature we needed to complete our testing. We did take a few steps further, due to the amount of tests that needed to run concurrently most of the time. But at the end, we managed to get maximum coverage of testing with a high degree of accuracy as we put in place redundant validation points.
- Ability to combine multiple test and adhere to the sequence that they need to run in order to complete successfully, regardless of pass or fail, the result is accurate.
- Excellent GUI design to make it as organic for the tester as they are revising or updating their tests. Once you get comfortable with the core functionality of SoapUI, you can explore the many added capabilities it has, like utilizing groovy or JavaScript. You can provide input and output files for the tests to use in sequence or randomly.
- Excellent reporting mechanism and options to print or to save to file. Also you can include verbose debugging content or create a shorter executive summary version. We even went as far as importing it to SQL database for cataloging and archiving for the sake of better tractability.
- Memory consumption, in large concurrent testing has been a challenge for SoapUI, mostly due to the amount of information that is getting written to the database, but there are workarounds to custom install SoapUI which for example runs on a Cloud server, where it can provide SoapUI the elasticity that it may need with large concurrent tests that run for while before completing.
- compatibility with all other databases and Open Cloud environment such as OpenStack out there in Open source, which I think is already in works.
- Integration of LoadUI is good, but to take serious step to compete with other performance and load testing tools
- On time completion of testing always translates and effects the ROI
- Accuracy and ability to meet the test coverage % that was planned also effect the confidence of the stakeholders
- Testers ramp up using SoapUI, therefore continue to become more and more efficient.
HP Products, Silk, IBM Rational suite of testing tools.
They just seemed to be overkill or mostly under the needed features. Some have made way to complex, where SoapUI manage to continue to improve the tool, but maintain the ease of use.
They just seemed to be overkill or mostly under the needed features. Some have made way to complex, where SoapUI manage to continue to improve the tool, but maintain the ease of use.
Using SoapUI Pro
75 - Various business functions related to internal and external critical applications and their accurate testing results. It's usage grew consistently over the life of the projects life cycle, which is my assumption, as I did not survey everyone in the group, that it indicates achieving desired results and upheld expectations from the tool used.
75 - I would imagine this number would remain the the same or grow gradually, as to date, it had been the most effective testing tool considering the special needs of the project, and the application.
- API Calls clustered to test each one, as well as put a strain on the application and database to find the thresholds of it's load capabilities.
- Creating a nightly regression testing routine that would take several hours to complete.
- Tap into the raw data SoapUI generated, aside from standard reporting to find weaknesses, and potential risk areas.
- Using the data via linking it to an external database for a deeper look, and establishing better tractability.
Evaluating SoapUI Pro and Competitors
Yes - In the past HP Service Test, JMeter and other similar tools were tried, however to get the complete capabilities needed, the decision was simple. We had to choose the tool that worked with multiple platforms, various languages and databases. It is true that the best testing tool for any system depends on the make up of the system, but SoapUI covered a wider range, and our intention was always to minimize the number different tools that was being used for testing.
- Product Features
- Product Usability
- Product Reputation
- Prior Experience with the Product
If you have been in the field of testing for 10+ years, and work with test automation, you may be familiar with evolution of the testing tools out there. SoapUI for example due to having a Open source version rapidly evolved in features and improvements in usability, and establish a reputation among those who has used it before.
I think a very thorough evaluation of the development, build and deployment, and testing tool is just good practice. Specially if it is a brand new product you have started to build. It eliminates the possibility of having to go back and revise your plan, if you have done the due diligent properly.
SoapUI Pro Support
| Pros | Cons |
|---|---|
Quick Resolution Good followup Knowledgeable team Problems get solved Kept well informed No escalation required Support understands my problem Quick Initial Response | None |
Yes - Some clues and indicators of why the high memory usage climbing. Yes, it was addressed and eventually improved.
long conference calls with support engineer to resolve the memory issue bogging down the test machines, and kept at it until a workaround was in place and a hot-fix patch was applied.
Using SoapUI Pro
| Pros | Cons |
|---|---|
Like to use Relatively simple Easy to use Well integrated Consistent Convenient Feel confident using | None |
- REST Calls, API calls
- Simulating live use by combining various calls that were dependent on one another, or another external return response to the call.
Yes, but I don't use it