Forum Discussion
alinder
13 years agoContributor
Curt, if it is of any help to you, the automation framework I've been working with in TestComplete gives some rough comparisons.
We have assigned a NameMapping and short Alias to about everything in our application under test, but we have some constraints we implemented against that required adding specific abstractions between our tests, the AUT, and the automation tool.
Because of those constraints we adopted, when we need to retrieve an object, sometimes we have an exact representation of the mapped Alias a test needs (like "Foo" and "Bar" for "Aliases.Foo.Bar") and sometimes we only have part of the information (like the same "Foo" and "Bar" for "Aliases.Foo.Alpha.Beta.Tau.Bar").
FindChild using the MappedName property with a wildcard (the representation of the Alias on each object) will work for either case, but as mentioned before it takes 8-15 seconds to return an object. Using "WaitAliasChild" returns my objects within a second - fast enough that we always try that approach first and failover to FindChild if unsuccessful.
We have assigned a NameMapping and short Alias to about everything in our application under test, but we have some constraints we implemented against that required adding specific abstractions between our tests, the AUT, and the automation tool.
Because of those constraints we adopted, when we need to retrieve an object, sometimes we have an exact representation of the mapped Alias a test needs (like "Foo" and "Bar" for "Aliases.Foo.Bar") and sometimes we only have part of the information (like the same "Foo" and "Bar" for "Aliases.Foo.Alpha.Beta.Tau.Bar").
FindChild using the MappedName property with a wildcard (the representation of the Alias on each object) will work for either case, but as mentioned before it takes 8-15 seconds to return an object. Using "WaitAliasChild" returns my objects within a second - fast enough that we always try that approach first and failover to FindChild if unsuccessful.