ReadyAPI Reviews

We are using this solution for API testing on HL7 messages for healthcare.

It's easy to learn how to use it.

Version control does not work well. It's has a git API which is defective and doesn't work well with our version repository, Bitbucket. We do all version control using git bash (command line driven), and sometimes we have to try several times to as there still hooks into the ReadyAPI git API which cause issues.

I have been using ReadyAPI since April 2020.

I don't find it to be that stable. Sometimes it stalls, shuts down or you have to shut it down and restart it.

We haven't scaled it. We have approximately nine people using this solution in our organization.

SmartBear does not take phone calls. You have to email them if you want something resolved. It's a lot of back and forth through email, which takes a long time.

I am not impressed at all with SmartBear. We don't want to purchase any of their products going forward.

HP ALM - support is not good and the yearly license was very expensive - also not an easy tool to build API tests as we were using Service Test.

Licensing costs are yearly.

There are costs in addition to the licensing fee. For example, if you want to add the load testing you would pay more.

Not for API testing as we already had ReadyAPI - another team was using it for adhoc testing

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.

ReadyAPI is predominantly used for functional testing of the APIs. Our company has a lot of micro strategy concepts, and we are building a lot of APIs. The focus is on more validations around the APIs for faster or quicker testing rather than the frontend. 

When you are working in sprints, you need to have continuous feedback. ReadyAPI definitely helps in automating very fast and rapidly. We have less coding, and we can more easily define our assertions. 

We don't use it for full-blown performance testing, but normally if you are doing your functional testing, it gives you the request and response time. Anybody who is doing functional testing can see what the request and response times are and raise a flag based upon their business affiliates, that is, whether it is meeting their affiliates. You can identify this during functional testing.

It doesn't have connectors to the NoSQL database. This is one of the things where they do not have a very solid strategy today. Other solutions have an in-built mechanism where I can directly and easily connect. An API is more around a user submitting a request on the frontend. It then hits the backend, puts the data, and responds back. If I am hitting MongoDB or NoSQL databases, I do not have ready-made inbuilt solutions in ReadyAPI that can easily help me in automating it faster. In our organization, we deal with NoSQL databases, and therefore, we need Groovy. We just cannot have a connector from ReadyAPI to do that. I have to write Groovy scripts. If you have themes that are predominantly using MongoDB, it leads to more maintenance and support activity because we are introducing more code into our commission.

In terms of additional features, it can have cloud support. This is one of the things where we are getting into cloud support. We'll see how it works, but it is one of the doubts that we still have.

I have been using this solution for almost four years now.

It's pretty good. I haven't seen any issue or ReadyAPI crash in the last four years.

It is scalable. For example, if I'm running a UI test case, it can take me a minimum of 1 or 2 minutes or 45 seconds to 2 to 3 hours, depending upon the complexity of the workflow. If I want to test the same in API and I have defined my framework and everything, I could do it in 30 seconds or 40 seconds.

Technical support is pretty helpful. They are pretty responsive. They come back to you to find out if you want some training on ReadyAPI. If you want to schedule, they will schedule one. They will also help your team to grow or scale up.

When I came in, we were only using SmartBear. Before that, maybe there were normal functional automation testing tools, where you can define your API frameworks and do API testing. With such tools, you write more code for defining the API framework, which already comes inbuilt with ReadyAPI.

The initial setup is pretty straightforward. Its deployment is pretty simple as well. It doesn't take too long to deploy it.

The cost of a license is probably around $1,000 to $2,000. Accounting is done by my leadership. I am more into implementations and making sure all things and processes are taken care of and the frameworks are maintained and managed. 

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 primary use case of ReadyAPI is as a testing tool for mock data testing. I'm a technical consultant and we are customers of this solution. 

I like that it's easy to automate within our deployment and to have the ability for more data-driven testing. ReadyAPI is also easy to integrate. 

I would ideally like to see a more user-friendly UI to replace what is currently there. Secondly, we never know when there's going to be a license upgrade and it would be helpful to receive an automated email prior to license expiry or some kind of auto-enabled system for license upgrades to give us an alert or some kind of notification before the license expires.

I've been using this solution for one year. 

The solution is stable and reliable. 

I think scaling up and down is possible. There are 10 users of this solution in my team but there would be many others throughout the company. We only use the solution for certain projects so it's not used on a daily basis. 

The customer support is good; they are very knowledgeable and they respond quickly. I was quite impressed.

Positive

I would advise anyone considering implementing this solution to look at the Smartbear documentation on ReadyAPI in order to explore new ways to implement it according to customer requirements and to understand how the product operates.

I rate this solution eight out of 10. 

We use ReadyAPI for API test automation. These APIs are developed by our development team and we need to validate the response. We use it for manual testing and then automation for those particular manual test cases. This has been my first experience completing API test automation or using tools for this purpose.

We get the data from an Excel sheet and then we input it into the API request to validate the response which we get. That is all done automatically using the automation suit I created on ReadyAPI. We save the data from the response into an Excel sheet. In my team, there are five people who are using it and we have five different licenses.

The most valuable feature has been the assertion as a test step as this has allowed us to increase the scope of testing and validation.

This solution is a pro version of SoapUI, which is a licensed version. There is a free version of SoapU but this requires coding and knowledge of groovy scripting. The overall scope of this solution is limited and could be improved. 

Stability of this solution could be improved. When we run test simultaneously, the systems gets stuck and we often need to restart it and try again. 

It is a scalable solution.

The initial setup is straightforward or works similarly to a Windows application. Once you open it up, you import the APIs which you want to automate or which you want to run. It is easier to setup compared to other API test automation tools. Deployment takes a few minutes. 

I would recommend this tool to others for basic test automation with good performance. A beginner level knowledge of groovy scripting will be sufficient to use this solution.

I would rate it a seven out of ten because I haven't used any other test automation tools so I don't have anything to compare it to.

I use ReadyAPI for API and data-driven testing. You can run your APIs through a loop.

ReadyAPI is a QA testing tool. We were able to catch many bugs because we could inject various scenarios running through our data-driven testing. This improves the quality of our products.

ReadyAPI could improve by having dynamic validation information.

I have been using ReadyAPI for approximately eight years.

ReadyAPI is stable.

The scalability of ReadyAPI is good. However, every one of the 20 QA team members uses it independently.

The support from ReadyAPI is very good.

I rate the support from ReadyAPI a four out of five.

Positive

The initial setup of ReadyAPI is straightforward.

The IT team members can install the solution themself.

We have received a return on investment using ReadyAPI.

Our IT team does the maintenance of the solution.

I would recommend others try out the solution to see if it fits their needs.

I rate ReadyAPI a nine out of ten.

ReadyAPI's best features are that it's user-friendly and its behavior-driven development is flexible.

Areas for improvement include the security files, endpoints, and process sessions. ReadyAPI should also include the ability to add and modify existing files.

I've been using ReadyAPI for almost fifteen years.

ReadyAPI is stable.

The initial setup is straightforward for anybody with experience.

ReadyAPI is moderately priced, with added costs for more plugins.

I would rate ReadyAPI eight out of ten.

I primarily use ReadyAPI to convert APIs into functional test cases and to manage customer information.

ReadyAPI's best features are user-friendliness, smooth integration with Postman, the speed of creating test cases, and integration with customer data.

An improvement for ReadyAPI would be automated import/export with third-party tools. It can also be hard for new testers to learn.

I've been using ReadyAPI for six months.

ReadyAPI is stable.

ReadyAPI's customer support isn't that great, particularly their response time.

The initial setup is very easy.

ReadyAPI requires a product license and a subscription, which is renewable every year or three years. Its pricing is very reasonable, unlike more expensive competitors like Tosca, XPlant, or Catalon.

I would advise anybody thinking of implementing ReadyAPI to install the trial version and go through the tutorial so that they can learn how the solution works. I would rate ReadyAPI as eight out of ten.

We have a lot of external vendors that we integrate with, so we need to validate all of the APIs. Also, we need to mark those services that don't need external vendor integration.

We are at the initial stage of using this product, and although we have a plan, it is too early to assess and recognize the benefits.

We like the user interface.

The most valuable features are the integration with Jira and the test management tools.

They have interfaces with our performance tools, so we were able to leverage all of these integrations and plugins. It is very good from an integrative solution standpoint.

The reporting is not very robust and needs to be improved. They give the pass or fail criteria, but we need to know the history and also why it has failed. Essentially, the details that we see in other tools are missing. This is a request that we have made and we hope that these are implemented in the next version.

They should include support for integrating with Xray, which is another test management tool. More generally, they should have a larger scope when it comes to integrating with test management tools.

We recently acquired the license for ReadyAPI and have been using it for the past three months.

We have not found any bugs or glitches so stability-wise, it is good enough for us to use.

The scalability is good. We have eight people in the IT department who use this product. There are four in development and another four in the QA team.

The interaction that we have had with Smartbear has been pretty good. They are responsive, and they can give an action item as well as a timeline for when it can be implemented.

I would rate the technical support an eight out of ten.

Prior to using Ready API, we were using Postman.

Postman is only for manual API testing, but when it comes to ReadyAPI, we can automate it using Groovy Scripts. We also have a plan to use Service Pro and LoadUI. These are the reasons that we selected ReadyAPI.

The initial setup was straightforward. All we had to do was configure the license server.

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.