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 Te...
  • 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

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

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

    Hi,

     

    Weird... Unless you have something set as a required child for initial Browser mapped item (Required Children pane next to the Properties one where mapping settings are specified) I would create Support ticket via the https://support.smartbear.com/message/?prod=TestComplete form.

     

    • ThomasCasserly's avatar
      ThomasCasserly
      Frequent Contributor
      4 years ago

      Hi Alex, thanks for the reply.

       

      I've no required children set for the initial browser mapped item. This has happened to me once before and then I just moved any mapped objects from the new browser node to the original one.

      I'll log a ticket and see what they come up with.

       

      Thanks for your help.