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.

We use the solution for validating the web services for the code which we are receiving from the onshore team. We configure the ReadyAPI automation with the web services. Then we validate the web services, such as providing the request and response, if the web services and the backend are working correctly. We are also using open banking services to validate the validity of these services. We are sending a request and getting a response for that request.

We have test cases set up in ReadyAPI and we use it with Swagger. We are a software development company and we used to use ReadyAPI to test our internal applications. We mostly create the backend application based on the API and mobile or web applications that use these APIs. We also used to develop our own APIs. 

We have now expanded our usage and also include quality assurance. For example, for functional testing, we start calling the URL and check the HTTP code and error code. We also check the format and input and then process the output. 

Our overall use case and usage of this solution varies from project to project.

I primarily use the solution for monitoring tasks. 

I was using it for API testing. I was not using it to do any performance testing.

It's for API validation. I was working on a banking project and I used it to check the response time.

I'm a test lead person so we have multiple teams who work under me and they use WebView API, other members use LoadRunner, and some members just use other automation techniques. They use Selenium and Java automation.