william_roe wrote:
Good feedback - thank you. Do you know if by not naming the alias is used?
I'm not sure I understand what you're asking. When you map an object, it automatically gets an alias and mapped object. We use the aliases to make writing the tests easier. I script all my tests by hand, but there have been a few times I've recorded a test to see how TC handles getting to a certain control (say, a non-standard drop-down list item). In those cases, the mapped object names were honored in the recorded test.
In case I just missed your question, here's another stab at it: I might have a login screen that has a bunch of design, but I really only care about the 2 textboxes and submit button. Usually TC will require some parent objects that I really don't care about (like DIVs, for instance). In that case, I'll map them, but get rid of their aliases. So while the Mapped Object might look like "NameMapping.page.div1.div2.frmLogin.txtUsername", the alias can be the more logical "aliases.page.frmLogin.txtUsername".
Sometimes I've found it safe to turn on Extended Find and delete those parent objects to clean up Mapped Objects, but I've found other times where doing so makes it so TC can't find the object I really want.
Hope this helps.