Creating the system testing projects

About this task

Copy a new project hierarchy from your baseline. This project will be used to build the system testing area.

Procedure

  1. Find the baseline by using the Query dialog box.
  2. Right-click over the baseline and select Copy Projects.

    The Copy Project dialog box appears.

  3. Set the For Release value to the appropriate release.

    If an appropriate release is not in the For Release list, use Refresh Choices. If necessary, see Creating or copying a release.

  4. Set the For Purpose choice to System Testing.
  5. In the Copy Subprojects list, you will see the projects for the baseline.

    For example if you develop your application on more than one platform, such as on Windows and UNIX, be sure to copy Windows projects separately from UNIX projects, using the appropriate Windows or UNIX machine. Additionally, if you develop your application for more than one release, be sure to create a system testing project hierarchy for each release.

  6. Change the new project version to a meaningful name by typing a new name in the Versions field. If the projects you are copying should have different versions, click to see each unique version of the projects being copied.

    Click Use Default and then type the new version for each entry.

    The version should indicate the release and platform for the project hierarchy, and that it will be used for system testing. For example, a version of winxp_3.0_sys would be appropriate for a system testing project on a Windows XP platform with a release of 3.0.

  7. By default, Rational Synergy updates all new projects after it copies the projects. If you do not want the new projects to be updated, clear the Update new projects check box.
  8. Check the work area path and change it, if necessary.
  9. Copy the projects by clicking OK.

    The system testing project hierarchy will be created.

Procedure

  1. Set your role to build_mgr.

    > ccm set role build_mgrccm set role build_mgr

  2. Copy a system test prep project hierarchy from the top-level project. (The following command shows you how to copy a new hierarchy from a top-level project called toolkit-4.8.)

    > ccm co -projectccm co -project toolkit-4.8 -subprojects -purpose sqa -to 4.9_sqa -release 4.9

    • The following options need to be a part of the command:
      • Set the Purpose option to sqa (-purpose sqa).
      • Set the Release value to the new release name (-release X).
      Note: If your project hierarchy contains multiple platforms, you’ll need to set an option to define the platforms to be checked out, as follows:
       > ccm co -projectccm co -project tool_top-1.0
      -subprojects -release 2.0 -purpose sqa
      -versions "1.0:sqa_2.0,win_1.0:win_sqa_2.0,hp_1.0:hp_sqa_2.0"

Results

If you set the release value to a name that does not exist as a release value, you will receive an error message and the copy will fail. Refer to How to modify release values to add the appropriate release value.

  • Leave the default Platform value set as it currently is (no change required).
  • Give the version a meaningful name (-to 4.9_sqa). The version should indicate the project hierarchy’s release and platform, and that it will be used for system testing. For example, a version of hp_3.0_sqa would be appropriate for an sqa project on a HP-UX platform with a release name of 3.0.
  • Copy the subprojects in the project hierarchy (-subprojects).
    Note: If you will release your application on more than one platform or for more than one release, repeat the preceding steps, creating a system test prep project hierarchy for each platform or release. Additionally, be sure to set the release or platform to the appropriate value.

Feedback