When you use ClearCase with Functional Tester, you must install ClearCase LT which comes with Functional Tester, or purchase and install ClearCase to use the Functional Tester integration with ClearCase.
With ClearCase LT you can use a snapshot view. A snapshot view contains copies of ClearCase versions and other file system objects in a directory tree on a local system. ClearCase LT does not support dynamic views. Dynamic views use, create, and maintain a directory tree that contains versions of VOB elements and view-private files. If you purchase and install ClearCase, you can use a snapshot or a dynamic view.
The advantages of using a snapshot view with Functional Tester are:
Only the scripts that you change compile when you record or play back a script so the performance can be faster than a dynamic view.
The disadvantages of using a snapshot view are:
Files are not updated automatically. 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.
A snapshot view uses a lot of disk space on your local hard drive because a snapshot view copies every file in the Functional Test project to your local hard drive.
The configuration specification that you use can affect the following advantages and disadvantages of a dynamic view .
The advantages of using a dynamic view with Functional Tester are:
Files do not take a large amount of disk space on the local machine because only the files that you check out or create exist on your local hard drive.
Files in a dynamic view are always current with the VOB. You do not have to remember to get the latest files from the VOB as you do in a snapshot view.
The disadvantages of using a dynamic view with Functional Tester are:
In a large team, when many users change scripts,
it may take a long time for all the changes to compile when you record
or play back a script.
Functional Tester, Java Scripting, compiles the project when an element
changes. If you are using a dynamic view, automatic compilation can be
time consuming, depending on the size of the project. To disable this
feature, click Window >
Preferences and clear the Build automatically check box. Functional
Test, VB.NET Scripting, does not automatically compile the project when
an element changes.
You can use the Functional Tester integration with ClearCase to perform these tasks:
Perform ClearCase tasks from the Functional Tester Projects view for Functional Tester, Java Scripting or from the Solution Explorer for Functional Tester, VB.NET Scripting.
Create a Functional Tester project and add it to source control from Functional Tester.
Add an existing Functional Tester project to source control after you create it in a ClearCase view.
Add a Functional Tester script to source control.
Remove a Functional Tester script from source control.
Check out a Functional Tester script from source control.
Check in a Functional Tester script to create a
new version of the script with changes.
A merge
operation occurs during checkin if another user has checked in the same
file.
Restore the previous version of a script.
Refresh the local, snapshot view with the most current copy of a script. This operation is necessary only with snapshot views.
List all scripts and files checked out in the current view.
Compare differences between the current script and its immediate predecessor.
Manage the supporting files for each script easily when you add a script to source control, check in or check out a script, or get the latest version of a script, all the supporting Functional Tester files for that script are managed.
View a history of the changes made to a script.
Related Topic:
About Software Configuration Management
Terms of use | Feedback
(C) Copyright IBM Corporation 2002, 2004. All Rights Reserved.