...
| Table of Contents | ||
|---|---|---|
|
Overview
You can associate test cases with requirements managed by your ALM/RMS and visualize the correlations in the Requirements view. The view shows which test cases cover the requirements so that you can easily identify gaps in requirement coverage.
Supported ALM/RMS
...
CodeBeamer
...
Jira
...
Importing from DTP requires DTP DTP 2020.2 or higher.
Importing from a ReqIF file is not supported.
...
Polarion
...
Requirements
Requirements
...
| icon | false |
|---|
- You can import requirements from either a requirements interchange format file (ReqIF) or from DTP.
- A Requirements Traceability license is required. Contact your Parasoft representative for additional information.
...
- Importing requirements from
...
- DTP requires DTP 2020.2 or newer.
ReqIF
- Export the requirements from your requirements management system in the ReqIF format. Refer to the documentation for your ALM/RMS for instructions on how to create ReqIFs.
- ReqIFs must contain all necessary information for identifying and making correlations between requirements and test definitions. This includes identifiers, names, and descriptions of requirements and test definitions, as well as information about which test definitions verify a given requirement.
...
DTP
...
Configure your SOAtest connection to DTP (see Connecting to DTP)
...
and specify the DTP project associated with the external ALM/RMS. DTP must be configured to connect to the external ALM/RMS and a project association must be configured. Refer to the DTP documentation for details.
Supported ALM/RMS
The following systems are currently supported
- CodeBeamer
- Jira (import from DTP only)
- Polarion
Importing Requirements
You can import requirements from DTP or from a ReqIF file exported from your RMS.
...
The view will be populated with either requirements from your ALM/RMS via DTP or requirements from the ReqIF. See Reviewing Imported Requirements Traceability for next steps.
Reviewing Imported Requirements
The view will reflect the project structure according to how it is defined in your ALM/RMS. All work items (requirements and their test definitions, if available) are arranged as nodes in a tree that you can collapse and expand.
You can double-click on a requirement or test definition to view it's summary details. The summary contains the ID, name, and description of the requirement or test definition. A link to the requirement or test definition will appear in the Description field.
Associating Tests with Requirement IDs
There are two methods for associating tests with requirement IDs.
- You can right-click a work item and choose Copy ID to copy its ID to clipboard. This helps you correlate a requirement or test definition with a test case by pasting the ID into your test case to create an association. IDs are associated in theRequirements and Notes tab of the test suite editor. The process for linking tests to requirements and other dev/test artifacts is described in the Indicating Code and Test Correlations section.
- Drag a test or test suite from the Test Case Explorer view into the Requirements view and drop it onto the requirement it should verify. You can also drag a requirement from the Requirements view onto the test or test suite in the Test Case Explorer.
Detecting Existing Correlations
After importing requirements to detect initial correlations, click the refresh icon on the Requirements view toolbar to scan for test cases as you work on your project.
...
You can also filter the view so that only requirements that are not covered by test cases appear in the panel.
Viewing Correlations in DTP
The Parasoft Traceability Pack extension for DTP enables you to view traceability information in DTP widgets, reports, and other visualizations. After associating tests to requirements, you can execute the test suites. Refer to the DTP documentation for details on configuring DTP to display traceability information for your SOAtest test cases.
...