What needs improvement in ReadyAPI is its load testing feature because there was a hiccup when my team performed some load testing on the tool. My team had meetings with the ReadyAPI team and tried to get that issue fixed, but it still hasn't improved. This is a shortcoming of the tool, especially when you compare it with HP LoadRunner.

ReadyAPI can improve because it is limited to only SOAP and REST services. They should update the solution to include more protocols so that other people are not limited to SOAP and REST services. Other than would be able to utilize it.

We should be given control over some of the customization of the reports, such as what things are to be included, and what are not to be included.

There is room for improvement in ReadyAPI, particularly in the user interface. I prefer working with multiple windows or tabs, like in SoapUI, rather than the current single-window setup. It becomes challenging to switch between tasks seamlessly.

There is a lot of room for improvement, mainly from the point of view of integrating ReadyAPI into the CI pipelines, and also the scripting aspect into Bitbucket. ReadyAPI is an extremely good and efficient standalone tool, but if you're collaborating on a project, it kind of becomes like a bottleneck. For use as a tool for group collaboration, there is some room for improvement.

I would like to see two new features. Number one is version control with Bitbucket or Git, where we can actually see the scripts and have meaningful pull requests. Right now, everything sits inside an XML file, so it's very hard to review the code that anybody writes. If I have a ReadyAPI project, I want to not only have it on my local machine, but also in a version control system like Git or Bitbucket. At this time I can put the project there, but it's very hard to decipher the files that ReadyAPI exposes. It would be nice for them to have it more like a .gui file where the formatting of the file and the readability of the code is easier for other individuals.

Second, is integration into a continuous integration pipeline, like a CI pipeline, where we can easily trigger, via Bamboo or Jenkins, and execute the scripts and maybe get the response of the results via an email or notification. Maybe it also needs integration into tools like Microsoft Teams or Slack, to get immediate feedback about the results of our execution. Those would be the new improvements I would like to see in their upcoming versions.

The Property Transfer capability could be more user friendly because it is a bit difficult to understand. It works pretty well, but took multiple documentation reviews with some trial and error before getting it right. 

Many times, when I'm testing the code, and it is deployed at a particular server when using ReadyAPI, and I'm getting an error. However, it's actually not an error in the code. For example, sometimes, if I changed something in ReadyAPI, it would not quickly pick up the change. It used to give me the same error repeatedly, and when I closed the application completely and restarted it, it would pick up that change. There was a lag for me while using ReadyAPI.

I don't know as to how it works at the backend, how it picks up the changes, and what functionality or code they use at their end; however, I would want it to be more functional to take in the changes. If I've made a request and I change something in it, it should not lag. It should be able to recognize that this is a change and should be able to pick that change up so that it does not give me the same error over and over again.

The solution does not notify you that you are about to lose your license. They need to give you some small timeframe so you can finish what you are doing and restart without losing work.

The solution is not user-friendly. It is a difficult tool to use. ReadyAPI is slow, taking two to three minutes to start and launch. As your project gets bigger, the time to load takes even longer.

ReadyAPI is not lightweight, it is a heavy tool. There are lots of options within the solution, however, they are not upfront or user-friendly. 

The solution's UI has a clumsy setup. On the left side, you have a list of all the test sites, followed by the test cases and the test steps. On the right side, there are two levels of division. Shown at the top is everything and at the bottom, the values you are passing will be shown. The variables that are getting passed globally within the test suite level will hide somewhere. Even after using the tool for a while, you need to click on a specific button to know that the value is being passed. I would like a UI that shows everything that is important upfront to avoid unnecessary clicks.

If performance improved with the UI changes, I would prefer this solution, as it achieves everything other products and tools offer.

I don't like how they don't have a clear way to manage tests between multiple projects. You cannot have a massive project with all the tests. With multiple projects, you have to get the API created all over again, and I'm not aware of any other solution in case you're using an APIX where you have to define that in all the projects that you are using. That's kind of a pain. You have to keep defining it, and only then can you use it. I like to break up the projects into something that's manageable. However, it makes that a little challenging. 

Sometimes, in trying to make creating tests faster, there are issues. It makes it easier to search and replace variables or anything if I'm writing it and using, say, any of the programming languages. However, with this one, it is very hard. You cannot search for a specific test. Any of those things are impossible. That is one of the big issues that I don't like. I'd often wish I could transition to something like Python or things like that.

In the next release, I would like to see a way by which we can share the code between multiple projects. Each project is an XML file. I cannot use code more than once unless I go and manually copy the code I create in one project into a different one. I'm not aware of any better way to do that.

The solution can be a little pricey.

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.

I would say if anything needs to be improved, maybe it's some aspects of the user interface.

The solution is made up of multiple tools, and the one additional feature we'd like to have is load testing.

The licensing is sometimes a barrier for our customers. You need to have separate licenses for functional tests, load testing and virtual (mock) services.

The support could also be improved to handle requests more quickly.

We have an older version of ReadyAPI and it's not supporting our whole tests, so we have had to migrate some or we've had difficulties running them because they're very old script. Better compatibility or more support for the older versions would be helpful. 

Also, I've been seeing the same UI for many years, since I was using the free version, and the paid version looks the same. I think the UI could be a little bit better.

The product could be improved by including an inherent feature for UI automation. This will allow us to require mobile UI automation testing.

In general, they just need to be better. They have performance testing also. However, it's not that great. It's costly when it comes to a small company, and the features are not that smooth. While the application testing is fine, the API performance testing needs work.

Maintaining your scripts does take work. 

Currently, we are hosting. We have repositories under the Git site, and we are checking our code there. We are executing it with the AWS cloud. The integration with GitHub is not there. They have given us some options. However, it is not workable. We have to check in or pull our code with Visual Studio right now. We have to use Visual Studio to manage that integration, actually.

The UI should be flexible. Currently, the UI isn't. If you want to minimize/maximize it and if you want to use it on a hub screen, you can't use it. It is not that user-friendly. 

Cloud integration should be there as modern work is in the cloud.

ReadyAPI could improve by adding a conversion tool from one file type to another. Import support for multiple file types would be beneficial.

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.

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.

The reporting in ReadyAPI could be better. It can become sloppy, sometimes it works and other times it does not.

Many users will consider this solution expensive compared to the layout. It is more expensive than other solutions.

To generate a test suite in API, I had to create a separate one each time because otherwise it would just override the test. Each API had to be added separately. I thought I could just have one and then create different methods, but I had to add each API separately to create the test for that. That is an area that could be improved.

It would be nice to have some kind of automation or organization.

This solution is a pro version of SoapUI, which is a licensed version. There is a free version of SoapU but this requires coding and knowledge of groovy scripting. The overall scope of this solution is limited and could be improved. 

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.

An improvement for ReadyAPI would be automated import/export with third-party tools. It can also be hard for new testers to learn.

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.

I would ideally like to see a more user-friendly UI to replace what is currently there. Secondly, we never know when there's going to be a license upgrade and it would be helpful to receive an automated email prior to license expiry or some kind of auto-enabled system for license upgrades to give us an alert or some kind of notification before the license expires.

ReadyAPI could improve by having dynamic validation information.

It is challenging doing upgrades and patches because sometimes the environmental variables or suits in the projects get erased. The solution can be improved by adding redundancy to protect the data from being erased. I would like to have the database integration like using the JDVC improved. The last thing would be a more user-friendly way to update the definition and refactor the definitions.

Areas for improvement include the security files, endpoints, and process sessions. ReadyAPI should also include the ability to add and modify existing files.

I would like to see a better dashboard for monitoring in the next release of this solution.

The reporting needs to be improved.

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. 

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