Hi,In my .Net Test Application, sometime I get error with our Messagebox. On this Case I have to run a procedure. Sometimes TC gets this messagbox as unexpected window and sometimes ignore it as unexpected window. I have read the log, the messagebox is not registered as Error or unexpected window. How can I solve this Problem, I want to get always this Messagebox as unexpected window.

MadGrb Since none of the suggested solutions worked, this issue definitely requires deeper investigation. Please contact our Support Team and describe it as minutely as possible. Our Support Team and Dev Team would need to reproduce it in their lab, so please send them a sample app and a sample TC project for this. Please post the solution you get from them here, thank you🙂

Hi, OnUnexpectedWindow event is triggered in TestComplete when some modal window (application or system) prevents your test code to interact with UI elements out of this modal window. Examples of such interactions are clicks, setting focus and sending keys sequences. Exactly like it looks like for the human user. Note, that if your test code does not interact with UI but operates on tested application's methods/properties, then modal window will not block such interactions and thus the OnUnexpectedWindow event will not be triggered. For example, <inputField>.SetText('blah') will always succeed as it uses direct property assignment and does not interact with the <inputField> element via GUI. On the contrary, <inputField>.Keys('blah') will trigger the OnUnexpectedWindow event if the form with the field is blocked by some other modal message window. The good approach to get a reliable test code in the cases like this is to use .Activate for forms/windows and .Focus methods for controls before interaction with them to ensure that forms/controls are not blocked. E.g.: <form>.Activate; <form>.<inputField>.Keys('blah'); <form>.<inputField2>.Keys('blah') ...

It happens to me sometimes also. I consider this is just a weakness of TC and try to always have a second level of detection (active detection instead of event). TC install hook on Windows message queue but we cannot be guaranteed that whenever it peek message on it, it successfully grab all. OS and software environment are becoming so complex so i don't blame TC for it.

Event means that you let system warn you when the event occurs. Active detection is you specifically search for the element. Your problem is: could you determine conditions or places/times when the message box appears ? - If yes then you could use one of the WaitNNN methods to wait for the message box. https://support.smartbear.com/testcomplete/docs/app-objects/common-tasks/waiting-process-or-window-activation.html - If no then you must rely on Event... Houston we've got a problem... If you are good enough in development, perhaps create your own Event listener to catch on your apps only the message box. Something like this: https://docs.microsoft.com/en-us/windows/win32/winauto/uiauto-howto-implement-event-handlers

Are you sure you have to use this inside the event function? Objects_WAWi.BugAuftreten_Form.Exists If you are looking for a particular window, use it inside the main unit function. As a parameter, you have a window object. And this is what you are currently looking for. There is no need to look for something specified in the function, which is used to manage unexpected events. Read also tristaanogre solution about .exist: https://community.smartbear.com/t5/TestComplete-Desktop-Testing/Validate-if-object-does-not-exist/m-p/196757#M16257

Hi, One more thing: MadGrb wrote:def EventSendToBugReport(Sender = None, Window= None, LogParams= None): [...] try: while Objects_WAWi.SendError_Progressbar.WaitProperty("Visible", True, mBase.cBase.GetTimes('SmallTime')): Delay(mBase.cBase.GetTimes('SmallTime')) except Exception as exp: Log.Message('Oh lalala, I crashed') finally: [...] I see very little reason to use try/catch here. The case is that try/catch are the means of the programming language to handle runtime exceptions. Those like division by zero or thrown by purpose programmatically. In your case, <object>.WaitProperty() statement is absolutely safe and cannot trigger runtime exception. Yes, logical failure will occur if, for example, you try to wait for some non-existent property. But this will not be a runtime exception and thus it will not be handled by the catch clause. It will be a logical TestComplete'e error that will trigger the OnLogError event and can be handled there.

OnUnexpectedWindow event sometimes not working for windows Appliction

13 Replies

AlexKaras
Champion Level 3
4 years ago
Hi,

OnUnexpectedWindow event is triggered in TestComplete when some modal window (application or system) prevents your test code to interact with UI elements out of this modal window. Examples of such interactions are clicks, setting focus and sending keys sequences. Exactly like it looks like for the human user.

Note, that if your test code does not interact with UI but operates on tested application's methods/properties, then modal window will not block such interactions and thus the OnUnexpectedWindow event will not be triggered.

For example, <inputField>.SetText('blah') will always succeed as it uses direct property assignment and does not interact with the <inputField> element via GUI. On the contrary, <inputField>.Keys('blah') will trigger the OnUnexpectedWindow event if the form with the field is blocked by some other modal message window.

The good approach to get a reliable test code in the cases like this is to use .Activate for forms/windows and .Focus methods for controls before interaction with them to ensure that forms/controls are not blocked.

E.g.:

<form>.Activate;

<form>.<inputField>.Keys('blah');

<form>.<inputField2>.Keys('blah')

...

Wamboo

Community Hero

4 years ago

Can You show us some code?

MadGrb

Contributor

4 years ago

Yes,

def EventSendToBugReport(Sender = None, Window= None, LogParams= None):
        if Objects_WAWi.BugAuftreten_Form.Exists:
                Objects_WAWi.BugAuftreten_btnSend.Click()
            
                if Tools.WaitForAvailablity(Objects_WAWi.BugZusatzinformationSenden):
            
                        Objects_WAWi.BugZusatzinformationSenden_AchtungSign.Click()
                        Objects_WAWi.BugZusatzinformationSenden_btnZusatzinformationenSenden.Click()

                        Tools.WaitForAvailablity(Objects_WAWi.AdditionalInformation_Form)
                        Objects_WAWi.AdditionalInformation_Txt.Keys("TestComplate Meldung!! Für mehr info rufe Mo an. Fehler Codes is unkown!")
                        Objects_WAWi.AdditionalInformation_btnOK.ClickButton()

                        Tools.WaitForAvailablity(Objects_WAWi.SendError_Progressbar)
                        
                        try:
                                while Objects_WAWi.SendError_Progressbar.WaitProperty("Visible", True, mBase.cBase.GetTimes('SmallTime')):     
                                        Delay(mBase.cBase.GetTimes('SmallTime')) 
                        except Exception as exp:
                                Log.Message('Oh lalala, I crashed')

                        finally:
                                Tools.MessagboxManager()
                                         
                                Tools.MessagboxManager()
                        
                                Objects_WAWi.BugAuftreten_btnOK.ClickButton()
                                
                                mBase.cBase.TestResult('AQC of WAWi says: I crashed. BugInfo discoverd.',TypeOfResultObject = 'Bug')
                                
                                if Objects_WAWi.Absturz_btnSchlie_en.Exists:
                                        Objects_WAWi.Absturz_btnSchlie_en.ClickButton()
                                        Log.Message('WAWi Absturz')
                                        mBase.cBase.TestResult('AQC of WAWi says: Ich absturz. WAWi wird neuegestarten.',TypeOfResultObject = 'Bug')
                                Delay(mBase.cBase.GetTimes('SmallTime'))

BenoitB
Community Hero
4 years ago
It happens to me sometimes also.

I consider this is just a weakness of TC and try to always have a second level of detection (active detection instead of event).

TC install hook on Windows message queue but we cannot be guaranteed that whenever it peek message on it, it successfully grab all.

OS and software environment are becoming so complex so i don't blame TC for it.

Forum Discussion

OnUnexpectedWindow event sometimes not working for windows Appliction

13 Replies

Related Content

Object sometimes doesn't support Exists

Object sometimes doesn't support Exists

Why the Wait method sometimes works sometimes not?

Sometimes "Missing operation for soapAction"

TypeError: Cannot read property 'push' of null .. well, sometimes

Recent Discussions

Keyword Test - Click - use -1, -1 by default?

How to import external node modules in TestComplete

convert absolute path to relative path

Multiple execution of a test plan with different values from an Excel table

Searching for mapped object took too much time msg