We handle this by using the title of the page in the NameMapping entry. You could also handle this by using the URL (assuming the individual browsers are on different pages).
If the same page is loaded in each of the three browsers and no unique identifiers can be used for the same page (like showing the logged in username in the title), you can fall back to using the Index of the parent (the browser itself).
bo_roop,
My test case is that all 3 users or browser instances are loading the same page.
Like I mentioned earlier, TestComplete 12 has an issue of not providing different indexes to different Chrome instances, while it does to IE browsers.
Bummer. I know we've run into some issues that are stopping us from updating to v12. Hopefully 12.10 is coming soon and it will fix all the problems that were introduced.
In the meantime, could you get around this by grabbing the Window's handle of the new tab when it's opened and then place it into a variable? You could then use that variable as a required property of the NameMapping entry. You should be able to get away with this logic as long as you are able to grab the correct handle from the newly launched tab.
Another thought would be to open the tabs as separate windows and drive them to a specific location and then use the ScreenTop or ScreenLeft values to differentiate between the windows.
Both are less than optimal options, but when left with nothing better...
