Forum Discussion
Here's an interesting thought... I took a quick browser through the "related topics" on the right side of the screen here for your post (lots of folks have run into similar situations). In some of the cases, the scroll didn't happen if the object itself was not actually visible yet... or the object was not enabled... or things like that.
So, you're telling TestComplete to go click on your button. Obviously, you've found the button... but is it enabled? Is it actually ready to be clicked at the moment that TC attempts to click it? Could it be that it's waiting for some other process or script on the page to complete before you can click on the button?
Just some things that my cold-medicine addled brain is processing today...
One other follow up:
One of those other threads presented an interesting problem with a dialog... that each time the dialog was created on the page, it was kept on the page but disabled... so, every time through the test, there would be a new, disabled copy of the dialog on the page. TestComplete couldn't interact with it because it wasn't on screen or visible... and yet, the human eye inspection said, "But I am looking right at it..."
So... investigate, also, how the buttons are instantiated... it COULD be that you may be finding the button but finding the wrong COPY of the button and, therefore, cannot always click on it.
Related Content
- 11 years ago
Recent Discussions
- 13 hours ago
- 2 days ago