Hi,
There is definitely something wrong regarding object recognition in the latest TC version. Our tests (web-based), which worked flawlessly in previous version, started to fail with "element not found" errors, while the element is clearly visible on screen.
Also, the failing action (typically Click) seems to ignore default timeout and fails well before reaching it. I had to add WaitAliasChild here or there before performing an action on "failing" elements. But this is definitely not acceptable solution. The problem is the random nature of this issue. So while I may add WaitAliasChild on certain actions, it may fail with some other in next run. And so far, I cannot reproduce it with something generic, like SmartBear page, so I have no project to send to support.
