Ranorex v7.2
AUT: WPF
Application pops a Message Box in different places in the UI. All from the same call "MessageBox.Show(stuffings)".
I've mapped the MessageBox completely and can address/id the xpaths most of the time.
HOWEVER,
In certain places of the UI, Ranorex gets blocked/locked out and can't id the MessageBox at all.
The only way Ranorex can negotiate the MessageBox is to send a Key Sequence e.g. {Return} But timing is everything.
Attempts to id these instances of the MessageBox with the SPY cause it (the SPY) to crash.
Any help would be appreciated.
Thanks!
WPF App Message Box Causes SPY to Crash
- RobinHood42
- Posts: 324
- Joined: Fri Jan 09, 2015 3:24 pm
Re: WPF App Message Box Causes SPY to Crash
Hi Hondo,
Do you know when the MessageBox will pop-up during your test run?
If yes, isn't the key sequence action a viable solution?
If no, how to you handle the Message Box? Are you using a pop up watcher? Which rx path to you use to recognize the window?
A Ranorex snapshot of the MessageBox would also be helpful: snaphot file
Cheers,
Robin
Do you know when the MessageBox will pop-up during your test run?
If yes, isn't the key sequence action a viable solution?
If no, how to you handle the Message Box? Are you using a pop up watcher? Which rx path to you use to recognize the window?
A Ranorex snapshot of the MessageBox would also be helpful: snaphot file
Cheers,
Robin