ReadyAPI Test vs TestingWhiz comparison

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

"I primarily use Soap UI to test XML/JSON requests and responses for APIs hosted by us and our vendors."

"SoapUI is very useful; before we started using SoapUI, we had to do everything manually, which is very time-consuming, and there were a few things we couldn't validate, but using SoapUI made everything easier, you can do six to seven hours of work efficiently, and it's more flexible to use."

"The interface is user-friendly."

"Using this solution, we developed tests about three times faster than we did with Java and by doing manual REST reverse engineering from product code (Java)."

"We can test as many APIs as we like, it's very reliable and very easy to understand, anyone can learn it very quickly."

"SoapUI is uncomplicated and user-friendly."

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

"TestingWhiz is a low code, no code tool with integration facilities, such as with Jira, and can be used over the cloud."

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

"Stability has been an issue for us."

"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 UI should be improved."

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

"Sometimes it would get stuck, so we had to close ReadyAPI and then start it again."

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

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

"Some features need to be implemented based on customer customization requests, which are currently not available."

"The cost is not that bad."

"My understanding is that the pricing is okay, however, that's taken care of by our procurement team. It's around $5,000 for three years."

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

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

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

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

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