Forum Discussion
Yes, all of us, a lot! :)
TestComplete will execute your test steps as quickly as it can, according to the project settings. Sometimes it can get ahead of your app and be trying to click on something that isn't there yet. This can happen when you are first working on a test, or when you move a test to a different machine, or the network is slow, or...
There are various ways to fix this. Take a look at this as a start.
- vthomeschoolmom6 years agoSuper Contributor
Thanks. I am well versed in wait strategies. The issue is not that the wait for the object is inadequate, but that the click that preceeds is not firing the event that causes the desired object to be shown as evidenced by the attached log. No matter how long I wait before the second click, the object is not visible.
- vthomeschoolmom6 years agoSuper Contributor
Nevermind. The thing that is being clicked on is not he desired object. I have more research to do. Thanks
- RUDOLF_BOTHMA6 years agoCommunity Hero
Just an observation. The click event before the error is clicking at an x,y coordinate, which may or may not have the button present at the time of the click. Would inserting a HoverMouse be appropriate here ?
Related Content
Recent Discussions
- 8 hours agoSvetaG