Work with functional test object maps
This section describes how you can use test object maps to facilitate your functional testing effort. The test object map is a static view that describes the known test objects in the application-under-test.
Before you begin
What to do next
- Test object maps
The Functional Tester test object map lists the test objects in the application-under-test. It is a static view that describes test objects known to Functional Tester in the application-under-test.
- Create and using a test object map to test applications
You create a test object map, refine it to more accurately to describe the application, and share the map with other scripts you create to test the application.
- Create a new test object map
You can create a customized, shared test object map that you can associate with scripts.
- Merging multiple test object maps
You use the Merge Test Objects into the Test Object Map page to merge multiple private or shared test object maps into a single map.
- Add objects to a test object map
When you add an object to a test object map, you can choose to add just the selected object, include the children of the immediate parent, or include all the visible controls in the current window.
- Insert dynamic test object
You can also insert dynamic test objects by using Insert Dynamic Test Object. The hierarchy of a test object in the object map represents the order of search of the particular control during playback. Over a series of application changes, the hierarchy of the objects may change if new objects are introduced in the test application. This results in a playback failure. Using dynamic test objects you can anchor a test object as a descendant to its parent.
- Converting dynamic test object
You can covert an existing mapped object to a dynamic test objects. By converting existing test objects to dynamic test objects you can anchor a test object as a descendant to its parent. This ensures that the playback does not fail even if the hierarchy of a test object in the object map changes.
- Use ClearCase with test object maps
You can use ClearCase® with shared test object maps and to merge scripts across branches.
- New test objects in an object map
After recording, Functional Tester may automatically display the test object map. This occurs by default if new test objects were added to an existing map. You can turn this on or off in the Recorder page by selecting or clearing the Bring up object map if there is new test object box.
- Add a test object to an object map and a script
Functional Tester enables you to add a test object to an object map and a script at the same time.
- Editing object properties
You can edit information in the property sets in the lower (or right) pane of the test object map window.
- Displaying associated scripts
You can list scripts associated with a test object map. You can use the list to select multiple scripts that you want to add test objects to.
- Renewing a name in associated script(s)
You can change a vague test object name to a more meaningful name. Functional Test updates the name in associated scripts from the test object map.
- Resetting object names to the default names in associated script(s)
You can revert the object name that you have changed to the default name using the Reset all test object names feature. Functional Tester updates all the changed object names to the default name in the associated scripts.
- Add test objects to a script
You use the test object map to include an object in one or more scripts. As part of the procedure, Functional Tester displays a list of possible methods for the object and you can choose the one you want to use for the test object.
- Add test object descriptions
You can enter descriptive text about an object that Functional Tester adds to the Administrative property set tab for the object. Functional Tester also displays the description when you place the cursor over the object name in a script.
- Editing test object descriptions
You can customize the text for test objects displayed in the hierarchy tree of the test object map.
- Delete test objects from an object map
When you delete a test object from an object map, Functional Tester removes all references to the object.
- Unifying two test objects
If an object in the application-under-test changes, a test object map may have two map objects that describe the same object. You can combine these objects into a single map object. When you unify two objects, Functional Test updates scripts.
- Maintaining a test object map
To maintain a test object map, you update it to reflect new versions of the application by accepting new objects on the map, unifying test objects that are similar, and deleting any obsolete test objects.
- Renaming a test asset
You can rename simplified test scripts, Java test scripts, test object maps, or other files in a project.
- Update recognition properties
You can update recognition properties for a test object in the application-under-test.
- Delete a test object map
Deleting a test object map invalidates any scripts associated with the map, making them unusable. Deleting a test object map cannot be undone.
- Locating a test object in the application
You can select an object in the test object map or the Script Explorer and have Functional Tester highlight the object in the application-under-test.
- Searching for objects in a test object map
To search for test objects in a test object map, you can use a property, a value, or either. There are two ways to search for objects in a test object map: Quick Find and Find by Filters.
- Regular expressions
You can replace a recognition property with a regular expression or a numeric range to allow for a pattern-based recognition. The pattern allows for more flexibility in the object recognition. You can convert properties to regular expressions and numeric ranges from within the Verification Point Editor or the object map.
- Object library
Use the object library to configure object recognition properties and property weights.