Using ClearCase with test object maps

You can use ClearCase® with shared test object maps and to merge scripts across branches.

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, HCL OneTest UI 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, HCL OneTest UI checks out the shared map.
  • Checking in. When you check in a script that references a shared test object map, HCL OneTest UI 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, HCL OneTest UI 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, HCL OneTest UI 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 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:

Procedure

  1. From the graphical user interface, start the ClearCase Version Tree Browser.
  2. On the command line, use the merge or findmerge commands to merge files in the following order:
    Note: 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 Test script will not run correctly:
    1. Shared test object map (*.rftmap)
    2. Script definition (resources/*.rftdef)
    3. Script helper file (resources/*Helper.java)
    4. Verification points (resources/*.rftvp)
    5. Script file ( scriptname.java for HCL OneTest UI, Eclipse Integration, or scriptname.vb for HCL OneTest UI, Microsoft Visual Studio .NET Integration)
  3. Check in files in the same order that you merge them.
    Note: Do not check in any of the script files until all files are merged.

Results

HCL OneTest UI automatically merges all files except the script java file for HCL OneTest UI, Eclipse Integration, or scriptname.vb forHCL OneTest UI, Microsoft Visual Studio .NET Integration. HCL OneTest UI does not merge test datapool files. The last datapool file you check in overrides the previous datapool file you checked in.

Feedback