Post
by krstcs » Fri Nov 13, 2015 2:45 pm
Ranorex version?
Are you attempting to find a Java element before Java is fully started? The "new" way that Ranorex instruments Java causes these issues if you try to find a Java element before Java is fully started (I don't like the new way...).
You may just need to add a Delay action to your first module in between starting the app and finding the first item.
EDIT TO ADD: The warning doesn't technically cause any issues and your test won't be marked as a failure due to it. However, as a developer, warnings are not good, that is why I don't like this new way of instrumenting Java on-the-fly. In my opinion, Ranorex throws way too many warnings for silly things like this.
Shortcuts usually aren't...