Use ClearCase with test object maps
You can use ClearCase® with shared test object maps and to merge scripts across branches.
Test object maps
New test objects in an object map
Searching for objects in a test object map
Create and using a test object map to test applications
Create a new test object map
Merging multiple test object maps
Add objects to a test object map
Insert dynamic test object
Converting dynamic test object
Add a test object to an object map and a script
Editing object properties
Displaying associated scripts
Renewing a name in associated script(s)
Resetting object names to the default names in associated script(s)
Add test objects to a script
Add test object descriptions
Editing test object descriptions
Delete test objects from an object map
Unifying two test objects
Maintaining a test object map
Renaming a test asset
Update recognition properties
Delete a test object map
Locating a test object in the application
Canceling while checking in a merged test object map
Using shared object maps
About this task
- Checking out. When you check out a script that references a shared test object map, the map is checked out with the script.
- Recording. When recording a script that uses a shared test object map, Functional Tester checks out the shared map. If you record two scripts that share a test object map, check in one of the scripts, and record into the second script, Functional Tester checks out the shared map.
- Checking in. When you check in a script that references a shared test object map, Functional Tester merges and checks in the shared map before merging and checking in the remainder of the script. When you cancel a checkin that requires a shared or a private test object map merge, Functional Tester behaves differently at various stages of the procedure.
- Canceling a Checkout. If you cancel a checkout of a script that references a shared test object map, Functional Tester cancels the checkout of the map only if no other scripts have checked out the map. You will not lose edits from other scripts if you cancel the checkout.
Merging scripts across branches
About this task
Occasionally, you might find it necessary to merge scripts across branches, for example, when maintaining multiple branches, one for an imminent release and one for an upcoming release. Each Functional Tester script consists of several files. To maintain the integrity of each Functional Tester script, merge the files that make up the script in the correct order.
To merge files:
- From the graphical user interface, start the ClearCase Version Tree Browser.
- On the command line, use the merge or findmerge commands to merge files in the following order:
Do not use the Merge Manager. The Merge Manager does not allow you to specify the order to merge files. You must merge files in the following order or the Functional Tester script will not run correctly:
- Shared test object map (*.rftmap)
- Script definition (resources/*.rftdef)
- Script helper file (resources/*Helper.java)
- Verification points (resources/*.rftvp)
- Script file ( scriptname.java for Functional Tester, Java Scripting, or scriptname.vb for Functional Tester, VB.NET Scripting)
- Check in files in the same order that you merge them.
Do not check in any of the script files until all files are merged.
Functional Tester automatically merges all files except the script java file for Functional Tester, Java Scripting, or scriptname.vb for Functional Tester, VB.NET Scripting. Functional Tester does not merge test datapool files. The last datapool file you check in overrides the previous datapool file you checked in.