This topic explains how to use ClearCase with shared test object maps and to merge scripts across branches.
Using Shared Object Maps
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. For information, see Canceling While Checking in a Merged Test Object Map.
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
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. You can merge files in a variety of ways:
From the graphical user interface, start the ClearCase Version Tree Browser.
On the command line, use the merge
or findmerge
commands.
Use either of these commands instead of the Merge Manager. Merge Manager does not allow you to specify the file sequence, as described below.
Functional Tester scripts consist of several files. To maintain their integrity, scripts must be merged in the following order:
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)
The merge of all files except the script java file for Functional Tester, Java Scripting, or scriptname.vb for Functional Tester, VB.NET Scripting is automatic. Functional Tester does not merge test datapool files. The last datapool file you check in overrides the previous datapool file checked in.
Do not check in any of the script files until all files are merged. Then check in files in the same order that you merged them.
Terms of use | Feedback
(C) Copyright IBM Corporation 2002, 2004. All Rights Reserved.