Hi Marsha,
I don't believe that's what I mean. I mean specifically about this line in the RefreshMappingInfo article:
"TestComplete caches mapped objects to speed up test runs. The first time a test uses an alias, TestComplete remembers the found object and uses the cached object for all subsequent uses of the alias."
The article Tanya pointed out to me talks about objects and properties in the code editor. I'm talking about cached objects during playback. After a test uses an alias once in a test, it caches the object (and its property values) found in the object browser and tries to use the cached object with subsequent calls to that alias.
I am wondering if there is a way to disable this feature so that TC will always look for the matched object in the object browser, instead of using the cached one, as it is possible the object properties will have changed.
If I am completely misunderstanding something please feel free to correct me. And if RefreshMappingInfo is the only way to get around this, then please let me know also.
Thanks.