neha_sharma
11 years agoContributor
Unexpected window handling
Hi,
I am trying to handle unexpectwed windows in my application.
I am getting an error "ADODB.Connection Provider not found".
So i am looking for TestComplete to close this window and procceed with the execution of next ProjectTestItem.
Here are the steps i have tried:
1.Added event onUnexpectedWindow and the code is:
Sub GeneralEvents_OnUnexpectedWindow(Sender, Window, LogParams)
'@@ Close the unexpected window
Call Window.Close
End Sub
2.Stop on error is unchecked in Default project properties.
3.I have added Stop on error and Stop on Exception ,set them as None in ProjectTest items.
4. The autowait timeout is 50ms in Default project Properties --> Playback.
Then also i am not able to close the Error window in automation and proceed to run next Test item.I have to do it manually.I have attached a screenshot of the window i want to close.
After this window i need to handle the window that ask to continue with next Project test item or stop execution.
Thanks,
Neha
I am trying to handle unexpectwed windows in my application.
I am getting an error "ADODB.Connection Provider not found".
So i am looking for TestComplete to close this window and procceed with the execution of next ProjectTestItem.
Here are the steps i have tried:
1.Added event onUnexpectedWindow and the code is:
Sub GeneralEvents_OnUnexpectedWindow(Sender, Window, LogParams)
'@@ Close the unexpected window
Call Window.Close
End Sub
2.Stop on error is unchecked in Default project properties.
3.I have added Stop on error and Stop on Exception ,set them as None in ProjectTest items.
4. The autowait timeout is 50ms in Default project Properties --> Playback.
Then also i am not able to close the Error window in automation and proceed to run next Test item.I have to do it manually.I have attached a screenshot of the window i want to close.
After this window i need to handle the window that ask to continue with next Project test item or stop execution.
Thanks,
Neha
- Also check out this thread here for more information on the original error you were getting.