ReadyAPI Reviews

We use the solution for performance testing tools.

I am satisfied with the product. Importing documentation is easy. It is also easy to import Postman collections and create an environment in the API. It is easy to work with the tool and get started with testing. The performance testing capabilities are very good. We can catch potential problems with the APIs. The tool has scaled up its performance testing and reporting. It provides comprehensive and detailed reports. We can see at which point the system starts to deteriorate under the load.

The vendor conducts webinars. They must do it more, though. The solution must update SmartBear Academy. The content on ReadyAPI in SmartBear Academy is outdated.

I have been using the solution for around eight months.

The product is stable.

The product is scalable.

The support team provides comprehensive support. The support persons are always willing to jump on a call to assist us.

Positive

We used Postman before. We switched to ReadyAPI because of its loop-testing features.

The initial setup is straightforward.

The pricing is very competitive. It has a good impact on our time-to-market metrics. We have the complete SmartBear environment. The single cost for all the services makes it easier.

ReadyAPI enables users to import Postman collections easily. The load testing capabilities, ability to integrate with Azure DevOps quicker, and ability to predefine SLA to test the suite based on the predefined SLAs are valuable. The tool enables us to find bugs and defects faster.

We have mostly tested REST APIs. We haven't tested SOAP-based APIs. I have more than 100 Microservices automated with ReadyAPI. They are integrated into CI/CD and are running on Azure DevOps on a daily basis. We get a comprehensive report on it. It is also faster to integrate and create a pipeline for ReadyAPI. We just have to point Azure DevOps to the XML file we generate when the project runs locally. It's quite fast. I will recommend the tool to others. Overall, I rate the product a ten 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 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.

We mainly use this solution for testing APIs, and we also use it for load testing. SmartBear has a free version as well, which is called SoapAPI, but it does not include all of the features we wanted, so we got the paid version. The pro version has many benefits, including the load testing and more features for the API testing as well. Since we are mainly focused on backend testing, we thought it would be useful for us to have this license.

We had been using Postman, but Postman only has a couple of solutions to automate the API tests, and with ReadyAPI we can do both the API testing and the load testing. I haven't seen any other tool that offers both types of tests in a single tool. This is very helpful for us, and it's one of the main reasons why we chose this service.

We have an older version of ReadyAPI and it's not supporting our whole tests, so we have had to migrate some or we've had difficulties running them because they're very old script. Better compatibility or more support for the older versions would be helpful. 

Also, I've been seeing the same UI for many years, since I was using the free version, and the paid version looks the same. I think the UI could be a little bit better.

I have had experience with this solution for about five years.

The solution is stable almost all of the time. I'm not exactly sure if any other users are getting hang or not, but I have never faced an issue with hanging.

The scalability of the solution is good. I think about 150 testers in our organization use ReadyAPI. About 250 to 300 of our developers use the free version, SoapUI, to do basic API testing.

I think the support is good, but it's not immediate because we have many layers. If I have a question, I take it to a person in my organization, and then they contact tech support. It doesn't take too long, maybe one or two days, but I usually go to the SmartBear community online and look for an answer there. 

I used Postman to test the APIs, but with Postman it's just the basic testing, like unit testing. To do an intensive level of regression testing or load testing, Postman doesn't help much. It is still good to use for the manual part, but for automation, I feel like ReadyAPI is better.

This tool is very easy to set up and install because you can download ReadyAPI and you just need the product key. It was done in a matter of minutes.

We have an employee who deals directly with the access keys and maintenance. I think I have been on this specific project for about a year and a half, and I have only seen a maintenance window two times, and they typically don't last long or they do it in the off-times so they don't really affect my work.

I would say they should know exactly what they're looking for because if they're looking for API testing, this is a perfect tool. If they want to automate the process, then go ahead and use ReadyAPI. It is the best tool that I have ever seen for API testing. However, if you're just using it for manual API testing, I would say get the trial version or use Postman. We also use JMeter for performance or load testing, but ReadyAPI gives both API and load testing. If you want to do both, this is a good tool.

I would rate this solution as a seven out of ten because we haven't integrated it yet with any deployment tools, so I don't know how difficult that process will be. 

We are service providers, so a customer will come to us and ask us to build a service. We'll build it, and then we'll use ReadyAPI to test the services before we publish it.

The solution got us more into automated testing, as far as web services go, so now we're able to mass-test.

The two most valuable features we use are the functional test and the security test.

I would say if anything needs to be improved, maybe it's some aspects of the user interface.

The solution is made up of multiple tools, and the one additional feature we'd like to have is load testing.

I've been using this solution for about six years now. 

I think the solution is pretty stable. I haven't had any crashing issues. It's actually been pretty solid lately. When we started using it, it wasn't very solid at all, but that was many years ago.

It is a scalable solution. There are currently about six users in our organization. 

I would rate the technical support as a five out of five. They're phenomenal. 

Positive

The complexity depends on your skill level. For somebody who doesn't know a whole lot about web services and how they're structured, it's kind of complex to set up.

The deployment was done in-house. I manage updates when the solution pushes them out; other than that, it's pretty easy. 

We definitely see an ROI with this solution. 

We use fixed licenses, and the last time I checked, I want to say it's around $680 per seat per year.

My advice is that based on the flexibility of the application, the ease of use, and the price, it's definitely worth it. There's no other product out there comparable to the price we found.

I would rate this solution as a ten out of ten. 

We were using ReadyAPI for performance testing and creating mocks but there were some issues in terms of scaling, so we are no longer using this solution.

The most valuable feature of ReadyAPI is that it is user-friendly.

We stopped using this solution because of issues with scalability. Performance and memory management both need to be improved because other solutions use less memory for the same amount of data.

I think that there was an open-source version, with a lower cost, then this would be a recipe to get into bigger markets.

I used ReadyAPI for about one year.

I think that this is a stable product.

ReadyAPI is not as scalable as other solutions, such as Karate. More resources, especially in terms of memory, are required for the same amount of data.

The scale does not only refer to the number of users. It concerns the applications and how often they make calls to different servers or mocks. 

The initial setup was pretty straightforward.

The implementation was done by my team.

It took about a week to deploy because it involved more than just an installation. There was connectivity to configure and it had to be integrated with existing testing frameworks.

We migrated back to Karate about six months ago. It is more scalable and has more plugin features. There is also the point of cost because ReadyAPI requires licensing and Karate is open-source.

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.

I'm using the solution for API testing. My developer developed their APIs in Postman, so ReadyAPI has this integration factor, and from there, I exported my APIs and imported them into ReadyAPI. Every API I convert into a functional test. 

The conversion of the testing and the conversion of those APIs into a functional test is a great aspect of the solution. 

It's priced well. When I compared it with the Tosca, Eggplant, or other tools that offer API testing open source, this came out on top. 

This is a scriptless, codeless tool. 

It's easy to implement.

This is a stable product.

In general, they just need to be better. They have performance testing also. However, it's not that great. It's costly when it comes to a small company, and the features are not that smooth. While the application testing is fine, the API performance testing needs work.

Maintaining your scripts does take work. 

I've been using the solution for one year.

It's stable and reliable. We haven't had issues with bugs or glitches. It doesn't crash or freeze. The performance is pretty good. 

Right now, I'm the only person using the solution. I'm not sure how scalable it is.

I purchased the license from a vendor based in India, and when I have any issues, I reach out to them directly. I create an incident ticket, and they help resolve the issue. Usually, it takes two or three working days to sort a problem out. It's a bit delayed. However, it's not bad.

Neutral

The solution is simple to implement and very straightforward. 

You have a license manager that you have to install in your license server or machine, and then you just have to install the instance of ReadyAPI.

The pricing was well within our budget. It's reasonable and not too expensive. 

We pay $3,000 annually for a floating license. actually. That allows another person from my company to use it as well. It's a cloud-based license. 

I'm an end-user.

I'd advise new users that this is not a free tool. If you don't have a budget, you can go try Postman. However, if you have $4,000 or $5,000 a year, ReadyAPI is one of the best tools to use. It is easy to learn, and it is easy to work with. The features are very good.

In general, I would recommend this tool to others. 

I'd rate the solution 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.