ReadyAPI Reviews

Our use case for ReadyAPI is REST API Testing. We essentially test student data because we're working for a school domain that can have different ReadyAPI test cases.

We have the positive test scenario where we collect real-time data and they pass through ReadyAPI, then post different data types for students, such as the school students enrolled in, whether students are full-time or part-time, what courses the students took, etc. There are positive scenarios and negative scenarios that we try to create in the system, including some junk data, then we'll see how ReadyAPI will behave.

ReadyAPI being a tool, means that you can also feed it any junk data, and it's going to post that data, but what we'll be looking forward to is the HTTP code generated towards the end of the day, to see whether it's valid or not.

If there are irrelevant data, for example, there's an address field that can accept any characters, that should be fine, but if we have a name that we need to find and we provide some special characters, then ReadyAPI will give an error message similar to this "Hey, it looks like you're using special characters, so that won't work for me."

There are multiple edge cases, but it isn't about the tool. It's about the applications being used, and there may be some loose ends within the applications. Edge case scenarios could come up, such as the positive scenario and the X, Y, and Z scenario, and ReadyAPI helps us and makes it easy for us by allowing us to post the data. It lets us create multiple test cases, for example, if we have fifteen resources for a test case, we can tightly bundle those resources under one test case, then execute the test case, then ReadyAPI will run everything under that particular test case.

ReadyAPI solves different business problems, and I've seen that, particularly in the education sector where I worked. One is that because ReadyAPI is a licensed tool and it's deployed on-premises, you can host multiple data sets on it. You can host more than a million records on ReadyAPI, and it will still be able to run because it's deployed on an on-premise server. It essentially runs on the CPU, and you don't need to consider resource utilization as much, compared to other tools that depend on memory space, so those tools are unable to run more than fifteen thousand or twenty thousand data, while ReadyAPI is very helpful in that area. The tool is also more user-friendly than other tools.

My primary use case for ReadyAPI is for companies dealing more with backend services. ReadyAPI provides services for accessing these services, conducting testing, generating test data, and offers Docker containers for cloud integration. This capability makes it feasible to integrate ReadyAPI right out of the box into any cloud environment, including private and public cloud environments.

ReadyAPI enhances my workflows by allowing us to use Docker containers based on the ReadyAPI test runner. It helps extend our functional tests, even though we are not heavily using performance testing. It supports a wide range of protocols such as Kafka and GRPC, depending on the project. It also aids in faster feedback to developers, allowing them to implement developments in a sprint without the need for extensive testing afterwards, thus improving our time to market metrics.

Our company uses the solution's SaaS to provide API testing for customers. 

Our quality and automation engineers use the solution. Senior directors randomly open it to ensure that it is working fine. Everyone thinks the solution is convenient to use. 

Most scripts are developed by automation engineers and used by different groups of people who are only comfortable with manual testing. They run scripts but some have challenges with the solution's Groovy programming at first because they are completely new to programming. Other than that, running scripts and using the tool is quite simple. 

The solution offers a wide range of API testing capabilities. 

The built-in Smart Assertion capability allows us to validate API responses quite easily without additional data inputs. You can easily add a table with unlimited rows and columns to pass line input. In contrast, Parasoft SOAtest sometimes requires an Excel document as input. 

Reporting is more robust than other products because test reports can be exported in multiple ways such as JUnit, Excel, or Azure. The most surprising thing is the built-in Azure capabilities because Azure uses a different framework. Previously when we worked on Java or Selenium projects, we used Azure as a dependency and imported that utility. Now, we can complete these projects within the solution's built in functionality.

The integration with GitHup and HTML is very good. 

The backward capability ensures scripts developed in very old versions also run on new versions. 

We have a product, a financial application, that uses a lot of services to connect to our backend systems, so we use ReadyAPI to test those services. Primarily, we use it to build out or mimic the exact services that the development team uses. Second, we use it to build out scripts in Groovy to automate certain scenarios and verify without any manual intervention.

The feature that allows you to import an API collection or a project is valuable. It reduces a lot of manual effort to give the endpoint and the parameters, etc. If the development team gives me the collection, I can directly import it into  ReadyAPI and it maps the entire project so that I can start hitting the APIs directly.

ReadyAPI can be used on the cloud and on-premise, and we are using both methods. We are using the solution locally as a server for test automation. It is local but we are also using Service Pro which is for virtualization and is on the cloud. The integration of the script happens on the dedicated test automation server on the cloud.

We use the solution for coverage of database response validation and service support validation.

ReadyAPI has benefited our organization. I will give a comparison between the open source and the commercial version of ReadyAPI. On average we used to automate five to seven scenarios using the open source version. However, we have seen that we can automate more than 25 to 30 scenarios using the commercial version.

ReadyAPI is where I've created the test tools I've used. I use it for functional testing.

I've used it for testing my code, as in for the unit testing basically, and also the functional tests. We had to perform all types of unit tests. 

We could test all the scenarios of the code, all possible scenarios before it goes to QA. We used Excel files to import the data so that we could test the majority of the data.

The Excel sheet feature is good. It allows for data-driven testing, basically the testing where I can load an Excel file. This was the most useful since, if we had to create a test suite every time for new data, that would typically be a lot of work to fill in the data. When we did it in the Excel sheet, in each row, we could put the data in each and then just copy and paste and simply change whichever column we wanted to change. This helps us test a lot of data at one particular point in time.

The initial setup is easy.

The solution can scale. 

I use ReadyAPI for API testing and functional testing. We have transitioned from using SoapUI to using ReadyAPI, and we utilize it for verifying request and response from the backend. We also use ReadyAPI to generate data based on responses, storing it in our internally-created database.

ReadyAPI is valuable for web service automation and allowing us to generate test cases and automate processes. We use it to verify request and response from the backend and to generate and store data in the database. The Groovy scripting feature is essential, although sparingly complex compared to other tools.

I use ReadyAPI for all things API testing – functional, migration, and security testing. It helps me automate tests, ensure reliability, and spot performance issues. The tool offers versatility, especially in virtualizing APIs and integrating with CI/CD.

The most valuable features of ReadyAPI are its robust functionality and collaboration capabilities. It excels in collaborating with tools like Jira, and its reporting capabilities are a game-changer for me.