Forum Discussion
11 years ago
I encountered a similar problem and I found it unresolvable:
My app is calling a FileOpen dialog from the OS (Windows7) and I want to specify a file name that isn't yet existing. Consequently the system prompts me saying the file doesn't exist and asking whether it should create it.
TC properly records the click on the Yes-Button, but when replaying the test, it will not find the object because both the FileOpen dialog and then Confirm dialog are identified by the respective window's caption, which in both cases is 'Open'. As a result, the Confirm dialog is virtually inaccessible by TC.
My pragmatic resolution was to make sure that the file to be specified does not yet exist, so I could safely expect the confirmation dialog to occur. Then I send a Sys.Keys('[Enter]') statement to click the default button (which is 'Yes').
Not really what I wanted, but it works for my test at last.
Seems your problem could be identical to this.
My app is calling a FileOpen dialog from the OS (Windows7) and I want to specify a file name that isn't yet existing. Consequently the system prompts me saying the file doesn't exist and asking whether it should create it.
TC properly records the click on the Yes-Button, but when replaying the test, it will not find the object because both the FileOpen dialog and then Confirm dialog are identified by the respective window's caption, which in both cases is 'Open'. As a result, the Confirm dialog is virtually inaccessible by TC.
My pragmatic resolution was to make sure that the file to be specified does not yet exist, so I could safely expect the confirmation dialog to occur. Then I send a Sys.Keys('[Enter]') statement to click the default button (which is 'Yes').
Not really what I wanted, but it works for my test at last.
Seems your problem could be identical to this.
Related Content
Recent Discussions
- 3 days agoMW_Didata