Forum Discussion

adoublin's avatar
adoublin
New Contributor
9 years ago

Issues with NameMapping after updating the TestedApps

Good evening everyone,

 

I am having an issue with my NameMapping. Originally everything was fine until I created a new build of the project I was working on. After this, the naming of some of my objects was extremely long and not very descriptive. Originally I was going to change the aliases, but realized almost all of my objects were going to be needing new aliases. My issue was that I could see the old aliases and the correct 'default' naming that TestComplete gave them. 

 

Unfortunatly, I believe that I could just delete the old aliases and TestComplete would just re-map and rename the aliases to a correct value and everything would be great. Sadly I now realize that was not the case and none of my old scripts and keywordtests work. 

 

I was wondering if there was an easy way to remove all old namemappings and start fresh, with the default mapping being created again. Would the best option be to Create a new project from scratch?

 

Any suggestions are accepted. Thank you!

  • NisHera's avatar
    NisHera
    9 years ago

    As I understand you haven’t built a test framework so it would be wise to start from scratch. Just record and play is a good start. (me too started the same way ) But to build a solid test frame take time and there is a learning curve. Name mapping is a critical part of your frame. Try mapping with future proof properties. Always do manual mapping.

     

    You do not have to map everything, try to map major stable parent objects only. Then you can call child by the parent mapping.  

    Better to have name mapping as it is, but keep Aliases short and clear so that your scripts are not messy.

    Before start full swing of test automation better do small parts(project) to test-the-waters.

    Read documents as much as possible, there are lot of  information.

    good luck..!

  • sreedevtr's avatar
    sreedevtr
    Contributor
    9 years ago

    Did you created the automation script using record and Play back? It seems the namemapping you defined is not robust enough to identify the controls uniquely. It is not a good idea to do it again the same way with the new build of your project because this may fail again on taking another build. So what we need to do is to identify the property of the control that remains unchanged between the builds and use them to name map the control. It is always better to map the controls manually rather than relying on testcomplete to do it during a recording.Hope this helps.

  • NisHera's avatar
    NisHera
    Valued Contributor
    9 years ago

    As I understand you haven’t built a test framework so it would be wise to start from scratch. Just record and play is a good start. (me too started the same way ) But to build a solid test frame take time and there is a learning curve. Name mapping is a critical part of your frame. Try mapping with future proof properties. Always do manual mapping.

     

    You do not have to map everything, try to map major stable parent objects only. Then you can call child by the parent mapping.  

    Better to have name mapping as it is, but keep Aliases short and clear so that your scripts are not messy.

    Before start full swing of test automation better do small parts(project) to test-the-waters.

    Read documents as much as possible, there are lot of  information.

    good luck..!