We have around 30 testers using the tool to write and update scripts for manual and automated testing. ReadyAPI Test is useful for API testing in a complex environment. For example, when we first started using ReadyAPI, our customer had a mainframe system. He wanted to log in to the mainframe system and use the data to request the payload of an API, so we needed to set up an API to get the response. The values from the response should be equal to those in the database.

Once everything is matched, then your test case is passed. In a single test case, you need to invoke a mainframe, API, and DB environment, then generate a custom Excel report. At the time, we had no reporting tool. Using our custom jobs, you can invoke a mainframe environment from ReadyAPI. ReadyAPI gives you a platform to invoke the custom jobs from the tool, so you can write the code. In ReadyAPI, you can write Java code because a Groovy snippet is almost always Java. 

Most of our automation is for REST API, and it involves requested response validation, database validation, and some level of UI automation/validation. The UI is done using Selenium, and SoapUI Pro is used for database validation and file-based validation.

I use the product for data, regression, performance, security, and functional testing. 

We use to do end-to-end testing on mobile devices. Our team has about 50 members, but there are around 500 to 600 people in the whole organization.

We use it for API testing, functional testing, and performance testing. It helps automate testing processes and ensures the quality and reliability of APIs and web services.

We were using SoapUI to do UI automation.

For now, our primary use case is for basic functional testing. We have six people using this solution, they are testers and developers. I'm a software test engineer and we are customers of SoapUI Pro. 

Currently, I'm using this solution to test the API email applications

Usually, our clients are in IT. They have web services - more than 300 web services. We are calling those web services in our front-end applications. In order to verify the actual values from the web service, we use SoapUI to connect with the current client endpoint.

We use the product for functional automation and functional validation. We also use it to write our scripts to check performance in certain cases.

We use it for testing SOAP protocol API. We also started with the REST API recently. We use it to manually test as well as to automate a few API calls.

An automation tool not only always has the purpose of redefining the APIs after their functional or performance testing, but also provides an easier execution platform for the APIs so that they can be easily consumed by the future developers who are yet to work on them.

We primarily use the solution for automatic testing and API testing.

We are using SoapUI Pro as an API testing tool. We do API building, testing, and tracking.

The primary use case of this solution is for API testing.

We were using this solution for unit testing.

Functional and load testing of the APIs we've developed internally and the APIs we've consumed from external parties.