The full deployment of Katalon Studio can be heavy. If we have to install the complete Android Studio, it takes a lot of space on the system. Otherwise, the setup is not that complex. They have improved over the years, it is much easier, but space is one constraint it has. Once you install Android Studio completely, it would impact the performance of your machine. 

The initial setup of Katalon Studio was easy. The initial setup of TestProject was easier than Katalon Studio's setup phase.

Understanding Katalon Studio and deploying the tool takes half an hour.

For Katalon Studio's deployment to happen, you need to download an EXE file for installation, after which you need to open the application and check whether it is a product compatible with your IT environment. After following the aforementioned steps in my company during the solution's deployment phase, we realized that Katalon Studio was not the specific tool we wanted, causing us to consider TestProject.

The solution is deployed on the cloud.

It is easy to install. It takes five minutes to complete and requires two people for installation. The complexity of maintenance depends on the automation framework.

The initial setup is simple and quick. It takes less than half a day to complete.

We use the standalone web application. The initial setup is not a big task. We can easily install Katalon. The website provides all the steps for installation. We can follow the steps and easily install it.

The initial setup of Katalon Studio is easy. It took less than 15 minutes to deploy the product.

The product's initial setup is not at all difficult.

For Katalon Studio's deployment, you can easily just download the ZIP file and install it on your system, and it's all set to go. Nowadays, there is an EXE file, which you download and double-click on to install it on your system, making it very easy to install and set up. Probably, the setup phase of the tool with integrations may take some time, but it is very easy to use. There is a beautiful UI and UX that Katalon Studio provides its users. With Katalon Studio, you can easily just provide the URL of your project management or test management tool, and then you can verify it, link it, and then you can do one-to-one mapping of your test cases as well.

I rate the normal setup phase of Katalon Studio a ten on a scale of one to ten, where one is difficult and ten is easy. For iOS specifically, Katalon Studio's setup phase was difficult.

The solution is deployed on an on-premises model.

Just one person can deploy the solution in a couple of hours.

The tool's setup is straightforward. You can just download and use it. I would rate the solution's setup a nine out of ten. The tool is hosted on the Katalon server. 

The initial Katalon Studio is simple, you only need to download and register, and it takes approximately 10 minutes.

We did a POC and then did the implementation and then go with it.

The solution's initial setup has medium complexity. It takes work to identify AJAX controls and then implement them. There should be an inbuilt method or features designed to handle these controls providing us with a straightforward deployment process.

The overall time taken to complete it is ten minutes. Although, for multiple integrations, it might take 20-30 minutes. Also, its maintenance takes time in case of UI changes.

The initial setup is simple. We can easily download the file.

The tool's deployment is easy but difficult for iOS devices. Deployment speed is pretty quick.

The initial setup wasn't complex. It was straightforward. I found it to be quite easy.

The initial setup of Katalon Studio is easy. There was some confusion when we were upgrading the versions. The implementation can be done in a few hours.

The initial setup is straightforward. Without using the manual, it took me approximately 50 to 60 hours to start being very productive. 

We did not find the initial setup to be overly complex or difficult. it was very straightforward. It was simple.

We have a team that can Google questions and find information online pretty easily if there is any maintenance that needs to be handled. We tend to handle the maintenance aspect for our clients. 

The initial setup was straightforward. Once we had approval for the product, it did not take long to roll it out across the organization. I'm still building a case for it, although there isn't much in terms of roadblocks or issues.

The initial setup was not complex at all. The installation was very easy. The configuration, as well, was very straightforward. There are videos online that really help in walking you through the process. If you get stuck at any point you can watch them and they really help navigate you through the process.  

I can't recall exactly how long the process took to complete. 

In terms of maintenance, basically, there was one DevOps employee who was doing everything related to the maintenance part. We also had a manager heading it up. We were basically in different scrum teams and we were working on the same product. We only needed one person to look after everything and manage it as necessary. 

The initial setup was a local setup; I simply downloaded it from the website.

It is actually a complex setup. If you want to do it in a good and sustainable way, it is complex to create a model, but if you want to just test things out and very quickly try out this product, then it is easy to get started. So, it is complex to create something that is sustainable. 

Overall, it took about one and a half to two months, which included many test cases implementations. The setup was done within a week.

It does require maintenance, but the maintenance of the server is up to your company policy. It depends on how often you patch your server, and how often you upgrade Java. The maintenance of the test scripts depends on how quickly the product changes. So, it varies.

It was easy. I just had to double-click on Mac.

The initial setup of this solution is straightforward.

We did not find the initial setup to be very difficult or complex. It was straightforward. It was easy. A company shouldn't have any trouble with the process.

We were using the trial version and it was very easy to install.

The setup of this solution was very simple for a simple web application, and deployment only took 20 minutes.  However, for multiple applications, the lack of integration makes implementation a longer process.

The initial setup was easy and straightforward. 

I didn't have any requirements.

It took a month to deploy 10 automating services.

The initial setup is straightforward. You just download a ZIP file, copy the contents of it into a directory, and you're ready to go. It is a bit like installing Eclipse. The deployment is quick.

Initial setup was easy.

It's tricky to say whether the setup is easy or not in an absolute sense. In some cases, it's very straightforward, and in general it is easy to set up. We usually take a few days for the installation of Katalon Studio.

It wasn't complex.

The initial setup takes a couple of weeks. That is not really too long for a product like this. It was relatively easy to do.  

The initial setup is really simple, which is one of the good things about this product.

It was really easy to implement and use. I look for information online from Katalon before we started our testing.

The initial setup is quite straightforward.

We deploy per release, where every two weeks we deploy a new release.

Our implementation strategy is to create the test case first, then to create a test suite in the object repository. We can add all of the endpoints, and the calls for the endpoints. We run the tests through the suites, which will test all of the test cases. It is then run with the Jenkins integration and Slack integration to get the results, and what has passed or failed will be clear.