Objects being reused and renamed causing tests to break

Hi Robert,

Thanks for your advice.

I have been able to work around this by using Extended Find on the object itself or a parent object. Though, I don't really like to use this as I understand it adds time to test runs and is already used a fair amount in the project.

I have looked at the ObjectIdentifier property of some of the objects already stored and most have nothing populated. I've also checked with a developer and they confirmed they don't follow any guidance at all concerning objects and\or coding for testing using TestComplete. This has prompted discussion internally :)

It seems like a good suggestion to always have a static identifier on every object. That way the desired Object is always the one that TestComplete is looking for and it's less "hit and miss" as to which one it is actually looking for. The trick will be encouraging others to understand the importance of this from our perspective and following that guideline. *added to the list! ;)

I'm glad you mentioned web testing as I am also having issues with identifying objects in those tests aswell! And your advice will no doubt help there aswell. Thank you!

This might sound a silly question but I'll ask it anyway! - Is there any way I can create a unique Object Identifier on an object? I've noticed some of the Identification Properties can be edited - I might be wrong - and I just wondered if they could be used in that way. I understand this might be waaaayyy to simplistic but thought it worth asking just in case.

Thanks for all your help!