First thing I would do is spend a bit of time examining the object in TestComplete object browser to see if there are any properties where the data is static and combining two or more of them results in a unique ID. For example, I have a form where there are multiple objects that, for all intents and purposes, are EXACTLY the same... except the one I want is has "Visible" set to true. So, I added that into my property identification mix. While there are properties of some stuff that are dynamic, there are many times a combination of properties that will work.
IF, however, you cannot figure it out, identify the parts of the properties that are dynamic and use wildcards. For example, if you have a property that has something like "text1234" as a value where the numeric part changes from run to run, change the identifying property to "text*". As long as that uniquely identifies the field, wildcards work well.
Robert Martin
[Hall of Fame]Please consider giving a Kudo if I write good stuff
----
Why automate? I do automated testing because there's only so much a human being can do and remain healthy. Sleep is a requirement. So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.
Mysterious Gremlin Master
Vegas Thrill Rider
Extensions available
