ReadyAPI Reviews

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.

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.

Our primary use case for this solution is for testing APIs, which is very basic. Additionally, we use it for tier-driven automation. For example, if we want a file-based operation for test automation, we can use ReadyAPI as a Groovy scripting tool. So we have some external jars and use Groovy code to invoke mainframe environments, retrieve the data from the mainframe environments into our file, and read the file data. We deploy this solution on the customer's device.

We have found the flexibility of ReadyAPI very valuable. For example, messaging queue frameworks like JMS are required when playing with the APIs because we usually work on data migration projects. It gives us leverage to use utility and things we cannot do with other tools. Additionally, it provides DB connectivity and a good coding standard, but it's not a typical coding base. So understanding coding is necessary, and you must also know the tool's capabilities. Hence, it is a blend of both being a professional, tool-based, and language-driven person.

Additionally, no UI is involved when designing a solution for a customer. So we can do the automation using ReadyAPI, DV, file creation or file deletion. Every operation can be done because it provides Groovy's coding platform, which is nothing like Java. If you have a working Java code, remove the class and other steps, like the primary method, and you can easily create the Groovy code, which is the same code written in Java. Then, the pending status can be updated and available. This allows for easy integration with various databases, even MongoDB and code databases can easily be integrated. With the test management tools and JIRA, it is effortless to integrate. Additionally, it is open and easily configurable with the database tools. Hence, it's one of my first choices whenever we do API testing.

The product could be improved by including an inherent feature for UI automation. This will allow us to require mobile UI automation testing.

We have been using this solution for five years and are currently using version 3.40.

The solution is stable. Initially, there was a huge problem, but currently, we're only facing a challenge with integrating test cases with databases because it hangs for a minute.

The solution is scalable. Approximately 50 people use this solution in our company.

We have had a good experience with customer service and support. I rate them an eight out of ten.

The initial setup is straightforward. You only need a license file from the customer, then download EXE and install the ReadyAPI. If the software support center is not providing us with the EXE., we usually download it from the internet. The customers provide a paid license file, or a license variety, in the model they are configuring. The setup takes approximately five to ten minutes.

We have seen a return on investment because our organization is large and we can easily afford it.

The licensing fee is charged annually, and we currently charge 10,000 Swedish Krona per user.

We chose this solution because it is a good test case. In addition, it allows us to speed up manual processes through automation.

I rate this solution an eight out of ten. I recommend this solution to new users because it is the best solution you can get across the globe for API, test automation, and API penetration testing. My primary advice to new users will be to understand the risks and the fundamentals of API testing.

ReadyAPI was installed on my system as a client and I used it for microservice API testing. The solution was used for an amusement park.

The most valuable features of ReadyAPI are the drag-and-drop options and the integration with versioning tool solutions, such as Git.

ReadyAPI could improve by adding a conversion tool from one file type to another. Import support for multiple file types would be beneficial.

I have been using the solution for ReadyAPI for approximately one year.

The stability of ReadyAPI is good, but if we have to import large files there can be issues.

This solution is best suited for medium to large-sized companies. However, the use of the solution is not dependent on the company size, it's dependent on the volume of data or the APIs that are being used. A small company can work on a solution that involves a lot of APIs

I have not used the support from ReadyAPI.

I previously used SoapUI but it was decommissioned and was renamed ReadyAPI.

The initial setup of ReadyAPI was straightforward. The deployment took approximately 15 people.

We did the implementation of ReadyAPI in-house. We have approximately 10 to 12 people that are supporting the solution.

I compared ReadyAPI to Postman and ReadyAPI is an enterprise-friendly application. There is no other tool that matches the capabilities of ReadyAPI for enterprise-level companies.

I would recommend ReadyAPI to others because it's user-friendly and can handle enterprise-level API testing needs. You have all that you need in an API testing tool.

I rate ReadyAPI a nine 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 testing APIs.

When we are doing API testing we have found it to be very efficient to receive results. Additionally, you are able to do tests directly from the API.

I have used ReadyAPI within the past 12 months.

The solution is stable.

I have found ReadyAPI scalable.

I have used the support and they assisted us with a problem which they resolved. 

I have used TestComplete.

The initial setup could be less complex.

The price of the solution has been fine.

My advice to anyone who wants to do API testing, this solution is easy to use.

I rate ReadyAPI an eight out of ten.

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. 

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.