What advice do you have for others considering ReadyAPI?

It's not stable. The Git API within ReadyAPI is a a GUI front end to make it easier to do version control but it doesn't work well as mentioned. It's not reliable. I would not recommend this product, as there are better products out there. I would rate this solution a six out of ten.

I would say go for it. It is a really great tool. It is a game-changer because you can automate faster and quicker. It also doesn't take much time for any person to pick up the tool. It is pretty lightweight. Any person who has a little bit of technical background or 1% JavaScript knowledge can quickly use it and write code in Groovy. I would rate ReadyAPI an eight out of ten.

Our plan includes a need to filter out all the API, middle-tier bugs. This is the initial phase of development. We don't want to find any bugs in either UAT or UAP. That's an objective for us, but right now, we are setting up the team and people are working on it. My advice for anybody who is implementing ReadyAPI is, to begin with establishing a framework of what they want to achieve. Comfort with the framework is more important, before acquiring the license. I would rate this solution an eight out of ten.

If you're testing mainly on API and then you want to have a full-fledged API testing on load performance, function, security, etc., this product will actually be a one-stop platform for that. I would rate this solution an eight out of 10.

The main advantage is that it could be integrated into different CI/CD tools. That is something that is really valuable and helpful. I would rate it an eight out of ten. In the next release, they should make the ability to extend different functions a bit easier. We extend some functionalities and it's possible to extend the functionalities because you have the ability to add many interesting pieces by yourself to that API but it's not so easy. It would really help if they improved that.

I would recommend this solution to people who need official support. For companies who have experts in open-source technology, they can avoid using ReadyAPI. I think that it would come down to the specific client, or project. I would rate this solution an eight out of ten.

Third-parties have been developing integration with this solution. For example, JIRA has been integrated. My advice for anybody who is considering this solution is to consider that they will save a lot of money, and there will be a reduction in errors from the use of external data or wrong parameters. The quality of their code will be better, so do not hesitate to buy this kind of solution. I would rate this solution an eight out of ten.

I would rate this solution a nine out of ten.