ReadyAPI Test vs k6 Open Source comparison

"The standout feature of k6 is its strong focus on API performance testing."

"The tool's big advantage is that it is more performance-test oriented for experienced testers who know what they are doing. In a normal working setup, performance engineers frequently work with DevOps and development teams. For these teams, k6 Open Source's syntax is much simpler and easier to understand and apply in the working process."

"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 out-of-the-box support for the database is a valuable feature."

"SoapUI is uncomplicated and user-friendly."

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

"The interface is user-friendly."

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

"The solution has some good scanning features."

"One good feature is SoapUI's URL check, which allows you to check among the applications. I'm not just talking about the ones for Android. It has all kinds of multi-world tests that are really helpful."

"One area where k6 could improve is by introducing a GUI similar to JMeter."

"The documentation needs to be improved because the interface is not easy for a first-time user."

"The UI could be a bit more flexible."

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

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

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

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

"Grouping of the cases is not possible in SoapUI, to my knowledge. When working with critical cases or the, we were not able to group them properly. We can definitely create a suite and add them there, but within a whole suite, we have to identify them, which was not easy."

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

"It is free of charge."

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

"The cost is not that bad."

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

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

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

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