Writing Auto tests against an application written in Visual Basic - remapping issues
I am working on a role to maintain automated scripts against an application written in Visual Basic 6. I received a deploy of a later version of the App (also written in VB6). I find I am doing a crazy amount of remappings as all the objects have changed (using TestComplete Keyword Scripting).
Where I can I wildcard and name map to see if that can improve performance against future deployments.
I believe that a release further down the line of this (client/server) application will be rewritten in VB .Net.
My question is will this improve mapping issues? Has anyone else experienced this?
In TestComplete, you can create aliases. That is the preferred way.
What I like to do is create an alias at 3 levels, 1st at the screen level (what ever window or dialog), then 2nd at the container level (what ever section or parent table is holding the target control), then finally one at the target control.
From there, you can remap those aliases to adjust to most major changes under the AUT.
So after you do your mapping, first map the window, assign it an alias, then map the container relative to the alias assign that an alias, then map the control relative to the container alias and assign that control an alias. Then when you reference controls in your tests, use the control's aliases instead of the direct mapping.
That cooler thing you can do from there, is you can create different mapping profiles in TC, that reassign those aliases. Which will allow you to keep your tests backwards compatible.