Item: ReadyAPI
Rating: 9
Author: Verified User

Overall Satisfaction with ReadyAPI (formerly SoapUI Pro, LoadUI Pro, & ServiceV Pro)

Use Cases and Deployment Scope

We use ReadyAPI almost daily for API testing and automating our test case suite for future runs. This helps us especially when doing regression testing of many of our components (around 10) and allows us to run the whole suite of +1000 tests in a couple of hours, and this is only for ONE team within the company!

Pros and Cons

Pros

Generating test data
Reusability of test steps
Flexibility on creation of assertions

Cons

Running big batches of tests can break the application or freeze the UI interaction
Creation of result reports
Version control is not possible (branching, merging, etc.)

Return on Investment

Less time between releases
Time saving in QA related tasks
More bugs detected on all phases of development

Key Insights

Do you think ReadyAPI delivers good value for the price?

Yes

Are you happy with ReadyAPI's feature set?

Yes

Did ReadyAPI live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of ReadyAPI go as expected?

Yes

Would you buy ReadyAPI again?

Yes

Likelihood to Recommend

As a QA Engineer, creating, automating, and running test cases for APIs involves 70% of my working time. For this, ReadyAPI has been an excellent tool to do my tasks in a dynamic and time-saving way. On the other hand, ReadyAPI has presented many challenges when more than one person wants to work on the same project. For this scenario, the tool is not suitable since it doesn't have the ability to create parallel branches and merge them together after working on a project.

Comments

Please log in to join the conversation

Speeding up QA tasks

Software Version