Forum Discussion
Uwe_Raabe
14 years agoOccasional Contributor
During the recording on Windows XP there was a situation where a message dialog popped up requesting a Yes/No/Cancel decision,which was answered with a click at the No-button. The caption of the dialog is "Bestätigen", which is "Confirm" in German (mind the umlaut).
The corresponding keyword test created by importing the recorded data expects a window named "wndBest_tigen" (the umlaut is mapped to an underscore).
When I run that keyword test on Windows XP everything works fine, but when I run it on Windows 7 TestComplete waits for the message dialog until it times out. Of course the same exe is used for recording and playback.
I converted the keyword test to a script and the offending line is:
Aliases.twincam.wndBest_tigen.btnNein.ClickButton;
(TwinCAM is the application name and "Nein" is German for "No")
The corresponding keyword test created by importing the recorded data expects a window named "wndBest_tigen" (the umlaut is mapped to an underscore).
When I run that keyword test on Windows XP everything works fine, but when I run it on Windows 7 TestComplete waits for the message dialog until it times out. Of course the same exe is used for recording and playback.
I converted the keyword test to a script and the offending line is:
Aliases.twincam.wndBest_tigen.btnNein.ClickButton;
(TwinCAM is the application name and "Nein" is German for "No")
Related Content
Recent Discussions
- 3 days agovladd1