You can export test assets, and then
import them into another project or workspace without losing any dependencies.
Test assets include projects, schedules, and tests. You can export and import
test assets to collaborate with other testers.
Before you begin
If you plan to export assets with dependencies, make sure that you
have migrated the test assets to the current version of the product before
you start to export.
About this task
When you copy a test with dependencies, any datapools or custom
code referred to by the test are also copied. When you copy a schedule with
dependencies, any locations or tests referred to by the schedule are also
copied. When you copy results, any schedules or tests referred to by the results
are copied.
Procedure
- In the Test Navigator view, right-click the
test assets to export, and then click Export. You can export projects, schedules, tests, and test results with dependencies.
- In the Export window, expand the Test folder,
and then click Test Assets with Dependencies. You can export test assets with dependencies if the test assets were
created in the current version of the product. You cannot export test assets
with dependencies if the test assets were created in a previous version of
the product and the assets have not been migrated to the current version of
the product.
- Click Next.
- Specify the path and name of the archive file into which you want
to export the selected test assets.
- Click Finish. The assets are
exported to the archive file.
- If the target workspace is on a different computer, transfer the
archive file to a location that is accessible to that computer.
- In the Test Navigator view, select the test
project into which you want to import the test assets. The target
project must have the same name as the source project. Optionally, you can
import test assets with dependencies into a workspace where no projects exist.
If you import test assets with dependencies into a workspace where no projects
exist, the Import wizard creates projects based on information from the archive
file. To import test assets into a project with a different name, you must
first import the test assets into a project with the same name, and then manually
move the assets into the project with the different name.
- Click .
- In the Import window, expand the Test folder,
and then click Test Assets with Dependencies.
- Click Next.
- In the Import with dependencies window, click Browse,
and then select the archive file. The test assets are displayed
in the File contents list.
- Click Finish to import the test assets with
dependencies from the archive file into the target project. If
a file that you are attempting to import already exists in the target workspace,
you will be prompted to choose whether to overwrite the file. You can also
choose to overwrite all files that already exist in the target workspace,
or not to overwrite any files that already exist in the workspace. If you
choose to overwrite all files that already exist in the target workspace,
you will be prompted again if the import process encounters a .classpath or .project file
in the source archive file.