If
you use ClearCase® for
source control management, you need to do some preliminary tasks to set up
a typical ClearCase installation.
Software configuration management You
can use the ClearCase integration
with Functional Tester to maintain an auditable and repeatable history of
your organization's test assets.
ClearCase
As you develop your
Functional Tester test scripts and the supporting files that accompany those
scripts, you can use Rational® ClearCase as your software configuration
management system to maintain an auditable and repeatable history of your
organization's test assets.
Functional Tester and ClearCase When
you use ClearCase with
Functional Tester, you have a choice of snapshot or dynamic views with ClearCase.
There are advantages and disadvantages to each view.
Functional Tester and ClearCase Remote Client
The IBM® Rational ClearCaseRemote
Client (CCRC) is an application designed to operate efficiently over
high latency network or wide area network. With Rational ClearCase Remote
Client, you can connect to a ClearCase Web server and access resources in
remote ClearCase repositories and load them into local ClearCase views as
ordinary files and directories under ClearCase control.
Setting up ClearCase
If you use ClearCase for source control management,
you need to do some preliminary tasks to set up a typical ClearCase installation.
Setting up ClearCase on a Windows server If
you use a version of ClearCase earlier than 2003.06 for source control
management of your Functional Tester test assets, you must update the ClearCase type
managers to recognize Functional Test object map files on Windows®.
The latest version of ClearCase includes Functional Tester type managers.
Setting up ClearCase on a UNIX server
If you use ClearCase,
you must update the ClearCase type managers to recognize Functional
Tester test object map files on a UNIX® system.
Setting up ClearCase to merge on UNIX
If you use Functional
Tester with ClearCase on
a UNIX system,
you need to set up ClearCase to merge the Functional Tester files
correctly.
Sharing a project
If you use ClearCase,
you must create the Functional Tester project in a ClearCase snapshot or dynamic view
to share a project.
Adding an element to source control A
new project, and a new script and its supporting files, are all view private
files and are not under ClearCase source control until you add them to
source control.
Checking out an element If
you use ClearCase for
source control management, you need to check out an element (a Functional
Test script, a Functional Test project, an object map or a Java™ file)
before you modify it.
Showing checkouts
If you use ClearCase for
source control management, you can list all the scripts and test assets that
you currently have checked out.
Editing an element
If you use ClearCase for
source control of your test assets, you can edit an element of the project
that is in ClearCase.
Checking in an element If
you use ClearCase for
source control management, you need to check in a script to create a new version
of a file.
Undoing a checkout If
you use ClearCase for
source control of your test assets, and if you check out an element and decide
that you do not want to change it, you can cancel the checkout.
Displaying the history of an element
When you use ClearCase as
your source control system, you can view the element type, the element name,
the date of the revisions, the first few characters of the comment, the user
who made the change, and the nature of the change for a test script or other
element in ClearCase.
Comparing versions of elements
If you use ClearCase for
source control management, you can compare an element with its previous version
to determine whether to check in your changes.
Getting the latest version
When you use a snapshot
view you must remember to get the latest files from the VOB on a regular basis
or changes that others check in can break your script. Updating once a day
is probably enough, depending on your particular team's needs.
Setting ClearCase preferences for Functional Tester
You can define the
following settings for the ClearCase integration with Functional Tester: enable
integration with ClearCase, show script details, save a file with
the keep extension, check out a script reserved, and save a new version of
the script and keep it checked out.
Support for geographically-distributed project teams As
you develop your Functional Tester test scripts and the supporting files that
accompany those scripts, you can use Rational MultiSite ClearCase as
your software configuration management system to support parallel software
development across geographically distributed project teams.
Unreserved elements There
are two kinds of checkouts for an element when you use ClearCase to manage your Functional
Tester test assets: reserved and unreserved.
Merging changes done by multiple users If
you use Rational ClearCase as
your software configuration management system, when multiple users make changes
to the same file, the second user to check in the file is required to merge.
Hijacked files When
you work with a Functional Tester script or its supporting files in a ClearCase snapshot
view, if you do not check out the file in ClearCase, and modify the file, the
file is hijacked.
Source control icons
If you use ClearCase for source control management, you can
use shortcut menus in the Script Explorer to do ClearCase operations on a selected
element, or view ClearCase icons in the Script Explorer that indicate
the state of an element.