Using ClearCase with test 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, Rational 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, Rational Functional Tester checks out the shared map.
• Checking in. When you check in a script that references a shared test object map, Rational 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, Rational 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, Rational 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.

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 Test script consists of several files. To maintain the integrity of each Functional Test script, you must merge the files that make up the script in the correct order.

To merge files: