In this section:
Jenkins Job Results
This widget shows the build results from a Jenkins job. You can connect the widget to the Jenkins server anonymously or specify credentials in the widget settings to connect to the server as a user. The widget shows the name of the job, build ID, and the name of the last run. Add an instance of the widget for each job you want to monitor. Use this widget to help verify that there are no errors related to building the application under test in the event that DTP is not collecting data.
This widget requires a DTP Enterprise license.
Contact your Parasoft representative for additional information.
Widget Configuration
You can configure the following settings:
Title | Enter a new title to replace the default title that appears on the dashboard. |
|---|---|
| Jenkins Server | Specify the URL of the Jenkins server, including protocol and port number, such as http://<HOST>:<PORT>. |
| Jenkins Job | Name of the job you want to monitor. |
| Jenkins User | (Optional) Specify a username to access the Jenkins server. The user must have access to the project. If you do not provide a specific user login, the Jenkins server must allow anonymous read access for the Jenkins-based widgets to function properly. |
| Jenkins Auth | (Optional) Specify a password for the user to access the Jenkins server. The user must have access to the project. If you do not provide a specific user login, the Jenkins server must allow anonymous read access for the Jenkins-based widgets to function properly. |
Actions
Click on the widget to view the job status in the Jenkins server.
Custom Dashboard Properties
This is a legacy widget and cannot be added to Custom Dashboard Templates.
Portfolio - Quality Status
This widget provides an overview of the quality status for the filters in the specified portfolio. Refer to the Configuring Portfolios section for details about configuring portfolios in DTP.
If you are a member of a project associated with a filter in the portfolio, you will see an entry in the widget for that filter. See Adding Teams to Projects for additional information about team membership or Permissions for information about built-in user permissions in DTP.
Quality status is based on data for the specified build using the following metrics:
- Severity 1 violations
- Failed tests
- Code coverage
You can configure thresholds that define acceptable levels for these metrics (see Widget Configuration). All values for the metrics must be within the acceptable range for the project status to be set to Passed. If data for the quality metrics does not exist, the status for the project will still be set to Passed.
Widget Configuration
| Title | Enter a new title to replace the default title that appears on the dashboard. |
|---|---|
| Portfolio | Choose the name of the portfolio from the menu. See Configuring Portfolios for additional information. |
| Build | Enter a build ID to use across all filters. If no build ID is specified, the latest build is used by default. Refer to Build Administration for additional information about build IDs. |
| Show Build Column | Choose Yes from the menu to include the Build column in the widget. The Build column shows the build ID specified in the Build field. Choose No to hide the Build column. If the Build column is not included, you can view the build ID by hovering your pointer over a filter in the Filter column. Refer to Build Administration for additional information about build IDs. |
| Show Violations Column | Choose Yes from the menu to include the Sev 1 Violations column in the widget. The Sev 1 Violations column shows how many severity 1 violations have occurred. Choose No to hide the Sev 1 Violations column. The Sev 1 Violations Threshold setting, described below, will still apply if the column is hidden. |
| Sev 1 Violations Threshold | Specify the maximum number of severity 1 violations allowed. If the number of violations reported exceeds the value in this setting, the quality status will be set to Fail. The default threshold is |
| Show Tests Column | Choose Yes from the menu to include the Failed Tests column in the widget. The Failed Tests column shows how many test failures have occurred. Choose No to hide the Failed Tests column. The Failed Tests Threshold setting, described below, will still apply if the column is hidden. |
| Failed Tests Threshold | Specify the maximum number of test failures allowed. If the number of test failures exceeds the value in this setting, the quality status will be set to Fail. The default threshold is |
| Show Coverage Column | Choose Yes from the menu to include the Coverage column in the widget. The Coverage column shows code coverage as a percentage. Choose No to hide the Coverage column. The Coverage Threshold setting, described below, will still apply if the column is hidden. |
| Coverage Threshold | Specify the minimum percent of coverage that is acceptable. If the reported coverage is lower than the specified value, the quality status will be set to Fail. The default threshold is |
| Width | The DTP dashboard is a six-column wide grid that can have an unlimited number of rows. Specify how many columns the widget should span. Default is Also see About the Dashboard Grid. |
| Height | The DTP dashboard is a six-column wide grid that can have an unlimited number of rows. Specify how many rows the widget should span. Default is Also see About the Dashboard Grid. |
Actions
You can interact with the widget in the following ways:
- Click on a column header to sort the data.
- Click on a link in the Build column to view the Build Audit Report.
Custom Dashboard Properties
You can add this widget to your custom dashboards by specifying the following properties in the dashboard definition JSON file (see Custom Dashboard Templates for details):
"name": "Portfolio.Quality_Status" "type": "native", "uuid": "12c53f03-1ff6-4072-ba9f-ca7586cb1e31"
Quality Status
This widget shows the overall code quality status for the target build. It uses the following metrics to determine the status:
- Number of severity 1 violations
- Number of failed tests
- Level of code coverage
You can define your quality policy by configuring the thresholds for each metric. A question mark will appear if the target build does not have data for a metric.
Widget Configuration
You can configure the following settings.
| Title | Enter a new title to replace the default title that appears on the dashboard. |
|---|---|
| Filter | Choose Dashboard Settings to use the dashboard filter or choose a filter from the menu. |
| Target Build | Choose a build from the menu. Only the data for this build will appear in the widget. |
| Coverage Image | Choose a coverage image from the menu. This is required in order to show coverage data in the widget. See Associating Coverage Images with Filters. |
| Sev 1 Violations Threshold | Specify the maximum number of severity 1 violations allowed. If the number of violations reported exceeds the value in this setting, the quality status will be set to Fail. The default threshold is |
| Failed Tests Threshold | Specify the maximum number of test failures allowed. If the number of test failures exceeds the value in this setting, the quality status will be set to Fail. The default threshold is |
| Coverage Threshold | Specify the minimum percent of coverage that is acceptable. If the reported coverage is lower than the specified value, the quality status will be set to Fail. The default threshold is |
Actions
Each metric opens its associated explorer view:
- Click Sev 1 Violations metric to view the build data in the Violations Explorer.
- Click the Failed Tests metric to view the build data in the Test Explorer.
- Click the Coverage metric to view the build data in the Coverage Explorer.
Custom Dashboard Properties
You can add this widget to your custom dashboards by specifying the following properties in the dashboard definition JSON file (see Custom Dashboard Templates for details):
"name": "Quality_Status" "type": "native", "uuid": "4181248e-95fc-421c-88b1-7e6423199177"
