Cloned name mapping object properties references project variable from original project
Ok, having a bit of an issue here...
I have a shared name mapping project item across all my TC projects. Some of the name mapping object properties are mapped using a project variable called NameMappingStr. I have the same project variable setup in all my projects. During test execution I set the NameMappingStr value (followed by a call to refresh mapping info) which allows me to dynamically set object identification properties and interact with dynamic content on a web page. Here's the problem, it appears the name mapping object property in Project B is looking at the NameMappingStr value from project A. So when I set NameMappingStr in project B the value is ignored. I believe this is because the name mapping project item for Project B was cloned from Project A and is holding a reference to the NameMappingStr variable in project A.
I can't seem to find a way round this at the moment. Ideally I would like to have the NameMappingStr variable set at project suite level rather than project level but I don't think name mapping object properties can reference project suite variables.
Has anyone else come across this and devised a work around for this. Happy to explain further if required....
Cheers,
Chris.