Inflectra Rapise vs ReadyAPI Test comparison

"The most valuable feature of the solution is its versatility."

"We always use the product for end-to-end automation test cases."

"It's pretty straightforward to set up."

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

"The solution offers excellent integration capabilities."

"The solution has some good scanning features."

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

"The tool’s scalability is very good."

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

"The product allows us to uncover any potential issues early on."

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

"The maintenance is very difficult. We've only been using the platform for three months, so I'm not sure if that will continue, but right now it's an observation I've had."

"It would be good if there could be more integration of Inflectra Rapise, since not all customers use the same tool for test management and automation integration."

"Inflectra Rapise needs to expand its ability."

"Automation features are not user-friendly."

"The current interface is unsatisfactory."

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

"I find that I'm fighting with the opportunities to order requests."

"Stability has been an issue for us. It needs to be looked at and made a bit better."

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

"SoapUI Pro could improve by having dashboards."

"The UI could be a bit more flexible."

"I rate the product's price an eight on a scale of one to ten, where ten means very good pricing."

"We pay no more than $50 annually for support of each one of the licenses."

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

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

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

"It is free of charge."

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

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