Forum Discussion
vthomeschoolmom
13 years agoSuper Contributor
Martin mentions manual comparison of screen shots. This is one option. Depending on your application under test and how open it is, you can also do your won coded checkpoints. What I am usually checking for is to ensure that the data that I am expecting is present on the screen or my output file contains the data that I expect for instance. (My advice will be of no use to you if your application deals in images!) I will use Test Complete built in checkpoints where I can; property, object, file checkpoints. Where I can't I will use the native properties of the object to examine the data and Log.Checkpoint to the log the results. (Or Log.Error if it fails.)
For instance, we use grids that are not supported by test complete. So I cannot use built in table compares. So I will write code to examine the raw values.
Please note that Log.Checkpoint is not available in test Complete version 7.whatever I used to use.
Good luck.
For instance, we use grids that are not supported by test complete. So I cannot use built in table compares. So I will write code to examine the raw values.
Please note that Log.Checkpoint is not available in test Complete version 7.whatever I used to use.
Good luck.
Related Content
- 9 years agodmacknight
Recent Discussions
Check PopupMenu exists
Solved21 hours agomfoster711- 2 days agosimonaferrara
- 2 days agomacheshmeh