|
Object Mapping
|
| WinRunner
|
Object mapping is available via the rapidtest wizard and also the virtual object wizard. This allows you to map non-standard objects or painted controls to standard objects as recognized by WinRunner. Rapidtest does not work when you have webtest facility enabled.
|
| QA Run
|
Has a good facility for object mapping. All identified objects use a hybrid of properties to uniquely identify themselves. These properties are: Type – whether it has derived title or not, Module, Class, Title, and Position. You can get QA Run to automatically create name for unidentified testing objects.
|
| Silk Test
|
You can map the custom win to the so-called meta classes i.e., BUTTON, STATIC, and MDI. You do this in the windows declarations dialog. It works as in other tools in that you map an object to a class you think it behaves like.
|
| Visual Test
|
Object mapping can be done via two ways. The first is from tools->Options->Recorder Tab. You can select the window/object you want to map. Then you select the object to map against e.g. pushbutton, etc.The other way to map object is when you are recording a scenario.
|
| Robot
|
Object mapping facilities can be accessed through the tools->general options menu. This allows you to include (map) a class against known classes. The classes to map include Java, HTML, PeopleSoft Tools and standard windows controls
|
| QA Wizard
|
You can map objects to pre-defined classes that the tools come with. This tool comes with most of the standard window controls and objects can be mapped against these classes. It was a little tough, at first, for us to find how to do that. The tool does not provide enough documentation as to how the object mapping works. We had to play around with it to get this done. Object mapping is quite weak in this tool.
|
