Forum Discussion
- tristaanogreEsteemed Contributor
What that means is that, for some reason, your test is acting against an object on screen that has a zero height and width. Most likely, this is a timing issue. I'm guessing your test goes something like this.
1) Click a button or link that brings up some other modal or causes some component to become visible
2) Click on a button or link within that subsequent component.
However, between 1 and 2, there's a timing delay... some sort of processing, page load, etc., occurs so that the modal or component is not IMMEDIATELY available. One thing to keep in mind, especially when recording, is that as you are recording you're taking into consideration visual queues that you, as a human, know signal when something can be acted against. TestComplete is "dumb" in that respect in that, unless you explicitly tell it not to, it will attempt to run as quickly as possible. This means it may attempt to act on an object that is not ready to be acted upon.
This is where you need to do detection code in your keyword test to make sure that components are ready to be acted on before you do so.
Related Content
- 8 years ago
Recent Discussions
- 3 hours ago
- 2 days ago