Forum Discussion

ThomasCasserly's avatar
ThomasCasserly
Frequent Contributor
4 years ago

Namemapping creating new browser specific root node, why??

Hi all, 

I'm recording some keyword tests and have an issues that has occurred. Up to this point, namemapping was placing all mapped items under a "browser" root node. But for my most recent test Testcomplete has created a new, browser specific node labelled "chrome".

 

This means all objects are now being detected as new and mapped under the "chrome" root, even though some have been previously mapped under the "browser" root node. Does anyone know why this new root node has been created??

 

My tested website address link is unchanged and current situation means a lot of extra namemapping work, moving items from one tree node to the other  for newly mapped items or pointing tests to the previously mapped item for ones that have already been mapped under the "browser" node

  • ThomasCasserly's avatar
    ThomasCasserly
    4 years ago

    This issue was occurring for me after a testcomplete crash for which I logged a separate case. Support team have come back saying that the crash issue will be resolved in the next release of TestComplete 14.72. So that may also resolve this Namemapping issue. I will update after the release is available.

     

  • AlexKaras's avatar
    AlexKaras
    Champion Level 3
    4 years ago

    Hi,

     

    Namemapping_OriginalRootNode_TestedSite.png attachment illustrates mapping for the Page but not for the Browser. So it is difficult to say anything...

     

    • ThomasCasserly's avatar
      ThomasCasserly
      Frequent Contributor
      4 years ago

      Hi Alex, 

       

      new screenshot added showing namemappings for the browser and chrome nodes

  • TanyaYatskovska's avatar
    TanyaYatskovska
    SmartBear Alumni (Retired)
    4 years ago

    Thanks for the help, AlexKaras!

     

    ThomasCasserly, I see that you are working with the Support team on this behaviour (case #00459238). Please let us know the solution.

    • ThomasCasserly's avatar
      ThomasCasserly
      Frequent Contributor
      4 years ago

      This issue was occurring for me after a testcomplete crash for which I logged a separate case. Support team have come back saying that the crash issue will be resolved in the next release of TestComplete 14.72. So that may also resolve this Namemapping issue. I will update after the release is available.