| || |
New Applications for Automation
Does anyone have any ideas on what should be checked to determine if an application is suitable for automation with TestPartner. I would like to put together some things that should be checked before Automation is suitable. For example, can you grab text from the screen, are controls learnt clearly etc. Any help would be appreciated.
Re: New Applications for Automation
Run Identify against the application. If controls are seen "for what they truly are", this is your first major step. VBEditBox, SAPButton, HTMLListBox, JavaComboBox, TreeView, are all good examples. If TP is seeing many things as GUIOBJECT, this means TP does not understand the objects. When this is the case you can try Alias Mapping, but it is hit-or-miss. Note that 3rd party .net controls will be seen as GUIObject, but can be automated via the .OBJECT for .NET feature.
A second check is understanding if TP understands Text in the application. A quick way to understand this is looking at what is captured into a text check.
After that a few Record-Play scinarios should be run to confirm that TP understands the app at both learn and replay correctly.