Copying a project to another workspace

You can export performance test projects and their contents from a workspace and import them into another workspace on the same or a different computer. Doing this allows testers to collaborate in the absence of a source control system.

In these instructions, the source workspace is the Eclipse workspace containing the exported performance test project. The target workspace is the destination into which the project is being imported.
  1. Start Performance Tester in the source workspace.
  2. Export the project(s) to a ZIP file. For instructions, see Exporting resources to a ZIP file. Note: datapools can be located in the same project as the tests that use them or in different projects. You should export any datapools in the source workspace that exported tests require.
  3. If the target workspace is on a different computer, transfer the ZIP file to a location accessible from that computer.
  4. Start Performance Tester in the target workspace.
  5. Create a performance test project(s) with the same name as the project(s) that you zipped from the source workspace. For instructions, see Creating a performance test project.
  6. Import the zipped source project(s) onto the target project(s). For instructions, see Importing resources from a ZIP file. As shown in the following figure, on the Import dialog box, change Into folder to /.
  7. (Optional) Modify the Java build path.

    If the imported project contains custom code or tests that have been executed, the Java build path might need to be changed in a number of cases including the following:

    • The Java build path was manually modified in the project from which it was exported. In this case, the same modifications need to be made in the imported project. During the import, you are asked whether to overwrite the .classpath file (which stores the project's Java build path). Answering Yes reduces the likelihood that the build path will require modification.
    • The project was imported onto a different computer with a different Java installation configuration. In this case, missing libraries must be removed from the build path.
    • The project was imported into a workspace on a different drive letter. Answering No when asked whether to replace the .classpath file reduces the likelihood that the build path will require modification.

    For instructions on build path modification, see Viewing and editing a project's Java build path.

Parent topic: Creating tests

Terms of use | Feedback
(C) Copyright IBM Corporation 2005. All Rights Reserved.