The stability is quite good. So, initially, when we started, we were quite skeptical about the stability because we didn't know much about the features. But then it was quite stable. So we ran it one to five times, and it worked the same.

I would rate the stability a seven out of ten. It is a stable solution. We faced some minor issues, but in general, it was okay. 

Stability-wise, Ranorex has been fine. We haven't had any issues. I think we had a couple of problems trying to update one service pack, but support helped us resolve that quickly. Other than that, anytime we try to run something and hit a snag, nine times out of 10, there's already an update that we just need to download.

The stability is in the range of eighty-five percent of what I was expecting. We still have some issues.

There will be two people executing the tests in another month or two.

Having Italian language support would make the solution a bit more stable.

The solution is stable with no performance, mining code, or repository clone issues. I rate stability a ten out of ten. 

Ranorex Studio is a reliable solution.

I rate the stability of Ranorex Studio an eight out of ten.

Ranorex Studio is a stable solution.

The solution is stable.

The solution has been fairly stable. I've only had a couple of crashes over two years. It's been a pretty decent product that way. Usually, if I have a problem, there's an update that happens fairly quickly and I can update the product fairly easily.

This is a stable solution.

No issues encountered.

We are using out-of-the-box features only with Ranorex Studio and the stability has been good.

I rate the stability of Ranorex Studio a four out of five.

I personally think that, perhaps, it is one of the most stable automated tools available in the market. You can rely on your tests and it won’t let you down.

Stability is fine and we have had no problem with it.

No issues encountered.

The application is more stable by comparison to other products on the market that we have considered for test automation.

It was unstable at times, locking out – especially on any virtual or remote desktop machines. The lockout required resetting Ranorex.

It is a very stable solution and that is a reason why we are using it. While we normally use it for enterprise businesses, we might choose it as a solution for businesses with a range of 50 to 1,000 employees.

No real issues, but I had to force close Ranorex Studio a couple of times, as it was stuck with the 'Not Responding' message for a long time on Windows 7.

The solution is very stable. The only issue is rendering pages if there are too many queries.

Performance was slow for Silverlight applications

No issues encountered.

For a very long time, we were running into crashes with either Ranorex or Ranorex's utility (UIALauncher) which would stop our testing dead in its tracks. These areas would then need to be run test by test, and not in whole batches at a time. We eventually tracked the issue down ourselves to be a rare condition between Ranorex and Windows 8, where both systems were trying to access an element at the same time, and was failing.

There have been no stability issues.

We need some tricks on instrumenting flex based web applications.

Yes, however many issues were in-house. Those that were not, were typically dealt with expediently with an update or offered support.

No issues encountered.

A few times without proper scripting skills the build will be always unstable.

As stated above, we had compatibility issues.

No issues encountered.

No issues encountered.

Stability was an issue.

So far so good.

When Ranorex is upgraded, the compatibility with other projects, in version control, in-house or on-premise, fails on occasion. However, overall, the stability is good.

With the new version of Chrome, some objects are identified differently, so we need to identify those and fix the x-path of the object.

No issues encountered.