TestComplete doesn't recognize Mapped Names
Hi all. I've recorded scripts for all of our system screens. It took me four months to do everything on version 2011.2. Now, our developers have compiled the version 2011.3 of the system...
Forum Discussion
Let's start with the button in question.
Differences in versions many times have these things happening to the components. What this means is that, rather than having to redo everything, you need to evaluate what changed so you can make the necessary adjustments to your mapping. And by "adjustments", I don't mean just changing values but using some of the techniques of NameMapping such as wild-cards, "Extended Find" feature, Conditional Mode, and Required Children to do your mapping in ways that are more reliable in finding and identifying objects.
- Which properties did you use in your mapping criteria in TestComplete? (as some properties are better for mapping than others)
- Did any of those properties change in value?
- Did anything in the hierarchy to that button (other forms, panels, etc) change in their mapping?
- Did the hierarchy itself change (new panels or forms in between)?
Differences in versions many times have these things happening to the components. What this means is that, rather than having to redo everything, you need to evaluate what changed so you can make the necessary adjustments to your mapping. And by "adjustments", I don't mean just changing values but using some of the techniques of NameMapping such as wild-cards, "Extended Find" feature, Conditional Mode, and Required Children to do your mapping in ways that are more reliable in finding and identifying objects.