ReadyAPI Reviews

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 use ReadyAPI to build our own testing cases. We are able to use the same testing cases to complete automation tests, performance test team and security tests at the same time.

This solution is very intuitive. Once you finish your first few testing cases, you can change several parameters and create lots of testing cases. You could use the same testing cases for different purposes such as automation, performance and screen testing.

Many users will consider this solution expensive compared to the layout. It is more expensive than other solutions.

I have used this solution for a year and a half. 

This is a stable solution. 

This is a scalable solution. 

This is a lot of documentation provided for support but they still need some important information to be added. For this reason, I check other communities discussions and forums.

I would rate the support team a six out of ten because they haven't always been able to solve my issue. 

Neutral

It is easy to install, but it takes time to set up your testing environment. You need to figure out how your API works and save the mutual authentications. You need to know the specification of your API partner and this takes time. It is not difficult to maintain.

I introduced the solution to my previous company. I just read the documentation and then got started.

It is more expensive than other API testing tools. For example, Postman is an open source tool and is free to use. ReadyAPI is a commercial tool and licenses. need to be purchased. It costs approximately $200 000 Taiwan Dollars for three years.

I would rate the pricing a six out of ten. 

I have used Postman before, but not for a long time. I definitely prefer ReadyAPI. It is very easy to use and it's very easy to learn. They also offer online virtual training and certifications. 

The documentation provided is good but it could be more comprehensive. 

I would rate this solution a seven out of ten. 

The primary use case is for APIs and API testing.

The feature I find valuable is project management. It allows us to organize our test cases and suits inside the project. It also gives the ability to store the variables in terms of properties so they can be used across test cases and test suits, so they can be placed at the project level or test suit level, or test case level.

It is challenging doing upgrades and patches because sometimes the environmental variables or suits in the projects get erased. The solution can be improved by adding redundancy to protect the data from being erased. I would like to have the database integration like using the JDVC improved. The last thing would be a more user-friendly way to update the definition and refactor the definitions.

I have been using the solution for three and a half years.

The solution is stable.

The solution has met our requirements and appears to be scalable.

The initial setup is straightforward. I give it an eight out of ten for simplicity.

Before choosing the solution I evaluated Postman. The selling point for the solution over Postman is the project management features.

I give the solution a seven out of ten.

I manage a testing team made up of four people including myself that use the solution daily.

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. 

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.

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 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.

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.