In this section:

Introduction

The Parasoft Traceability Pack is a set of artifacts for your DTP infrastructure that help you establish and demonstrate traceability between tests, code analysis, and peer reviews performed with Parasoft tools and requirements in external application lifecycle management (ALM) systems. The following ALM systems are supported:

  • Azure DevOps
  • codeBeamer ALM
  • Jama Connect
  • Jira - The Xray test management plugin is also supported 
  • Polarion ALM 
  • VersionOne

The Parasoft Traceability Pack also includes the Jira Issues Widget and a custom flow for sending test data to the connected ALM.

Contact your Parasoft representative for download and licensing information.

The Traceability Pack includes the following components.

External System Traceability Reports Flow 

This artifact contains the DTP traceability widgets and reports for tracking traceability between the requirements stored in your ALM system and the test, static analysis, and build review data sent to DTP from Parasoft tools (C/C++test, dotTEST, Jtest).

Sending Test Data to External System Flow

This artifact automatically calls the syncTestCases DTP REST API endpoint when Data Collector receives unit or functional test execution results from Parasoft tools. The API sends the test results from DTP to the associated external application.

Jira Issues Slice

This artifact adds two widgets that show issues from the connected Jira system. Both widgets are pie charts that organize issues by status or by priority. One widget has settings for querying Jira. The other widget allows you to manually enter a JQL to find issues.

Requirements

  • Refer to the requirements section for each individual integration.

Installation and Usage

Refer to the following chapters for installation and usage details:

Upgrading

Although Parasoft extensions are designed to be forward compatible, they are not guaranteed to work in newer versions of DTP or Extension Designer. We strongly recommend installing the latest version of the artifact and removing the previous version. 

  1. (Optional) If you have applied custom changes to models and/or profiles associated with your artifacts, back them up before upgrading. See Working with Model Profiles for instructions on how to export copies of your models and profiles. 
  2. Delete the existing models/profiles and install the newer artifact as described in Installation and Usage for your integration. 
  3. Un-deploy older artifact from Extension Designer by deleting its nodes and clicking Deploy
  4. Deploy the newer version. 
  5. (Optional) New models and profiles are installed as part of the upgrade. If you backed up models/profiles, refer to them and apply any modifications you may have implemented in the previous version to the newly installed models/profiles.
  • No labels