1. For dialog handling to function properly, you often must set the SimulateRealClick
property to True for the 'Click' step that triggers the dialog.
Another option is to manually set the UnexpectedDialogAction behavior with code like this:
Settings.Current.UnexpectedDialogAction = UnexpectedDialogAction.HandleAndContinue;
Just put this code in a Coded step and place it before the step where you expect the dialog to appear.
Now, you can change it again for the step where you want to handle the dialog by putting another Coded step with the following code:
Settings.Current.UnexpectedDialogAction = UnexpectedDialogAction.DoNotHandle;
Note that setting the UnxpectedDialogAction in this way will also work even if you run your test from Quick Execution.
2. If the actual Frame could not be found you would receive a different error. See here
for more information.
I believe the Find Logic on the element itself is too specific:
- id 'Exact' ctl00_m_g_32993630_d000_446f_aae0_0651008dc19b_ctl00_ctl02_ctl00_toolBarTbl_RightRptControls_ctl00_ctl00_diidIOSaveItem
I suspect that ID is dynamic. If so, change 'Exact' to 'Contains' and edit the ID so it only contains the static portion.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items