Namemapping - Individual & Merged
New to TC, migrating over from QTP. I've run across a problem, that I hope you can help me with. Let's say that I have two seperate applications, each of them are tested on their own. Different Pro...
Forum Discussion
Not only different aliases, but the NameMapping tree is dependant on a hierarchal structure starting at the system root (Sys) object. Each app is a process off the Sys object so you would have
NameMapping.Sys.App1
NameMapping.Sys.App2
. So, MainMenu of App 1 will show as a child object of that app and MainMenu of App 2 will show as a child object of that app. Because the parent object is different, the child objects will be kept separate.
NameMapping.Sys.App1.MainMenu
NameMapping.Sys.App2.MainMenu
NameMapping.Sys.App1
NameMapping.Sys.App2
. So, MainMenu of App 1 will show as a child object of that app and MainMenu of App 2 will show as a child object of that app. Because the parent object is different, the child objects will be kept separate.
NameMapping.Sys.App1.MainMenu
NameMapping.Sys.App2.MainMenu
