A functional test project
stores application test assets such as scripts, object maps, verification
point baseline files, and script templates. You must create a functional
test project before you can record scripts.
Creating a functional test project
A functional test project
stores application test assets such as scripts, object maps, verification
point baseline files, and script templates. You must create a functional
test project before you can record scripts. You must create a new
project or connect to an existing project before you record a new
script.
Connecting to a Functional Test project
If you have an existing Functional
Test project or another member of your team has a project you need to use,
you can connect to it and use it.
Disconnecting a Functional Test project
If you no longer need to work on
a Functional Test project, you can remove it from the Functional Tester Projects
view.
Deleting a Functional Test project
There may be times that you want
to delete a project that is no longer needed from the Functional Test Projects
view. If you use ClearCase® for source control, you can delete a
project only from your view, or from your view and from the ClearCase VOB.
Functional Test Projects view
The Functional Test Projects view, which is the left pane
of the Functional Test Perspective, lists test assets for each project.
Exporting functional test project items
You can export project items
such as scripts, test object maps, Java™ files
or Visual Basic files, datapools and application visuals to another
functional test project.
Importing functional test project items
You can import project items
such as scripts, test object maps, Java files
or Visual Basic files, and datapools into a Functional Tester project.
Functional test projects and Rational projects
When you create a Functional
test project, you can associate it with a Rational® project
to take advantage of the Functional Tester integration features with
TestManager if you have TestManager installed.