I would rate my experience with the initial setup around eight out of ten, with one being difficult and ten being easy. It wasn't overly difficult; it's mainly an installation process with a learning curve on how to use the tool effectively.

It was deployed on-premises. We installed it on local machines. They have runners. So you can buy a license to run and trigger the execution from your own machine to different servers.

Setting up Ranorex is really straightforward.

The initial setup was complex, but not because of Ranorex Studio. 

This was an internal problem for us because the installation required an administrator and I am not an administrator.

We had to repeat the process a couple of times as a result. For the Ranorex Studio side, it was fairly straightforward.

The deployment method was on-premises.

It was straightforward and very easy set up.

The solution's framework was already in place when I joined the team and my focus was importing utilities. 

The initial setup of Ranorex Studio is easy. The deployment took approximately 10 days. Our only difficulty was choosing what hardware we wanted to use.

I rate the initial setup of Ranorex Studio an eight out of ten.

The initial setup is straightforward, it is not a problem.

In general, I believe it is ordered through the 104 internal portals, so it takes 30 minutes to an hour to install.

There's only one person who maintains everything. There are no major items that require to be maintained. Everything appears to be in working order. It's fine because it comes in a package.

The solution's initial setup process is easy and less time-consuming. We have to follow the steps mentioned on its website for installation. It is easy to maintain as well.

The initial setup was pretty straightforward. The only complexity was due to the fact that it uses a licensing model where any of my remote systems has to talk to a service on my main machine that has to use a specific port. Sometimes I have some issues with that. Initially, it took a while to set them up and get them to be able to talk to each other. Once I got it running, was been pretty consistent and has been for a while now.

The initial setup was straightforward. Just install it and you’re off and running. The software installation was also quick compared to other products. Admittedly we had an inbuilt framework that we’d built available to us so we just wired Ranorex into that framework.

The initial setup for this solution was straightforward. It took us a few days to set up two virtual machines - one for the database and another for the clients and Ranorex.

Setup is easy, anyone with an elementary knowledge of programming should be able to work with it right away. Otherwise, there is comprehensive user guide, some nice video tutorials, and an excellent community forum.

Ranorex Studio is straightforward to do the initial setup. There is a lot of flexibility given to understand the functionality, it's very easy to understand the existing functionality, and what is available in desktop applications.

The full deployment does not take more than a day with everything updated and the scripts running.

The initial setup is straightforward.

The initial set-up is very basic, download the executable and run it just like most other programs.

In the beginning we had small problem with configuring Ranorex License manager in our infrastructure due to our firewall and proxy settings, but with the help of Ranorex support we quickly found the fix to solve the issue.

Setup is simple and straightforward. The integration with SVN was simple, and the license server was very simple.

Straightforward, easy to setup, great support from Ranorex team for initial setup and initial training.

The initial set-up is easy for an experienced person, and for technical QA, without a lot of automation experience. Ranorex is a great tool to learn automation with pleasure.

For me the initial setup is straightforward. There is more than just the testing administration to sets up, but also you configure the tech management and reporting management. It is a few things to do, but I am familiar with them so it is not hard.

It was straightforward with no complexity in setting up. The documentation is crisp and clear.

The set-up of Ranorex itself was very straightforward. but getting the tests stable on a remote server required a bit of practicing. Also, we had to find a way to run the tests without a real screen and use it with Jenkins but actually in the end it’s not hard to learn this at all.

The initial setup was easy.

I had a problem almost one week after implementing. From the beginning, you must look at the webinar. If you don't watch the webinar, it will be hard to work with the solution at the beginning. 

Very simple

Setup and installation was straightforward. If you watch the online webinars, you can easily start with recording test steps. If you have previous experience with C# or VB.NET in visual studios, you won’t have any problems developing in Ranorex. Otherwise, you can find a lot of information online how to expand your recorded modules with additional code.

I wasn't involved in the beginning of the project.

Setup and installation of Ranorex was extremely straightforward. However, getting the initial script running was a bit complex, as we soon found that parts of our application weren't accessible through Ranorex, and the way Ranorex wanted us to create scripts wasn't intuitive to us. We eventually opted out of "their way" of doing things, which is more for a non-coding QA person, and opted for a 99% programming method.

The initial setup was completely straightforward.

It was straightforward. You install the .exe and you are done. 

It was pretty straightforward.

All we had to do is to link a couple of .dlls into the automation solution. The complexity was in how to structure the adaptors so that the code maintenance effort could be kept as low as possible, but that had got nothing to do with Ranorex.

It's straightforward.

Setting up Ranorex and jumping into your first test suite is extremely easy, even for non-programmers The record/playback feature makes it easy for anyone to automate a test case..

It was simple. Everything was inline, but some features needed support – like creating virtual platforms for testing. Connecting to a real IOS was impossible without a dev account.

Easy installations no hiccoughs.

Very easy – desktop application installation. It's almost one click, and only takes five minutes.

It was very straightforward, just click on the EXE file and it will do the rest automatically.

It was simple.

It was straightforward.

It very straightforward. So good, and easy.

The setup is easy.

It was simple.

I would rate it average -- neither straightforward nor complex.