This topic explains how to correlate code with tests in order to configure change-based testing and requirements/defects traceability through DTP. The correlations are processed when the execution results are sent to the connected DTP (see Connecting to DTP).

Sections include:

Correlating Code During Implementation

Check-in Correlations

If code is not correlated to a task with associated requirements or defects, then the related requirement or defect should be specified upon check-in.

• Requirements: Include the following text in a revision comment when committing a file into the repository where <ID> is the requirement ID: @req <ID> 
• Defects: Include the following text in a revision comment when committing a file into the repository where <ID> is the defect tracking ID: @PR <ID> 
• Enhancements: Include the following text in a revision comment when committing a file into the repository where <ID> is the feature request ID: @FR <ID> 
• Tests: Include the following text in a comment when committing a file into the repository where <ID> is the test ID: @test <ID>  

For information on how to use a custom tag to mark defects, see Associating Tests with Development Artifacts below.

Correlating SOAtest Tests

The Requirements and Notes tab of SOAtest’s test suite configuration panel allows you to identify requirements/tasks/bugs associated with the tests in the test suite. The requirements you define will appear in Structure reports (and also in Report Center), allowing managers and reviewers to determine whether the specified test requirements were completed.

To configure correlations:

1. Select a node from the test suite tree within the Requirements and Notes tab.
2. Click the Add button.
3. In the Type box, select a requirement type. DTP will use this information to associate the test suite’s test cases to the specified element type. For instance, if it is associated with a specific bug, information about the test case’s status will be considered for Report Center’s bugs graphs. Custom tags can be added as described in Associating Tests with Development Artifacts. Default tags are:
   • @pr for bugs.
   • @fr for feature requests.
   • @req for requirements.
   • @task for tasks.
   • @test for tests
4. Enter an ID and a URL for the requirement and click OK.
   
   
   
   The requirement you defined will display in the Requirements table within the Requirements and Notes tab and correspond to the test suite node you selected and all of its child nodes.
5. (Optional) If you want to enter notes for the test suite, enter a description in the Notes field. This option is useful in that it enables you to view a quick description of the test suite purpose.

Correlating Load Test Scenarios

See Reviewing and Customizing Load Test Results.

Using Custom Defect/Issue Tracking Tags

You can customize the tags your team uses to associate a test case with a work item from your ALM, defects, or requirements tracking system (e.g, codeBeamer, Jira, TeamForge, VersionOne, etc.). This allows you to configure the tag to match the language that your organization uses to refer to defects. For instance, some organizations use the term "PR" to refer to a defect. Others use "defect" and would thus prefer to use a custom @defect tag rather than the default @pr tag.

By default, @pr is used for associating tests with defects/issues, but you can specify aliases for these tags.

1. Choose Parasoft> Preferences.
2. Select Parasoft> Issue Tracking Tags.
3. Use the available controls to add, modify, or delete tags.
   • A tag is followed by one or more values that must be represented by either a single string or a number of strings separated by separator tokens.
   • Separator token values can be any permutation of comma-separated lists of strings and whitespace-separated lists of strings.

The  tags listed here will be available in SOAtest when you configure the Requirements Tracking options in the test suite editor (when you go to Add a new requirement correlation). See Associating Tests with Development Artifacts for details.

Linking to Correlated Artifacts in Reports

If you want SOAtest reports to link to correlated artifacts, you need to specify URL templates that explain how links to these artifacts are formatted. To do this:

1. Choose Parasoft> Preferences.
2. Select Parasoft> Issue Tracking Tags.
3. In the panel’s top table, specify how links to each artifact type are formatted. For example:
   • Mapping @pr to http://bugzilla.company.com/show_bug.cgi?id=${id} means that the URL for PR1024 is http://bugzilla.company.com/show_bug.cgi?id=1024
   • Mapping @task to http://host.company.com:8080/grs/jsf/planning/task/edit_task.jsf?entityId=${id} means that the URL for task 1215 is http://host.company.com:8080/grs/jsf/planning/task/edit_task.jsf?entityId=1215