Page tree

Skip to end of metadata
Go to start of metadata

This practice allows you to specify a development guideline that your code should comply with, as well as define thresholds for acceptable levels of compliance.  In this section:


In Parasoft, "a compliance" is a collection of code analysis rules that have been mapped to check against a particular development standard or set of guidelines, such as MISRA C:2012 or OWASP Top 10. By default, Parasoft code analysis rules are grouped according to general concepts, such as "Exception" and "Initialization," but these compliance categories can be reoriented to the nomenclature used in various standards and guidelines. See Custom Compliance Categories for additional information.  


  • DTP 5.3.3 or later
  • DTP Enterprise Pack 5.3.3 or later


See Downloading and Installing Artifacts.

Adding Practices to Your Policies

A practice is a mechanism for monitoring and enforcing development and testing policies. See Defining Policies for instructions on adding and managing practices.


  1. Choose a compliance category from the Select compliance drop-down menu. DTP ships with limited compliance categories, but you can define your own categories or install a compliance extension (i.e., MISRA Compliance pack). 

  2. Define your compliance thresholds in the fields provided.

Monitoring Compliance

You can add the Gate Summary - Donut widget to your dashboard and configure it to the project and gate holding your compliance practice configuration. This widget is available from the Parasoft Marketplace. See the Policy Center Gate Summary Widget documentation for additional information on installing and configuring the widget.

  • No labels