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.

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.

I'm using ReadyAPI for services, automation, security testing, and manual updates.

The most valuable features of ReadyAPI are the scripting tools and the connectivity to external data sources, such as Excel and PDF files. There are plenty of useful features that are useful, such as automating flexibility and usability. Overall, the solution is easy to use.

The reporting in ReadyAPI could be better. It can become sloppy, sometimes it works and other times it does not.

I have been using ReadyAPI for approximately seven years.

ReadyAPI is a stable solution.

When I was using an older version of the solution I had to use community support online. I have not contacted support from ReadyAPI directly.

The initial setup of ReadyAPI is easy. You only need to install it.

ReadyAPI is one of the best tools which is available in the market to automate and test manually.

Most of our employees know how to use the solution well and value it.

Utilizing ReadyAPI is highly recommended. It's a user-friendly and efficient tool that can meet your fundamental requirements, both in manual and automated methods. It's a reliable tool that's easy to use and there aren't many better alternatives available.

I rate ReadyAPI a seven out of ten.

We mainly used the different applications of API. It's data-driven, so I had to create the Excel sheet and then loop it through the test suites. We were running each version, which was helpful.

Our organization doesn't have many servers due to security compliance.

The most valuable feature is being able to run each version for test suites.

To generate a test suite in API, I had to create a separate one each time because otherwise it would just override the test. Each API had to be added separately. I thought I could just have one and then create different methods, but I had to add each API separately to create the test for that. That is an area that could be improved.

It would be nice to have some kind of automation or organization.

I used the latest version of this solution for about six months.

It was okay. There were one or two times the solution closed on me but otherwise it was fine.

The scalability is okay.

Support was good.

Setup was fine, but I needed to have some meetings with support to complete the integration with Azure DevOps.

The price was around $6,000 for one license, but I don't remember exactly. It is definitely expensive. Our organization was planning on having multiple licenses for this year.

I would rate this solution 8 out of 10. I definitely like ReadyAPI. It is a good tool and it's easy to use.

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.

We are it using it with the license on individual machines.

We have a bulk of APIs for our different products. Previously, we used to do  Postman, and for automation, we used to do C-Sharp code. However, we came to ReadyAPI as it is a tool that can give some exposure to the person who does not have much core coding or programming knowledge. 

We like the basic features. We can add additional features. It is a hybrid kind of tool. Over here, can add our own code, and we can write the assertion with the script. As a programmer, it is a good tool. We can utilize it dynamically if you have programming skills.

It's great for those that don't have as much exposure to programming. 

Currently, we are hosting. We have repositories under the Git site, and we are checking our code there. We are executing it with the AWS cloud. The integration with GitHub is not there. They have given us some options. However, it is not workable. We have to check in or pull our code with Visual Studio right now. We have to use Visual Studio to manage that integration, actually.

The UI should be flexible. Currently, the UI isn't. If you want to minimize/maximize it and if you want to use it on a hub screen, you can't use it. It is not that user-friendly. 

Cloud integration should be there as modern work is in the cloud.

We've been using the solution for the last two years. 

It is a great tool and has great exposure for future API automation. The only thing that is missing is the integration with the different cloud services so that we can manage that project in the cloud and check in and check out the code. Currently, that core functionality is missing. 

It is a scalable solution. However, it is not so flexible. If multiple team members are working together, they have to frequently pull and push the code to sync with the single team and take the latest code, which other team members develop. For better functionality, we have to go every time to Visual Studio.

Multiple teams are using the solution right now. On my team, we have seven to eight people using it. I'm unaware of how many people are using it from the client side. Users are a mix of automation testers and manual functional testers. 

I do not personally contact technical support. Another team member handled that aspect. We used to communicate with SmartBear, and if there were any critical issues, we would reach out. However, I don't handle that aspect. From what I understand, support is helpful. 

Previously, we used to code the API automation in C-Sharp. That could be handled by the core programming person. I'm a core programming guy, so I can manage that code and write the new scripts for the automation. However, we found that we could utilize this tool so that a person with basic knowledge and not core programming knowledge could also contribute to this tool with the API automation. That is the basic module.

This tool is giving exposure to resources with little programming knowledge. They can also start contributing to this, and certainly, they can learn the programming part of that tool as well. However, in terms of the UI part, through the UI, we can automate the API. It depends on our logic, and how we want to utilize the different assertions and different checks. If you have programming knowledge, you can also use that tool with the programming part. The idea, however, was to make it more useable for everybody.

The initial setup of ReadyAPI was considered to be easy. It's quite straightforward. We have to download the .EXE and install it and register with the license. That's it. 

It will take not more than five minutes if you follow the instructions.

I'm not sure of the exact cost. 

We are a customer and end-user. 

If you are going to use this product, you should have a basic knowledge of APIs and how APIs work. This is an API automation tool specific to automating the APIs. If you have previous exposure to an open-source tool, like Postman, then you can easily get started with this tool. However, you must go through basic training if you don't know APIs and never work on APIs.

I'd rate it six out of ten. It gives us core value, however, the UI isn't great.

The primary use of this solution is to perform code testing. We can set up the environment, the representations, and the code coverage.

We have this solution deployed on a Windows station, on-premises.

With this solution, we have achieved a fifty-percent gain when it comes to writing test cases.

The most valuable feature of this solution is SoapUI Pro. It is very friendly to use with the API.

ReadyAPI is not just a web service launcher, but a tool that can analyze results, for example from a dashboard, for tests that take a long time. You can see if there is a degradation in the service of the management system.

You will not find the coverage provided by ReadyAPI in other tools.

The dashboards are very good and consolidate all of the tests that you are performing with the client.

This solution is focused on web services, but it should be expanded to a complete test manager. For example, in the test suite, you can include a UI test, but this is with another tool. It is not fully integrated.

ReadyAPI is not fully integrated with all system ecosystem tests. If ReadyAPI had more integration with all of the big tools on the market then this would be very useful.

For what we have been doing, this solution has been ninety percent stable.

We are deploying it on a heavy client, and it depends on the infrastructure of our users. We did not deploy it on a virtual desktop. While it is very stable, it is not one hundred percent in our configuration.

We have between twenty-five and thirty people who use this solution.

Technical support for this solution is very good.

The only problem is that we are in France, and the support is in the US, so there is a difference in time that we have to accommodate for. That said, while they are on-site, they are very reactive.

Most of the time, we have to wait one day for support.

The deployment of this solution was very quick and simple.

This is a cheap solution when you consider the money that will be saved in testing.

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.

My use cases are mainly for the functional tests of APIs. I have the desktop installation, and I'm using the latest version.

Testing API with this tool is very effective. Testers can very quickly get productive with ReadyAPI.

The great thing about ReadyAPI is that it has a wide variety of functions. You can test any API that you come across. You are not limited to one type of API. It supports many API types.

It is very straightforward and easy to design the tests. Also, when we need it, we can extend it with scripting. So, it is easy to use for simple testing, and it is also capable enough for complex testing on large projects.

The licensing is sometimes a barrier for our customers. You need to have separate licenses for functional tests, load testing and virtual (mock) services.

The support could also be improved to handle requests more quickly.

I've been using SoapUI, a free version of this product, for 10 years. For one year, I have been using ReadyAPI as I have switched to the paid version.

It is very good. I can't remember any instability issues. It is usually very stable.

It is a desktop application, so technical scalability is not applicable. 

The product is very good, but the support could work more smoothly. Sometimes, the response time and the type of response are different from what I would expect.

Their knowledge base and documentation are very good and of high level.

Positive

I also work with other solutions, such as Postman. Postman's functionality for API testing isn't that comprehensive as in ReadyAPI. On the other hand, Postman is pretty strong in API design and API sharing (publishing).

For a company that uses REST APIs only, Postman could be a good option. Postman's focus is a bit different than ReadyAPI's. ReadyAPI is a testing and API virtualization tool, whereas Postman is also suitable for API design and marketing because you can easily share your API with others. However, it can be used for testing as well. So, there is a testing overlap with ReadyAPI, but in that area, ReadyAPI is much stronger. 

On the other hand, Postman has very friendly and affordable licensing.

It is straightforward. We can set up the application and start testing straight away. It takes about 15 minutes to deploy the desktop application.

It does not need any other maintenance. It just needs upgrades, and the upgrades are automatic.

Each user needs to be licensed, and the product has different licenses. It starts at 750 euros for a single user per year. 

This basic cost is for functional testing only, and then there are additional licenses for load testing and virtual services. You are limited if you want to use these areas with the functional test license. If you have all three licenses, then you have complete functionality of ReadyAPI.

Insomnia, Postman.

It is good to explore the ReadyAPI functionality first and compare the benefits with its price. 

ReadyAPI can become a great tool for your organization for the long run and different types of APIs. 

You should consider the API styles you have, such as SOAP, REST, or GraphQL, and check out how it is supported in ReadyAPI and how much benefit ReadyAPI will bring to you.