Name mapping
Is there a way to create name mapping on the fly? The scenario that I am running into is I have a WPF application where there is a job queue, For each job there is a button that can say start o...
Forum Discussion
I see where I can use name mapping to try to do what I am talking about, but anytime I point to anything below the top level properties ie. DataContext.Name TestComplete can no longer find the object.
I have verified that I am entering the information exactly as shown in object spy but still cannot find it when putting that in the name mapping. I get errors saying the name mapping is ambiguous and all I did for a test was go to conditional mode of the object I left the default property there which is ambiguous but does not give any errors and clicked the and button then selected [Type property name] and entered DataContext.Name, I then selected Equals for the condition, and for the value I entered test1 which is the name of a job that I currently have in the queue. When I click ok I get error saying that the name mapping is ambiguous and if I say yes then the name mapping for the object is broken until I remove the second property.
So the first problem is how can adding an and to the conditional name mapping suddenly make it ambiguous? Especially since the default value that TestComplete picked is completely ambiguous, but does not give any errors indicating that.
The second problem is why is the name mapping not reading the property that I entered correctly? I entered one of the few things that Object Spy shows as unique but the name mapping part does not see it that way. Why is there a difference between the two? How do I fix it?
I have verified that I am entering the information exactly as shown in object spy but still cannot find it when putting that in the name mapping. I get errors saying the name mapping is ambiguous and all I did for a test was go to conditional mode of the object I left the default property there which is ambiguous but does not give any errors and clicked the and button then selected [Type property name] and entered DataContext.Name, I then selected Equals for the condition, and for the value I entered test1 which is the name of a job that I currently have in the queue. When I click ok I get error saying that the name mapping is ambiguous and if I say yes then the name mapping for the object is broken until I remove the second property.
So the first problem is how can adding an and to the conditional name mapping suddenly make it ambiguous? Especially since the default value that TestComplete picked is completely ambiguous, but does not give any errors indicating that.
The second problem is why is the name mapping not reading the property that I entered correctly? I entered one of the few things that Object Spy shows as unique but the name mapping part does not see it that way. Why is there a difference between the two? How do I fix it?
