Last post Jul 22, 2009 10:19 PM by farmas
Jul 21, 2009 12:28 PM|AikiBushi|LINK
any idea how to work around this?
Jul 22, 2009 02:24 PM|AikiBushi|LINK
I found the problem. Just an FYI if anyone else comes across this issue:
The app I am testing starts at a launchpage that automatically launches the webapp into a popup (to remove all toolbars, buttons and address bars) on the onload of the body tag. If I close this popup and use the framework to relaunch the app I can successfully
hook the popup. So it seems all popups have to be triggered by the test framework.
Jul 22, 2009 10:19 PM|farmas|LINK
Yes, LTAF needs to hook into the window.open of the test page, and this happens whenever a command is received by the driver frame. If you navigate to a page that automatically popups a new page, LTAF doesn't get a chance to capture it.
BTW, there is a known issue in the current version that if a test fails while automating a popup window, the DOM that is reported in the error page is from the main window instead. We are looking at addressing that in the next release.