Forum Discussion
HKosova
13 years agoSmartBear Alumni (Retired)
Hi Oleg,
On second thought, if I understand you correctly, a possible solution is to create Name Mapping (object repository) for your tested application and use conditional name mapping in combination with Extended Find to map objects in different branches to the same object hierarchy.
For example, you can define a mapping condition for an object similar to this:
(
[ WPF identification condition ]
ClrClassName = 'TabHostView'
AND
Index = 2
)
OR
(
[ MSAA identification condition ]
ObjectType = 'PageTab'
AND
ObjectIdentifier = 'Configuration'
)
and then refer to this object as, say, Aliases.MyApp.MainForm.Foo.Bar.MyTargetObject, regardless of whether it's in the WPF or MSAA branch.
And it leads to very bad practices in scripts, when we have to search for objects belonging to the same visual pane, but in different trees. Merging them would be fantastic.
On second thought, if I understand you correctly, a possible solution is to create Name Mapping (object repository) for your tested application and use conditional name mapping in combination with Extended Find to map objects in different branches to the same object hierarchy.
For example, you can define a mapping condition for an object similar to this:
(
[ WPF identification condition ]
ClrClassName = 'TabHostView'
AND
Index = 2
)
OR
(
[ MSAA identification condition ]
ObjectType = 'PageTab'
AND
ObjectIdentifier = 'Configuration'
)
and then refer to this object as, say, Aliases.MyApp.MainForm.Foo.Bar.MyTargetObject, regardless of whether it's in the WPF or MSAA branch.
Related Content
- 11 years agoalexey_ostapov
- 6 years agoAdagio