ReadyAPI OverviewUNIXBusinessApplication

ReadyAPI is the #5 ranked solution in top Performance Testing Tools and #9 ranked solution in top Functional Testing Tools. PeerSpot users give ReadyAPI an average rating of 7.8 out of 10. ReadyAPI is most commonly compared to ReadyAPI Test: ReadyAPI vs ReadyAPI Test. ReadyAPI is popular among the large enterprise segment, accounting for 71% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 21% of all views.
ReadyAPI Buyer's Guide

Download the ReadyAPI Buyer's Guide including reviews and more. Updated: November 2022

What is ReadyAPI?

ReadyAPI is an all-in-one automated testing platform that allows teams to create, manage, and execute automated functional, security, and performance tests in one centralized interface.

ReadyAPI Features

Some of ReadyAPI’s key features include:

  • Continuous integration
  • Comprehensive dashboard
  • API discovery
  • Central, standardized reporting function
  • Plugin architecture
  • ReadyAPI Projects
  • Multiple options for scripting to create functional, load, or security tests

ReadyAPI Benefits

Some of the benefits of using ReadyAPI include:

  • Easy and flexible test creation and execution: ReadyAPI has visual editors and wizards that make testing easy, saving time and simplifying onboarding.

  • Test APIs continuously: With ReadyAPI you can run consistent tests on local environments, Docker containers, or other distributed staging environments.

  • Team friendly: ReadyAPI enables software teams with the ability to easily share testing projects and artifacts, share licenses between team members, and report issues directly from the testing IDE.

  • Powerful, data-driven testing capabilities: With ReadyAPI, you can save time by checking for numerous real world conditions.

  • Supports multiple specifications, schemas, and protocols: ReadyAPI includes legacy SOAP services, microservices powered by Apache Kafka, and mainstream REST services, as well as IoT use cases leveraging MQTT. It allows you to test and virtualize the most popular API protocols and also to import APIs from specifications and schemas instantly.

Reviews from Real Users

Below are some reviews and helpful feedback written by Dell EMC Unity users.

PeerSpot user Vallalarasu P., Test Architect at a tech services company, states, “ReadyAPI is one of the best tools for API testing because they have made a single platform for functional testing, load testing security, and also service actualization. We also have virtual work that can be an add-in within ReadyAPI. For integration for CACD, they have something called TestEngine, which can also be an add-on for ReadyAPI. We use Python request library and things like that but if you're a bigger organization with hundreds of APIs, then ReadyAPI is a one-stop solution for complete API testing. If you consider TestComplete and other products for an equivalent outcome, you might get something nearly comparable, butReadyAPI is the outstanding product.”

An IT Manager at an insurance company says the solution has “Fast automation, less coding, and is pretty lightweight. 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."

Balamurugan A., Manager at a financial services firm, comments, “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.”

ReadyAPI was previously known as Ready API.

ReadyAPI Customers

Healthcare Data Solutions (HDS)

ReadyAPI Video

Archived ReadyAPI Reviews (more than two years old)

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Manager, Clinical Applications QA Testing at a healthcare company with 1,001-5,000 employees
Real User
Easy to learn how to use it but the version control doesn't work well, it's not stable, and the support needs improvement
Pros and Cons
  • "It's easy to learn how to use it."
  • "Version control does not work well."

What is our primary use case?

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

What is most valuable?

It's easy to learn how to use it.

What needs improvement?

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.

For how long have I used the solution?

I have been using ReadyAPI since April 2020.

Buyer's Guide
ReadyAPI
November 2022
Learn what your peers think about ReadyAPI. Get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
656,862 professionals have used our research since 2012.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

How are customer service and support?

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.

Which solution did I use previously and why did I switch?

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.

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
IT Manager at a insurance company with 10,001+ employees
Real User
Top 5Leaderboard
Fast automation, less coding, and pretty lightweight
Pros and Cons
  • "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."

What is our primary use case?

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. 

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

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.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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

What's my experience with pricing, setup cost, and licensing?

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. 

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
ReadyAPI
November 2022
Learn what your peers think about ReadyAPI. Get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
656,862 professionals have used our research since 2012.
Balamurugan Arjunan - PeerSpot reviewer
Manager at a financial services firm with 1,001-5,000 employees
Real User
Good support, we like the user interface, and it integrates with several test management tools
Pros and Cons
  • "The most valuable features are the integration with Jira and the test management tools."
  • "The reporting is not very robust and needs to be improved."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

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.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Vallalarasu  Pandiyan - PeerSpot reviewer
Test Architect at a tech services company with 1,001-5,000 employees
Real User
Top 10
A great single platform for functional testing, load testing security, and service actualization
Pros and Cons
  • "A single platform for functional testing, load testing security, and service actualization."
  • "Lacking flexibility of adding more custom verification for security testing."

What is our primary use case?

We are partners with SmartBear and I'm a test architect.

What is most valuable?

ReadyAPI is one of the best tools for API testing because they have made a single platform for functional testing, load testing security, and also service actualization. We also have virtual work that can be an add-in within ReadyAPI. For integration for CACD, they have something called TestEngine, which can also be an add-on for ReadyAPI. We use Python request library and things like that but if you're a bigger organization with hundreds of APIs, then ReadyAPI is a one-stop solution for complete API testing. If you consider TestComplete and other products for an equivalent outcome, you might get something nearly comparable, butReadyAPI is the outstanding product.

What needs improvement?

I think the security testing with API could be improved as they provide limited templates. It would be helpful if they provided us with more capabilities and the flexibility of adding more custom verification for the security testing part of ReadyAPI. Basically, some additional features would improve the product. 

For how long have I used the solution?

I've been using this solution for five years. 

What do I think about the scalability of the solution?

If you are thinking about huge numbers of APIs that need to be maintained and executed, this product can be scalable to large amounts. We can create multiple projects, maintain them and group them according to what suits our test skills. All this comes with a beautified structure from whatever SoapUI open source we have. They carry all the advantages of open source and additionally they are non-scripting and generate reports after test events. All these things as well as custom reporting if you need that, so it's very comfortable for scaling.

We need to use ReadyAPI for scalability, because if you go to RestAssured and are writing a framework there, it is good for a hundred APIs. But if you go for a thousand APIs you'll need to have someone to maintain the code completely and to fix it whenever it's failing. You need to rewrite the frameworks and then if your API is getting updated you need to modify all this stuff, but here the API is so good.

How are customer service and technical support?

Technical support is very good. If you have a customer ID and you purchase the license, I think you will get a response from SmartBear within 24 hours. They also give a platform for requesting new features. They have a large technical team who analyze and try to implement, and they give you the status of your suggestions, so they will tell you that they're still in the process of analyzing whether they will accept them or not. Their community, the SmartBear community, is huge and very well organized actually. If you have any technical questions, even if you don't raise a support ticket but raise a question in the community, they have multiple community managers for specific products. They'll either answer or tag someone to answer any question. 

Which solution did I use previously and why did I switch?

I previously worked with SoapUI Open Source, and also with ParaSoft SOAtest which is a similar product to ReadyAPI from the ParaSoft SOAtest. That is also a very good API testing tool and I think they recently added smart generator features and other things. I think that perhaps their ID is not very compatible and not as user friendly as ReadyAPI, but it also has very good features.

How was the initial setup?

The initial setup is pretty straightforward, it's just an exe. And then when we execute it, the UI pops up and we can use it. Recently I think they've added a lot of integrations and other new releases. Implementation takes a couple of minutes and we're up and running. 

What's my experience with pricing, setup cost, and licensing?

When it comes to large enterprise, ReadyAPI is good. They also sell specific additional products but they don't force you to buy the complete package. You can select and purchase whichever products you want. The price is reasonable and I don't think it's very high, because of the flexibility - anyone can buy any product at any time.

What other advice do I have?

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. 

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
PeerSpot user
it_user1285470 - PeerSpot reviewer
Program Manager at a tech services company with 201-500 employees
MSP
Has the ability to combine it with different CI/CD tools
Pros and Cons
  • "It has the ability to combine it with different CI/CD tools."
  • "The performance in some cases needs improvement. Sometimes it requires too many resources."

What is our primary use case?

Our primary use case of this solution is to test services to have an understanding of what the request to the service should be and the response. We also use it for performance tests.

What is most valuable?

It has the ability to combine it with different CI/CD tools. You can see tests locally and then you can upload them through a type of digital environment and then they will be implemented, executed, built and deployed. That it is really convenient.

What needs improvement?

The performance in some cases needs improvement. Sometimes it requires too many resources.

What do I think about the stability of the solution?

It is stable. Even if crashes happen, it is very seldom. 

What do I think about the scalability of the solution?

Scalability is actually another really useful and convenient function of this software. It has the ability to pass tests on different machines. You need to have a kind of server on a machine. Then you can instal clients from the other machines and then the application does tests on different machines. It's really convenient as well.

It's used on a daily basis. 

How are customer service and technical support?

Their support can be a bit slow. 

How was the initial setup?

The initial setup was quite easy, it wasn't a problem at all. It took around half an hour to set up. 

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
MonoranjanGorai - PeerSpot reviewer
Senior Manager - Technology at Publicis Sapient
Real User
A user-friendly tool for performance testing and creating mocks
Pros and Cons
  • "The most valuable feature of ReadyAPI is that it is user-friendly."
  • "Performance and memory management both need to be improved because other solutions use less memory for the same amount of data."

What is our primary use case?

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.

What is most valuable?

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

What needs improvement?

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.

For how long have I used the solution?

I used ReadyAPI for about one year.

What do I think about the stability of the solution?

I think that this is a stable product.

What do I think about the scalability of the solution?

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. 

How was the initial setup?

The initial setup was pretty straightforward.

What about the implementation team?

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.

Which other solutions did I evaluate?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
PeerSpot user
Testing Tool Expert at a insurance company with 10,001+ employees
Real User
Good code coverage and quality assurance, user-friendly, and helpful dashboards
Pros and Cons
  • "The dashboards are very good and consolidate all of the tests that you are performing with the client."
  • "If ReadyAPI had more integration with all of the big tools on the market then this would be very useful."

What is our primary use case?

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.

How has it helped my organization?

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

What is most valuable?

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.

What needs improvement?

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 how long have I used the solution?

We have been using this solution for two years.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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

How are customer service and technical support?

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.

How was the initial setup?

The deployment of this solution was very quick and simple.

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Test Manager at a logistics company with 5,001-10,000 employees
Real User
Simple to use and the integration with Jenkins is helpful

What is our primary use case?

I am a test manager, and we have testers who are experts with these tools. We primarily use this solution for API testing and integration. We have an on-premises deployment.

What is most valuable?

The training for this solution is very good. The integration with Jenkins is good.

The interface is ok and they have the ability to re-load tests so that you can reuse them.

Overall, the process is simple.

What needs improvement?

I would like to see a better dashboard for monitoring in the next release of this solution.

The reporting needs to be improved.

For how long have I used the solution?

We have been using this solution for about eighteen months.

What do I think about the stability of the solution?

Some versions of the software have had bugs, but in general, it is quite stable.

What do I think about the scalability of the solution?

Scaling this solution is quite easy. I had some problems migrating to the cloud, with Java, but overall it is easy.

We have about twenty users for this solution, although it depends on the project. Some projects have fewer users.

How are customer service and technical support?

We have not needed to contact technical support.

What other advice do I have?

I would rate this solution a nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free ReadyAPI Report and get advice and tips from experienced pros sharing their opinions.
Updated: November 2022
Buyer's Guide
Download our free ReadyAPI Report and get advice and tips from experienced pros sharing their opinions.