ReadyAPI Test Reviews

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

The product allows us to uncover any potential issues early on.

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. 

ReadyAPI has the power to enrich all the technical work. You can achieve any complex task using ReadyAPI. I can also do UI automation with ReadyAPI. In a few test cases, we want to check the API and the equivalent UI. I download a job and write a piece of Groovy or Java code. It's almost the same in ReadyAPI. I can do that in a single test case. ReadyAPI is a powerful tool because you can do anything you want, but only you need to download the right set of jobs and produce the right set of code.

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.

The utmost importance lies in the performance of the application.

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.

We run around 10,000 different validations, including database validations, and we can complete the entire aggregation in less than one hour. This includes file validations, database validations, and response validations. All 10,000 plus the test conditions include all these three types of validations.

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. 

The solution has some good scanning features. It scans API descriptions to generate functional steps and then runs functional tests. It then gives the opportunity to add some assertions and then finally to integrate them into a grid pipeline, like on Jenkins, and generate G-units or generate reports that are in G-units or J-units format.

We chose this tool because it's lightweight, simple and intuitive. It's open software, it has a command-line interface that is very important for integrating later in the bid process and to get decent reporting. It's a good tool. 

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.

SoapUI is very useful. Before we started using SoapUI, we had to do everything manually, which is very time-consuming, and there were a few things we couldn't validate. Using SoapUI made everything easier. You can do six to seven hours of work efficiently, and it's more flexible to use. Before, we had a manual Excel sheet folder where all the manual details were located. Let's say I am developing a particular part of it and it is assigned to some other company. Then we wouldn't be able to test it ourselves. Our client would lack confidence if we were doing manual testing. So that's the reason we used to have one or two teams. One would handle the development, and the other did the testing. But once we had been introduced to these automation tools, it was pretty much straightforward. With SoapUI, you can validate the test kits just by looking at the output screen. Now, we don't really need to have separate teams for development and testing. 

We can do all the automations at a nice pace in less time, so we don't need to spend two or three days testing. The times are changing fast with these new technologies and software solutions, so our relationships are fundamentally changed by these tools. In the future, we'll see more advanced versions of these tools, wherein everything will be done by automated processes. One day we'll be able to do complete tests in just five to 10 minutes.

We were using SoapUI to do UI automation.

Using SoapUI's automation suites to run all our test cases saved us a lot of time. Running 300 test cases takes about three to four days. When you automate all that, it takes only two to three hours.

We used SoapUI for Web API Automation as well as UI automation. With SoapUI's automation suites, we were able to make it very easy and readable by any other user. The test cases were written in a given format where we were able to fulfill the prerequisites by the given statement. We were able to very easily load the data into the database as a prerequisite for the UI and input the given steps using the GUI. 

And when we got to the part where we were performing the action in the UI, the integration between Selenium and SoapUI was very easy. In that step, it made it very easy to validate the UI. 

SoapUI is easy to learn. When we get a new tester on the teams, they can pick it up quickly.

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.

SoapUI provides us better usability and better features. People from different domains can use it effectively.