Unexpected Window event is fired only once.
I am testing WPF application. And i have configured a UnexpectedWindow event via Events--> EventControl. The Event is fired only for the first time an unexpected window appears. For the subsequent ...
Forum Discussion
rraghvani
Champion Level 3
Champion Level 3The unexpected dialog that appears, is it an assertion or an error dialog coming from the actual application? Does it always appear after performing specific actions?
It is an error dialog coming from the actual application. It appears only when certain conditions fail. The event was not fired all the time during the error(condition failure) case.
- rraghvani
Based on past experience, if the application throws an unexpected error message, I won’t automate it. This is mainly because the next steps may not produce the expected results due to the previous error. However, if the error message consistently appears after performing certain actions, then I can easily handle it without using event handlers.
Regardless of the project settings, the event handler should be triggered, provided it meets the requirements. More information can be found in Handling Unexpected Windows.
Thanks for sharing the experience. let me check if that is the case here.