I rate ReadyAPI Test 10 out of 10 for ease of setup. It's straightforward unless you have a code for a license key. You need to in inject a license key if you have that. You can input the license key and it'll be mapped to the server. Sometimes you can put all the licenses on a server and use the IP of that server. You can have a HERE license or an individually tagged license. 

Initial setup wise, the local one was straightforward, but doing it on AWS took some time for us. We were doing it for the first time on AWS, so it took some time for us to understand and complete the setup.

The setup was quick and easy, but integration with other servers, for example, the Jenkins server with the AWS server via SoapUI Pro, took some time. Otherwise, installation on just the AWS server took just a couple of minutes, but integrating it and having a working setup took almost a month for us, including all the approvals and the delays around the approvals.

Setting up SoapUI was relatively straightforward. Generally, we don't do the setups ourselves. The IT team takes care of the installation and provides the software to us in development. I believe it takes about 15 minutes, but I'm guessing, so I'm not very sure about that.

The initial setup was straightforward. You simply have to download it and begin your work.

The setup was a little bit complicated because we need to download the external JAR to support the Oracle database connection. We had to download the extra JAR for the SoapUI. We also had to do the Selenium setup. We need to create folders where we could place these — that Selenium standalone and the JAR. That was a little bit complex but not too bad. This was our first time, but if we had known what to do, then it would have been easy.

It was not straightforward because we had to integrate with Selenium and the external JAR was needed to set it up and automate the UI. But I was still able to do it by myself in two to three hours.

I implemented the solution; it was straightforward and took a few minutes. 

The initial setup is not complex. It's very easy. You just need the endpoint, and you add the project, if you want REST API, if you want XML, whatever, you can just add those from the file system. It's very simple. It's very easy for anyone. The entire setup only takes about one hour.

You only need one person to handle the deployment and maintenance. 

I had a bit of experience, so the automation was not difficult for me. When I was training an individual who was new to ReadyAPI, it was a bit tough for them to understand things. The initial setup is complex for a new user. I rate the ease of setup an eight out of ten.

If you don't know the structure of web services, it could be complex to set up. 

I do the testing. I do not take care of the deployment. In its deployment, two developers were involved. All three of us are also responsible for its maintenance.

It doesn't take too long. Once it is deployed, I need to check if it works as expected, and the behavior is what is expected in production. 

Setting up SoapUI is straightforward. I just downloaded it and started using it. That's the good thing about it. I don't have to go through all those things.

The initial setup of SoapUI Pro 

The initial setup needs an automated headless installer.

I don’t recall, but I do remember it was fairly simple. Install and add the license and I was good to go.

The initial setup is straightforward and it takes less than 30 minutes.

The initial setup was simple and straightforward. It took a short time to deploy.

The setup was straightforward.

Setup was easy. You just run the installer and set up your license.

Initial set-up of program is straightforward, preparing own project with dynamic path e.g. JDBC connection or endpoint is more complex.

Very easy to setup and use.

Straghtforward, when it works! Impossible when it does not.