This procedure describes how to create and edit a test object map that you can use to test an application. You create a test object map, refine it to more accurately describe the application, and share the map with other scripts you create to test the application.
(Optional) For Functional Tester, Java Scripting, create a new test object map. For Functional Tester, VB.NET Scripting, create a new test object map.
Note: When you record a script, Functional Tester creates a test object map (or perhaps uses an existing shared map) for the application-under-test. For information, for Functional Tester, Java Scripting, see Creating a New Test Object Map. For Functional Tester, VB.NET Scripting, see Creating a New Test Object Map.
Assign a name that identifies its purpose.
Include all objects that you want to test in the application.
Edit object properties. For example, you can convert a recognition property value to a regular expression, which allows for more flexibility in the object recognition.
For each object, describe its purpose to reflect what you would like to see in a script.
(Optional) Edit descriptions for commonly used test objects.
For Functional Tester, Java Scripting, record a script. For Functional Tester, VB.NET Scripting, record a script.
On the Select Script Assets page, in the Test Object Map field, click Browse to select the shared object map you created.
You now have a test object map that reflects the application it was designed to test. You can share this map with the scripts you create to test the application. If the test object map is used by many scripts and it becomes necessary to change it, changing recognition and administrative properties in the map allows the associated scripts to run with this improved application definition. When using private test object maps, the application properties must be updated on a per-script basis.
Related Topics:
Terms of use | Feedback
(C) Copyright IBM Corporation 2002, 2004. All Rights Reserved.