We just raised a $30M Series A: Read our story
2019-08-26T06:42:00Z

What needs improvement with ReadyAPI?

11

Please share with the community what you think needs improvement with ReadyAPI.

What are its weaknesses? What would you like to see changed in a future version?

ITCS user
Guest
88 Answers

author avatar
Top 10Real User

Version control does not work well. It's has a git API which is defective and doesn't work well with our version repository, Bitbucket. We do all version control using git bash (command line driven), and sometimes we have to try several times to as there still hooks into the ReadyAPI git API which cause issues.

2020-12-01T16:38:00Z
author avatar
Top 5LeaderboardReal User

It doesn't have connectors to the NoSQL database. This is one of the things where they do not have a very solid strategy today. Other solutions have an in-built mechanism where I can directly and easily connect. An API is more around a user submitting a request on the frontend. It then hits the backend, puts the data, and responds back. If I am hitting MongoDB or NoSQL databases, I do not have ready-made inbuilt solutions in ReadyAPI that can easily help me in automating it faster. In our organization, we deal with NoSQL databases, and therefore, we need Groovy. We just cannot have a connector from ReadyAPI to do that. I have to write Groovy scripts. If you have themes that are predominantly using MongoDB, it leads to more maintenance and support activity because we are introducing more code into our commission. In terms of additional features, it can have cloud support. This is one of the things where we are getting into cloud support. We'll see how it works, but it is one of the doubts that we still have.

2020-11-18T04:31:53Z
author avatar
Top 5LeaderboardReal User

The reporting is not very robust and needs to be improved. They give the pass or fail criteria, but we need to know the history and also why it has failed. Essentially, the details that we see in other tools are missing. This is a request that we have made and we hope that these are implemented in the next version. They should include support for integrating with Xray, which is another test management tool. More generally, they should have a larger scope when it comes to integrating with test management tools.

2020-10-29T21:29:38Z
author avatar
Top 5LeaderboardReal User

I think the security testing with API could be improved as they provide limited templates. It would be helpful if they provided us with more capabilities and the flexibility of adding more custom verification for the security testing part of ReadyAPI. Basically, some additional features would improve the product.

2020-08-16T08:00:21Z
author avatar
Top 20MSP

The performance in some cases needs improvement. Sometimes it requires too many resources.

2020-03-30T07:58:00Z
author avatar
Top 10Real User

We stopped using this solution because of issues with scalability. Performance and memory management both need to be improved because other solutions use less memory for the same amount of data. I think that there was an open-source version, with a lower cost, then this would be a recipe to get into bigger markets.

2020-02-05T10:15:27Z
author avatar
Real User

This solution is focused on web services, but it should be expanded to a complete test manager. For example, in the test suite, you can include a UI test, but this is with another tool. It is not fully integrated. ReadyAPI is not fully integrated with all system ecosystem tests. If ReadyAPI had more integration with all of the big tools on the market then this would be very useful.

2019-09-27T04:38:00Z
author avatar
Real User

I would like to see a better dashboard for monitoring in the next release of this solution. The reporting needs to be improved.

2019-08-26T06:42:00Z
Learn what your peers think about ReadyAPI. Get advice and tips from experienced pros sharing their opinions. Updated: October 2021.
542,721 professionals have used our research since 2012.