Linking test cases to development work items

If your team has set up an integration with Rational® Team Concert® version 2.x or the Change and Configuration Management (CCM) application, you can link your test cases to development work items. As such, you can set up a mapping between a feature that a developer is working on and your test case.

Before you begin

Before you can link a test case to a work item, these requirements must be met:

  • Integration must be configured with Rational Team Concert version 2.x or the CCM application.
  • There must be work items in an Engineering Workflow Management or CCM project area to be linked to.

About this task

The types of work items that are available depend on the process that the development team is using. Not all work item types are available in all processes. Typical work item types include Plan Items, Defects, Enhancements, Tasks, Stories, and so on. For more information about work items, see the section on "Managing change and releases".
Limitations:
  • If configuration management is enabled for your project, the current configuration must be a global configuration to link to artifacts such as requirements or development plans in other Engineering Lifecycle Management applications.
  • If you have not enabled configuration management, when you create a link to external artifacts in a ELM application, a link is automatically created back to the source artifact in the target application, which is called a back link. However, the synchronization between bidirectional links and the traceability between source and target artifacts are not guaranteed.
When a source artifact and target artifact link to each other, this is known as bidirectional linking. The source and target applications store their links in separate databases, and the source application does not have access to the database in the target application. Certain transactional operations, such as when artifacts are copied or deleted, can occur on the source application server. In these cases, corresponding back links in artifacts in the target application are not automatically added or removed. Also, instances occur where back links are intentionally removed from the target application without removing the corresponding link from the source application. As a result, if bidirectional links are not in a state of synchronization, traceability between the source and target artifacts can appear different based on your starting viewpoint.

Procedure

To link a test case to a work item:

  1. Open a test case or create one.
  2. If there is no Development Items section in your current test case, you can add one:
    1. In the test case, click Manage Sections.
    2. In the Manage Sections window, click Show all Sections.
    3. Select Development Items, and then click the arrow pointing to the right.
    4. Click the up or down arrow to move the Development Items section to the appropriate location in the test case.
    5. Click OK.
  3. In the table of contents, click Development Items to open the Development Items section.
  4. Click the Add development items icon (Add).
  5. Select the work item to link to the test case.
    1. In the Type field, select the work item type to search for; then select Show All to show all work item types.
    2. Type the work item ID or words that the text of the work item contains.
    3. Select the work item that you want from the list.
    4. Click OK to add the work item to the test case.
    5. Click Save to save the test case.

Results

After the work item is added to the test case, you can hover over the work item ID to view the status of the work item. When the developer updates the status in the work item, the changes will be reflected in the work item ID in the test case.

Later, you can open the test case from the link in the work item.


video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki