NisHera is correct in that, depending upon what you are using for your properties for mapping, they could be incompatible. Multiple configurations as indicated in the linked documentation is one solution. Another, more involved solution, is to work at using properties and such that work no matter what OS.
I have been playing around with this issue for the last several days, and I believe there are a number of problems that seem to be confusing me.
1. I am switching between OS on the same project. I am quite sure that the object hierarchies that are built are different enough that I need to look at multiple configurations as a solution.
2. The application I am testing builds itself at run time through plugins and other dynamically created objects. As a result, I believe this will cause different object hierarchies to be created between test runs. I suspect that this is possibly a bigger issue than the OS issue that resulted in me creating this blog entry in the first place.
3. The automatic building of the object hierarchy, especially QT objects, seems to turn itself on and off. When it is off, the entire name mapping capabilities becomes useless to me. I can force it to build a hierarchy by using the recorder, but otherwise I cannot tell what I am doing that turns it "off" and "on". I prefer to use the recorder only to map out my test scenario and then reconstruct it with more object-driven detail and less coordinate mapping.
I am developing a powerful love/hate relationship with TestComplete Desktop right now :-)
