Robert Martin [Hall of Fame] Please consider giving a Kudo if I write good stuff ----
Why automate? I do automated testing because there's only so much a human being can do and remain healthy. Sleep is a requirement. So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group. I love good food, good books, good friends, and good fun.
Try/Catch keyword operations, likewise the same operators of programming/scripting languages, handle execution runtime exceptions like division by zero, stack overflow, etc. Extra window displayed on the screen is not an exception and thus it is not handled by try/catch.
Extra windows in TestComplete can be handled using one of two ways:
a) Do explicit check if an extra window is displayed on the screen using .WaitWindow()/.WaitAliasChild() methods. If the window is found, handle it appropriately;
b) If an extra window is modal one (i.e. it prevents access to all other UI elements of the tested application until the window is closed -- this is your case, according to test log), then you may create a handler of the OnUnexpectedWindow event and handle displayed window within this handler.
Regards, /Alex [Community Hero] ____ [Community Heroes] are not employed by SmartBear Software but are just volunteers who have some experience with the tools by SmartBear Software and a desire to help others. Posts made by [Community Heroes] may differ from the official policies of SmartBear Software and should be treated as the own private opinion of their authors and under no circumstances as an official answer from SmartBear Software. The [Community Hero] signature is used with permission by SmartBear Software. https://community.smartbear.com/t5/custom/page/page-id/hall-of-fame ================================