Creating the integration testing projects

About this task

Copy a new project hierarchy from your baseline to build the integration 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 Integration Testing.
  5. In the Copy Subprojects list, you will see the projects for the baseline.

    If all of the locations you will use for build management work areas for these projects are not visible from the system you are running Rational Synergy on, copy the projects that will have visible work areas here.

    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 an integration 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 a project hierarchy, and that it will be used for integration testing. For example, a version of winxp_3.0_int would be appropriate for an integration project on a Windows XP® platform with a release of 3.0.

  7. Check the work area path and change it, if necessary.
  8. 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.
  9. Copy the projects by clicking OK.

    The integration testing project hierarchy will be created.

Results

Because you are using process rules, the update properties are already set up properly. The release and purpose of your project determine which process rule a project uses. As long as you have set the release and purpose on the project correctly, you do not need to do anything else to set the update properties.

Before you can perform build management project activities, you will need to control the project hierarchy to be used as the starting point. Most sites use the last released version of their application. If your site already uses Rational Synergy, then you will want to create a baseline from the last project hierarchy released to your customers.

Note: Be sure to create a baseline for your new project.

A baseline is a set of projects and tasks used to represent your data at a specific point in time. A baseline has many uses. When you perform an update, Rational Synergy uses a baseline as a starting point to look for new changes.

Creating a baseline for each Integration Testing and System Testing build enables testers and developers to refer back to the set of changes that were used to create the build. Typically, you will create a baseline for all projects in the same release and purpose. For example, you would create a baseline for each Integration Testing build using all Integration Testing projects for that release.

See Baselining projects and Creating a baseline for a thorough discussion.

Procedure

  1. Set your role to build_mgr.

    > ccm set role build_mgrccm set role build_mgr

  2. Copy the project hierarchy’s top-level project to any integration prep project hierarchy.

    The following command shows you how to copy a new hierarchy from a top-level project called toolkit-4.8.

    > ccm copy_project toolkit-4.8 -subprojects -purpose integrate -to 4.9_int release 4.9 -reconf tasksccm copy_project toolkit-4.8 -subprojects -purpose integrate -to 4.9_int release 4.9 -reconf tasks

    The following options need to be a part of the command:

    • Set the Purpose option to integrate (-purpose integrate). This indicates that you will create a prep project for integration testing.
    • Set the Release value to the appropriate release name, such as 4.9
      (-release 4.9).

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

    • Copy the subprojects in the project hierarchy (-subprojects).
    • Leave the default Platform value set to its current value (no change required).
    • Give the version a meaningful name (-to 4.9_int).

      The version should indicate the project hierarchy’s release and platform, and that it will be used for integration testing. For example, a version of hp_3.0_int would be appropriate for an integration project on a HP-UX platform with a release name of 3.0.

      Note: If you will release your application on more than one platform or for more than one release, repeat the preceding steps, creating an integration prep project hierarchy for each platform or release. Additionally, be sure to set the release or platform to the appropriate value.
  3. If you forgot to set the release, platform, or version, you can do so now.

    Modify the top-level project’s release, platform, or version attributes.

    > ccm attr -modifyccm attr -modify attribute -value value -project top-level_project

  4. Copy the values (-copy version) to subprojects (-subproj) in the hierarchy.

    > ccm attr -copyccm attr -copy version:release:platform -project top-level_project -subproj top-level_project

Results

Note: If your hierarchy contains projects with different platform settings, you will need to set different versions for each project with a unique version.

Feedback