Forum Discussion

tatianacarvalho's avatar
tatianacarvalho
14 years ago

TestComplete 6.53 x TestComplete 8.20 (NameMapping)

I have a lot of scripts that I run successfully with TestComplete 6.53. 


Some of these scripts were converted automatically by the TestComplete 8.20, but when we try to run them, some errors from TestComplete 8.20 are presented.


I work with NameMapping.


I am using the same NameMapping used in the version 6.53.


In the Object Browser some objects are displayed in different ways.


In the attached evidence we can see two examples:


1 - The Object "Item(376)" has the same Name in both versions.

2 - The Object "el_cp_idNovaDataAtual2Table_dateField" has the Name "Item("el_cp_idNovaDataAtual2Table_dateField")" in version 8.20 and another Name "el_cp_idNovaDataAtual2Table_dateField" in the version 6.53.


How do I set the NameMapping to not recognize automatically the field name with "Item.." before the full name?



I've already enabled the "Use short names when possible" option described in the "Engines - General Options" but the problem still persists.



Tatiana Carvalho


 

1 Reply

  • AlexeyKolosov's avatar
    AlexeyKolosov
    Icon for Staff rankStaff
    14 years ago
    Hi Tatiana,



    You've already submitted a support case regarding this problem, so let's continue working on it in that support case.



    Here is a copy of our latest reply from that support case just in case:





    TestComplete scripts are not supposed to fail due to the naming difference: both "abc" and "Item("abc")" are supposed to work when you address an object via its full name. This, however, will not work if you use the Name property for objects identification in the FindChild method or in your Name Mapping scheme. If this is the case, you will have to change your scripts and/or Name Mapping scheme.



    If the object cannot be found when addressed via its full name, I recommend that you try following the suggestions provided in the Handling the 'Object Does Not Exist' Error help topic - it's possible that some recognition criteria need to be fixed. If this suggestion does not help, please zip your entire project suite folder along with the log of the failed test execution and send me the archive. Make sure that messages in your log correspond to the latest version of your tests.