| || |
VB Control Hierarchy
I'm new to using SilkTest and VB. The app I'm testing is a VB app and I have noticed that controls are nested in a hierarchy which makes the identifiers in test cases quite long. I have "flattened" the hierarchy by defining each control in a window definition file with fully qualified tags.
Is this a good idea? I am concerned about going down a rat role and getting bitten later on. "Flattening" all of the controls is a lot of work. Perhaps there is a better way to approach this?
Re: VB Control Hierarchy
You could consider using the parent clause in the declarations. That will help you do what you need w/o having to put complete tags.