< Previous | Next >

Lesson 2: Copy a test plan

In this lesson, you create a test plan for the first JKE Banking maintenance release by duplicating another test plan.

About this task

You can reuse test artifacts by copying artifacts. Then, you can modify the copied artifacts without affecting the original artifact. Typically in the Quality Management application, the copy operation is referred to as duplication. Duplication is an efficient way to create test artifacts, and it reuses many associated test artifacts. When you duplicate a test artifact to the same project area, the test artifact is duplicated. By default, the copy refers to all of the associated test artifacts except test case execution records and test suite execution records.

In a previous lesson, Bert configured the project area to include a team area for the new run team. The run team has rotating membership and is focused on defect fixes and enhancements for released versions of the JKE Banking product. In this lesson, the test lead, Tammy, creates a test plan to start the testing effort for the first maintenance release.

Tammy has experience with the System Verification test plan. She thinks that a copy of this plan is a good starting point for planning the maintenance release. After Tammy creates the duplicate, she can modify any of the section content or links to associated test artifacts without affecting the original artifact.

For a demonstration of how to copy test artifacts in the quality management application, watch this video:
Video about copying test plans


  1. Log in as the test manager by typing tammy for both the user ID and password. If you are prompted with a project login window, select the JKE Banking (Quality Management) project. The quality dashboard opens.

    The dashboard provides an overview of project information and access to complete information. Dashboards are composed of widgets, which are small views that show different facets of the project. You can customize your dashboard by adding, configuring, and editing widgets.

    Tips: You can rearrange the dashboard by dragging widgets to different locations. Drag the My Tasks widget to the upper-right corner of the dashboard. Click Save to accept the change.

    To add, configure, and edit widgets, in the upper-right corner of the dashboard, click the Add Widget Add viewlet icon.

    Home page for the test manager

  2. Open the System Verification test plan by clicking Planning > Browse Test Plans. From the list of test plans, in the Name column, click System Verification. The test plan opens in the test plan editor.
    Tip: To open all of the sections of the test plan, at the bottom of the left menu, click the Show All Sections check box.
  3. At the top of the page, click the Duplicate (Copy) icon.
  4. In the window that opens, click Finish. In the duplicated artifact, links are created to the artifacts that are associated with the original artifact. To create a simple copy with no links to other artifacts, you can clear the Duplicate with references check box. However, Tammy wants to reuse the original test cases in her new test plan, so she uses the default settings.
    The screen capture shows the Duplicating window.
    When the operation is competed, the new artifact opens.
  5. Click Copy of System Verification and type a new name, such as JKE Banking V1.0.1.
  6. To associate the test plan with a team area and its associated artifacts, from the Team Area list, select JKE Run Team. An example of an associated artifact is the Maintenance timeline.
  7. Update the Release category.
    1. In the Summary section, click the Manage Test Plan Categories icon.
    2. Expand Release, and from the Action menu, click Create Value.
    3. For the name, type R 1.0.1. Click OK.
    4. From the Release list, select R 1.0.1.
  8. Click Save.

What to do next

Familiarize yourself with the test plan and its sections. Because the JKE Banking 1.0.1 test plan was duplicated from another test plan, several sections are preconfigured.

For example, open the Requirement Collection Links section. The Release 1 Planning requirements collection is linked to the plan. The requirements still apply to the maintenance release, although Tammy knows that extra requirements in a new collection might also apply. When those requirements are completed, Tammy adds the collection link to that section to ensure requirements traceability.

Lesson checkpoint

In this lesson, you learned how to duplicate a test artifact and assign it to a team area. A test plan can use iterations from a timeline that is also associated with the team area.
< Previous | Next >

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki