Managing functional test assets
You can integrate HCL OneTest™ UI with
IBM® Rational® ClearCase®
or Rational Team Concert™ and manage functional test assets using any of these source control management tools.
- Software configuration management
You can use the ClearCase or Rational Team Concert integration with HCL OneTest UI to maintain an auditable and repeatable history of your organization's test assets. - Testing with Rational ClearCase
As you develop your HCL OneTest UI 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. - Using ClearCase with test object maps
You can use ClearCase with shared test object maps and to merge scripts across branches. - 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 test assets, you must update the ClearCase type managers to recognize Functional Test object map files on Windows. The latest version of ClearCase includes HCL OneTest UI type managers. - Setting up ClearCase on a UNIX server
If you use ClearCase, you must update the ClearCase type managers to recognize HCL OneTest UI test object map files on a UNIX system. - Sharing a project
If you use IBM Rational ClearCase, you must share the functional test project and then add the project to source control. When you share a project, you move it to a Rational ClearCase snapshot or dynamic view. The project must be in a Rational ClearCase view for you to add it to source control. - Adding an element to source control
A new solution, project, or 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. - Adding a solution to source control
You must add a solution to ClearCase to share test script assets, merge files, and provide version 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 display all the checked out elements and all the new elements that you have not added to source control. - 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 - Setting check out options
If you use ClearCase for source control management, you can change the checkout options from unreserved, the default, to reserved if you do not want other users to check the file or script in while you work on it. - Setting undo checkout options
If you use ClearCase for source control management, you can set the undo checkout option to save a copy of a script whose checkout you want to cancel. The saved file has a _keep extension. - 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 after all, 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. - Canceling while checking in a merged test object map
When you cancel a check in that requires a shared or a private test object map merge, HCL OneTest UI behaves differently at various stages of the procedure. - Setting ClearCase options for HCL OneTest UI
If you use ClearCase for source control management, you can change the default settings for checkout -- reserved or unreserved, or define undo checkout with a _keep extension. - Support for geographically-distributed project teams
As you develop your HCL OneTest UI 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 HCL OneTest UI 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 HCL OneTest UI 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. - ClearCase state icons
If you use ClearCase for source control management, the Solution Explorer displays icons next to each file to indicate the state of an element. - Software configuration management
You can use the ClearCase or Rational Team Concert integration with HCL OneTest UI to maintain an auditable and repeatable history of your organization's test assets.