What do you like best?
Ranorex is a fairly powerful test automation platform, particularly given it's price point. Compared to other tools I've used (QTP\Quality Center, TestComplete, Selenium), there are many benefits out-of-the-box other than price:
- reporting libraries
- support for multiple browsers and devices
- more robust IDE and debugging capabilities
- native .NET, so no need to use archaic scripting languages or to learn new ones
- for us, being presented via native .NET libraries means we can actually forego the Ranorex IDE (built upon SharpDevelop) and perform all development within Visual Studio. The benefits of this include
-- native .NET compiling and debugging - better than sharpDevelop's and far better than QTP\Selenium
-- easy integration with tools we already use: TeamCity, SVN, nCover
-- QA and development use the same tools... can share projects, code, resources
What do you dislike?
UPDATE APRIL 2017:
With the v7 release, Ranorex now supports running automated tests against the EDGE browser. However, if (like us) you counted on their native support for Visual Studio, and have developed your framework within Visual Studio rather than the Ranorex IDE, you've been left out in the cold. Ranorex has chosen to keep their WebDriver integration private, meaning that people who are referencing Ranorex libraries with Visual Studio still have no way to run tests against the EDGE browser. According to their Forum and User Voice sites, there is no plan to change this. Good news is that Telerik DOES support Edge, so for those of you in our shoes it may be possible to migrate...
Limited third party integration. We can roll it ourselves, but out of the box integrations don't meet our needs most of the time.
Foreign product - which isn't bad (and there is a COE in Florida). However, the user base seems small compared to other vendor's offerings. This isn't mush of a problem generally, but when you need answers fast it can be a drawback
Not a lot of information about how to use... API is documented virtually without examples. Advanced usage information practically non-existant
License manager is slow to release licenses locked to clients that have completed work...
Recommendations to others considering the product
APRIL 2017 UPDATE - IF YOU PLAN ON TESTING AGAINST THE EDGE BROWSER, STICK TO RANOREX'S IDE. IT ISN'T NEARLY AS FLEXIBLE AS VISUAL STUDIO AND ITS DEBUG PERFORMANCE IS FAIRLY POOR, BUT EDGE TESTING IS ONLY SUPPORTED IF YOU USE THEIR IDE.
If I had to do it again, I think that I'd have us stick the Ranorex IDE. It isn't as powerful as Visual Studio in terms of debugging, but there are a lot of features built into the "system" which many folks would probably want to take advantage of, such as visual test ordering\re-ordering, the new remote deploy and run functionality, multiple test drivers available natively, at the test case level...
If going the route we followed - into Visual Studio - spend a little upfront time building a robust test runner. We ended up putting together a nice test driver, but it works on the local machine level. Bringing it back out the the network can save a few headaches...
What business problems are you solving with the product? What benefits have you realized?
well, obviously test automation. After performing a POC with the Ranorex IDE itself, we were able to move to Visual Studio (reference Ranorex core libraries) and build a fairly robust test framework pretty quickly.
We are able to run thousands of tests against various app configurations and on various OSes pretty easily
We've done some POC work with mobile device testing and are reasonably satisfied with what we've learned, at least for Android devices.