OpenText Service Virtualization vs ReadyAPI Test comparison

"The feature which is most valuable in this solution is the ease of use. The product is very easy to use and very easy to implement."

"The support for integration patterns and the ease of use to wizard-based utility is what I would consider the most important features for service virtualization platforms."

"The most valuable feature is that it reduces the dependency so that the down time of the environment is not a major cost. That cost can be used for something else like the cloud."

"The most valuable feature is SAP virtualization."

"It is easy to use. This is what I tell my customers. The coding is easier to develop as well."

"The Pro and free version of SoapUI Pro has good technical support."

"ReadyAPI has the power to enrich all the technical work. You can achieve any complex task using ReadyAPI. I can also do UI automation with ReadyAPI. In a few test cases, we want to check the API and the equivalent UI. I download a job and write a piece of Groovy or Java code. It's almost the same in ReadyAPI. I can do that in a single test case. ReadyAPI is a powerful tool because you can do anything you want, but only you need to download the right set of jobs and produce the right set of code."

"It's a very simple solution to use."

"It clearly makes it easy to test APIs based on the SOAP protocol. We are a logistics company, and we have lots of tracking calls coming in. We provide APIs for tracking services, and it makes sense for us to use SoapUI to test them thoroughly."

"SoapUI Pro is a good tool when it comes to API design and orchestration. Additionally, it is beneficial for functional and for performance testing."

"Using SoapUI's automation suites to run all our test cases saved us a lot of time. Running 300 test cases takes about three to four days. When you automate all that, it takes only two to three hours."

"API mockups, functional testing, and load testing are valuable features."

"The most valuable features are that it is user-friendly, it's easy to use and easy to teach to others."

"More support for different protocols. I would love to see more wizards rather than relying on some custom coding, which you can use C# as well as Visual Basic scripting. In the service virtualization platform, I would love to see more wizard features as well as the ability to connect to an external database, which by the way, we have put an enhancement request in for. I'd love to see that in the service virtualization platform."

"HPE products are good, but they never make a product for a specific use. They make a product for the enterprise because that is their vision. They like multi-generational business plans. That means that they don't deliver small bits and pieces, but rather, they deliver to the enterprise."

"The current protocol needs to be updated to be much more flexible. The product needs more technical flexibility in implementation and customization."

"The integration with other solutions, such as ALM and Jira, should be improved."

"The monitoring feature is not impressive because they use Windows for so much monitoring. They set a lock on the window, and then we have to gather the information from the main monitoring feature in the Windows server. There is not enough capacity for problem solving performance issues."

"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."

"Occasionally, when you are saving, the solution can hang."

"Automation features are not user-friendly."

"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."

"The current interface is unsatisfactory."

"SoapUI would 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."

"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."

"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."

"Micro Service Virtualization is very expensive. The pricing of this product is in line with all of the other big name-brand products."

"It's an expensive solution, but you can get discounts. You have to buy one server and one designer together, for example, and it may cost 15 million Thai Baht."

"SoapUI Pro is open source but it has a subscription-based model which involves some more features. At the moment we are using the free version. The Pro version requires a license, and it is an annual license to use it."

"It is free of charge."

"The cost is not that bad."

"We have team members who are working in shifts, and it is not possible for us to utilize a single license on a single piece of hardware so that multiple team members can use it. We have to take out multiple licenses for each team member."

"The Pro version can be expensive for some companies. There are no costs in addition to the licensing fees."

"ReadyAPI Test is about $680 per user, per year."

"ReadyAPI Test is expensive, and I rate its pricing a four out of ten."

"I think the number of users is also limited, considering how much we pay."