From installation to having everything set up for automation, the deployment takes around one day at most.

You have to request Ranorex, the license key, and tell them why they need the solution. What are you gonna do with it? Then they'll provide you a license key, and then you'll be able to install it. So that's just one of the hurdles. 

Then, you will get set up files. You can download the storage. You can easily set up by downloading or just visiting their site. With Ranorex, the main thing is that you have to request the setup, which is followed by a couple of details. 

We managed the deployment in-house. We have experience with installing automation tools, so no external assistance was needed. Just one person from my team worked on it.

But we didn't reach the maintenance stage. We conducted a POC, but we haven't started full-scale automation, so there hasn't been a need for ongoing maintenance.

However, we did reach out to Ranorex's support for help with specific issues, and they were reachable and provided guidance.

We implemented on our own, without the help of any consultants or partners.

My team implemented it for a customer.

The solution was implemented in-house. 

We did the implementation of the solution ourselves. We only needed help with licensing. We had two to three people that did the implementation.

We did not use an integrator or consultant.

We handled the deployment in-house and did not need the assistance of consultants or integrators. 

We implemented using an internal team. One thing I would say is that if you have the choice I would always get your automation completed by a professional team rather than manual testers looking to become automated testers. Whilst the costs may seem higher initially I’ve yet to see a manual team introduce robust, maintainable automation anywhere near the timescales that a professional team can achieve. Automation is an art.

The setup was mostly done by our in-house team with the occasional support from Ranorex. 

We implemented it in-house as the setup is easy and straightforward. It just requires some time to create and implement a good test automation workflow, however, this is irrelevant to the test automation product itself.

We use two engineers for the deployment of the solution.

We implemented the product in-house. The only tricky part is if using their floating license option, the configurations need to be set up across the network. My current organization is small so we experienced no issues. Implementing on a much larger scale could be a bit tricky.

We implemented it with an in-house team with the help of a vendor team, but I expect that for companies with less strict network security policies, it would be less of a problem.

Implemented this one through an in-house team.

In-house implementation. It's great to have Ranorex paired with Bamboo and AWS

We are doing all the installations and developing ourselves. So everything is in house.

In-House. It's pretty easy to implement Ranorex. The documentation itself was sufficient.

We implemented it completely by ourselves. The implementation depends a bit on the requirements of the organization I think.

in-House

We did the implementation by ourselves, it was not that difficult to install and add the license key.

The solution was implemented as an in-house one. There wasn't need to hire the vendor team since the project by itself is not that big or complex.

All implementation is done in house with a small team of three to four engineers. My best advice for implementation is that if you can, try to go through a pure programming route with your implementation, and not through the recorded modules. While it may be more time investment in the beginning, it will pay off in the end because you will have a more robust suite that will scale much better then using the "standard" Ranorex Route.

We installed and did the set-up in-house.

We performed implementation in-house. The difficulty of implementation can scale with the size and complexity of your software project, it can become quite a daunting task.

My advice is that you back up and test your current project in a separate environment. Start small, and dedicate time to learning the different Ranorex tools and features.

We are a QA team capable of writing automation code, thus we implemented everything in-house. Before implementation, think hard on how to structure your automation code, especially your adaptors.

We did it in-house.

The initial set-up was quiet simple, and there was no need for any external help.

We implemented it in-house.

We used an in-house team.