What is our primary use case?
We use ReadyAPI for API testing. The APIs are the communicator factor, services, and web services, which we create in a REST model. The REST APIs are there. So we use this ReadyAPI to test our services, which we created using REST.
We do some user/user testing there. We do change the services as well. For example, our company is basically on the banking side, so we do FinTech service creation. Therefore to test FinTech services, if you want a complete example of the user journey, then we create a few services for customer creation. To inquire about the same customer, we do have other services. To modify or delete the same customer, we have another service.
So we use this product to check the user journey for the services, We do all the changes using the ReadyAPI. For all the variables, whatever we use, we use ReadyAPI.
How has it helped my organization?
We used to use SoapUI for manual testing. We only used to do manual testing, however, then, when we considered ReadyAPI as a tool, we bought some licenses for it, and we started doing some automation using ReadyAPI.
Eventually, we enhanced the whole automation, and how it should get integrated with the hardware, or another tool like Jenkins for CI/CD automation. That is the reason we switched over. That's the best benefit we've seen.
What is most valuable?
Personally, I like two features. The first is adding multiple assertions. Another is having the ability to change the services and provide some variables.
The solution is pretty straightforward to install.
We find the product to be scalable.
For the most part, the solution is stable.
What needs improvement?
When we wanted to install the ReadyAPI on Unix or Linux environment, we found it to be really difficult. We had difficulty installing the license there since it is headless. We could not do the installation for these two environments. That is why we were not able to do a headless integration. It would help if that was possible.
It is very slow sometimes. If they could improve its performance, it would be really great for the users.
This is an expensive product. There are other options that you can use for free.
For how long have I used the solution?
I've been using the solution for around four years.
What do I think about the stability of the solution?
The performance could be better as it often is quite slow.
While the solution is stable, sometimes we don't understand that the latest version is available. And due to some time constraints, like priorities surrounding the projects, we cannot install the latest version of ReadyAPI. And if we don't install the latest version of it, it starts behaving a little weirdly, like slower than usual, or it can crash sometimes.
What do I think about the scalability of the solution?
We have 30 users on the solution right now.
It is a scalable product.
We use the solution on a daily basis. We may not expand usage. We are also looking for some other applications or tools, since ReadyAPI needs licenses. That is the reason we are planning on moving onto some other tool, which is open-source.
How are customer service and support?
Mostly, support is fine. We found, while installing the licenses, we got a quick response from the technical team. However, I forgot how to install the repair license on the Linux and the EMS environment. If that information, was more readily available, I'd say I'm happy with the technical support of it.
Which solution did I use previously and why did I switch?
Before ReadyAPI, we used to use SoapUI. We wanted to enhance the automation and SoapUI was manual.
How was the initial setup?
It is really not so hard to install. If we download the latest version from Google or somewhere else, we can install it easily. The license installation is simple, so I don't think it's difficult to install.
We have about 30 people that can be involved in a deployment.
How long it takes to deploy the product depends on if we have small use cases for execution. In that case, it takes less time. However, for huge bulk data, where we are using bulk data and huge amounts of data, take more time for deployment and execution.
We do the executions and deployments on a weekly basis. We get the reporting software and use report portals. If there is anything for us to do when we get the report, we only fix the glitches there. Therefore, there is some ongoing maintenance and tasks to handle once it is set up.
What's my experience with pricing, setup cost, and licensing?
We bought our licenses from SmartBear only.
The cost is in a higher range, and that's the reason we are planning to move. Otherwise, performance-wise it is good. If the price will reduce, we might stay. We have many other applications and tools available in the market, which can be considered as replacements for ReadyAPI, and they're free, so why pay?
I cannot speak to the exact cost of the solution in general. However, there are no additional costs or fees that you need to pay, beyond the license itself.
Which other solutions did I evaluate?
We are looking into different products as we may move away from this solution in the future.
We need a product or maybe a tool that can be used for API testing. Basically, right now, for my team and my product, we do API creations and we need a tool that we can use for API testing. We want something open-source.
What other advice do I have?
We're an end-user.
It is deployed on a cloud now. We have all services, APIs, which had already been deployed on the cloud, and the ReadyAPI's being used to test the same services.
I'd rate the solution six out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
*Disclosure: My company does not have a business relationship with this vendor other than being a customer.
