Object spy for the Window
Object spy for UserName (fill-in) widget
Obje
Hi,
As I can see, your GUI elements are perfectly recognized and you can start interact with them.
E.g. if you want to type "Name" into the UserName textbox, just try:
Set textbox = Aliases.prowin.wndProMainWin.ProClientWin.ProFrame.Edit textbox.Keys "Name"
etc...
Ok sounds good. So I take the things in simple way -
1. Do Recording
2. Look object names in Name Mapping or Object Spy
3. Give Meaningful Names in Name Mapping
4. Create Aliases in Script with the meaningful name
Now My script would be more familiar to us if I follow above.
If something I am missing Please guide me.
Hi,
> Now My script would be more familiar to us if I follow above.
From the long-term perspective the better sequence is:
1. Analyze your application in the Object Browser / Object Spy and identify the UI objects that you will need to use in the test;
2. Consider how the required UI objects can be mapped reliably (What properties to use; wildcards / regexp for the property values; what parent objects are required for reliable identification of their children; whether or not to use Extended Find and Conditional namemapping);
3. NameMap required UI objects;
4. If needed, clean and reorder the Aliases tree in namemapping to get objects hierarchy that is more convenient to your needs;
5. Do Recording.
If steps 1-4 are done correctly, you should get much cleaner recording that should require much less manual adjustments.
Thanks a lot. I will keep in mind.
