Forum Discussion

joffre's avatar
joffre
Regular Contributor
14 years ago

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, and the CRUD tests were supposed to be done with my TestComplete scripts. The problem is that TestComplete isn't recognizing ANYTHING.



So, I tried that "Display Object Properties Window" tool to see if the objects were correctly mapped, and for my surprise, it wasn't. So, I tried to map the button's name. For my surprise, it is already mapped. And since TestComplete doesn't let me override a MappedName, I'm lost.



I just can't do everything all over again. How will I fix it?

6 Replies

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    Let's start with the button in question.  


    1. Which properties did you use in your mapping criteria in TestComplete? (as some properties are better for mapping than others)

    2. Did any of those properties change in value?

    3. Did anything in the hierarchy to that button (other forms, panels, etc) change in their mapping?

    4. 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.
  • joffre's avatar
    joffre
    Regular Contributor
    The funny story is that the first window of my automation script doesn't change since version 2010.3!!!



    The window is the same. I tried to re-map the object name, and it is everything the same.
  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    so, it comes down, still, to those questions I asked.  The window may not have changed, but perhaps some other things around it did.  NameMapping can offset all those dynamic factors when going from one version to another, but you need to spend the time investigating and then making modifications so as to prevent those problems moving forward.



    I'm assuming there's an error message in your test log when it fails?  Something on the lines of "object not found"?  There should be information in the "Additional Information" panel of that test log.  Could you post the contents of that here?
  • Hi Joffre,


    To help us investigate the problem, could you please send us the test project and the old and new versions of the application under test?

  • Good afternoon,


    I am having the same problem.

    was automated  the entire project in the version 2011.1 and after installing the version 2012.1 nothing works.

    checked in the "object properties" and namemapping is empty, but the "aliasses.drag mapped objects" here mapped as shown the prints.


    How will I fix it?

  • Hi,


    It looks like the object hierarchy in your application has changed. As far as I can see from the third screenshot you've posted (ObjectProperties.jpg), currently, the object you are inspecting is not mapped. That is why, the MappedName property is empty.


    To fix the problem, you need to check what identification properties and property values are used for mapping objects. Then, correct name mapping if the stored and actual values of identification properties differ.


    I hope this helps.

    Ann