Forum Discussion
I did not mean that and did not aware about my cap lock
Will be careful next time
Using 11.31
Please post the contents of your checkpoint. Does this need to be a region or is it acceptable to compare text instead? That might be more accurate.
- varsha9 years agoOccasional Contributor
FoundDeviceView Click ... Clicks at point (96, 27) of the 'FoundDeviceView' object.
FoundDeviceView DblClick ... Double-clicks at point (34, 3) of the 'FoundDeviceView' object.
RadiobuttonAlwaysRespondTo ClickButton Clicks the 'RadiobuttonAlwaysRespondTo' radio button.
RadiobuttonAlwaysRespondTo2 ClickButton Clicks the 'RadiobuttonAlwaysRespondTo2' radio button.
ButtonOk ClickButton Clicks the 'ButtonOk' button.
Region Checkpoint SampleRegionCheckPoint Aliases.KuliteConfig.HwndSource_MainWindow.MainWindow.DockPanel.StatusBar.StatusbaritemFound1Device, ... Compares the SampleRegionCheckPoint Stores item with the image of the Aliases.KuliteConfig.HwndSource_MainWindow.MainWindow.DockPanel.StatusBar.StatusbaritemFound1Device object.- Marsha_R9 years agoModerator
I think you would have better luck checking for the text "Found 1 Device" in the object than you will in comparing regions. The text will exist no matter where the region ends up (which can change with screen size, etc.).
In the lines before that, you should also consider Click and DblClick using the object name rather than on a point. You may run into the same problem as with the regions and things will move a bit on the screen and with points your test will fail but objects should make it more flexible.
- Colin_McCrae9 years agoCommunity Hero
100% agree with Marsha.
That's a pretty horrible way you're doing it. It all looks very fragile, easy to break, and unlikely to work on any other machine.
Related Content
- 2 years ago
Recent Discussions
- 2 days ago
- 8 days ago
- 11 days ago