If you use ClearCase® for source control management, you can
use the Check Out dialog box to check out a script before you modify it.
You can check out an entire project or one or more files at a
time. Use the Check Out dialog box to check out a file to modify it.
- Selected Elements
- Lists the scripts, files, object maps, class files, or projects that you
select from the Functional Tester Projects view.
- Check Out
- Select to check out an element. Clear the Check Out check
box if you do not want to check out an element. If unavailable, a gray box
appears instead of a check box, and you cannot check out this element.
- File, Script, Element, or Project Name
- Displays the name of the element, project, script, or file name. If an
element is in a folder, the folder appears as <foldername>.<filename>.
For example, Myfolder.myfile.
- Project Name
- Displays the name of the project.
- Details of <selected element>
- Lists the state, file name, and path for each supporting file of an element
or the selected element under Selected Elements. Functional
Tester does not display the script details unless there is a problem checking
in the files. If the script details are not visible, optionally, set
the Rational Functional Test ClearCase Preferences to display the script
details.
- State
- Displays the state of each supporting file.
- File, Script, Element, or Project Name
- Displays the name of the element, project, script, or file name. If an
element is in a folder, the folder appears as <foldername>.<filename>.
For example, Myfolder.myfile.
- Path
- Displays the location of each supporting file in a Functional Tester project.
- Some of the files in selection have been hijacked
- Appears if you modify an element without checking it out. ClearCase hijacks
this element. The hijacked file appears under Details of <scriptname> with
a warning symbol (
) next to the file. Unavailable if an element is not hijacked.
- Convert hijacked files to checkout
- Appears if you modify an element without checking it out. Click to check
out the hijacked version of the file. When you check in the file, the hijacked
version replaces the version in the VOB.
- Replace hijacked files (save each hijacked file to a file with
a _keep extension)
- Appears if you modify an element without checking it out. Click to check
out the version of the file in the VOB. When you check in the file, ClearCase checks
in the version in the VOB and creates a copy of the hijacked file with a _keep
extension in case you need the changes later.
- Request Mastership
- Displays in a ClearCase multisite situation, when one or more
of the files in the selected scripts, shared maps, or Java™ files
is not mastered locally. Click to request mastership for the file. For more
information, see About Requesting Mastership.
- Reserved
- Click to reserve a checkout. A reserved checkout gives you the exclusive
right to check in the element when you are done. Clear to check out an element
unreserved. With an unreserved checkout, you might need to merge your changes
at checkin time, if someone else checked in the same element before you did.
- Finish
- Applies the settings in the Check Out dialog box to a single element or
to multiple elements.
To open: In the Functional Tester Project view, right-click
one or more elements, and then click .