We are building a new experience for our SmartBear Community.
This site is now read-only. You can still browse and search as usual. Learn More
This site is now read-only. You can still browse and search as usual. Learn More
Here's an explanation and examples that may help you out.
https://support.smartbear.com/testcomplete/docs/testing-with/running/handling-errors/unexpected-windows.html
That's under this part in that same documentation. Try changing your timeout value.
Here's an explanation and examples that may help you out.
https://support.smartbear.com/testcomplete/docs/testing-with/running/handling-errors/unexpected-windows.html
Marsha,
that link did truly help me get quite a bit farther along. the only problem I have now is more of a performance issue. in the linked article it states
TestComplete only checks for unexpected windows when the test performs an action (Click, DblClick, Activate, etc.).
so the popup window can sometimes sit there for a long time before the handler is getting invoked to handle it. You can see that the popup was on my screen for more than a minute and a half before the event handler (which contains the Log.Message that put “Popup detected” message in the log attached image) kicked in and handled it. I need to figure out something that will force this to happen much sooner.
That's under this part in that same documentation. Try changing your timeout value.