Forum Discussion
I just recorded the following using TC12, the latest version of Chrome, and the TestComplete forum page.
function Test1() { var browser; var page; Browsers.Item(btChrome).Navigate("https://community.smartbear.com/t5/TestComplete/ct-p/TestComplete_forum"); browser = Aliases.browser; page = browser.pageCommunitySmartbearComT5Testc; page.panel.footer.link.Click(); browser.pageSmartbearComProductTestexecu.Wait(); }
With this recording, when I playback, everything works fine... I don't even need to do a "ScrollIntoView"...TC automatically handles that.
So... what's different between what you're doing and what I'm doing?
I even made the following change,
function Test1() { var browser; var page; var link; Browsers.Item(btChrome).Navigate("https://community.smartbear.com/t5/TestComplete/ct-p/TestComplete_forum"); browser = Aliases.browser; page = browser.pageCommunitySmartbearComT5Testc; link = page.FindChild(['ObjectType', 'href'], ['Link', 'https://smartbear.com/product/testexecute/overview/'], 2000); link.Click(); browser.pageSmartbearComProductTestexecu.Wait(); }
Where, instead of just clicking, I find the object I want and then click it.
So... something still is different.
What type of object is it? What type of control? I see it saying "Button" as an object type but what sort of behind the scenes language and structure is being implemented to build those buttons? It could be that something is implemented differently in your application under test than what I'm experiencing.
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...