The Build Audit Report shows all test and analysis artifacts and metadata associated with a build so that you can understand how well the build is tested. You can archive builds from the repost to prevent test and coverage from being removed during normal database procedures, as well as lock builds so that they can be used as baselines in widgets and explorer views. For additional information about the concepts covered in this report, please see DTP Concepts.
Click on a build from the Build Administration page (see Build Administration - Statistics) to access the report. The Build Audit Report has the following sections:
The Summary table provides an overview of the test and analysis data associated with the build. Any descriptive tags added on the build administration page are shown in parentheses next to the build ID in the header. You can also archive and lock the build by clicking the icons. See Locking and Archiving Builds for additional information.
The Tests table shows the number of tests passed, failed, and incomplete organized by test type, such as functional or unit tests, associated with the build. The number of passing tests are also represented as a percentage. Test data is automatically merged so that overlapping tests do not affect the totals reported.
The Coverage table shows the code coverage associated with the build organized by coverage image (see DTP Concepts to learn about coverage images, builds, and other concepts).
DTP supports up to five coverage images per build. The run configuration associated with the coverage image displays in parentheses. The following coverage images are included by default:
See Associating Coverage Images with Filters for additional information.
The Static Analysis table shows the number of violations and suppressed violations reported in the build.
The specific run information associated with the build is displayed in an interactive Runs table.
You can perform the following actions:
The Setup Problems column lets you know if the report contains irregularities related to the analysis and test execution tool configuration. Setup problems are organized by severity into the following categories:
The Build Audit Report shows setup problems in the following format:
<total problems>[<number of errors>, <number of warnings>, <number of infos>]
You can hover over a link in the Setup Problems column for a quick overview.
Click on a link to open the Setup Problems report, which provides detailed information.
See the documentation for your code analysis and test execution tool for additional information.
Builds must be locked and archived before you can download a report associated with the build. See Using Build Administration for additional information. You can download a complete Build Audit Report archive, which includes reports for all run IDs, or download individual reports for each run ID. You can download reports in XML, HTML, or PDF format.
The information presented in the report is dependent on the type of run (static analysis, test execution, etc.) and the report settings configured for code analysis and test execution tool. As a result, some preferences may not be applicable to the report data. See the documentation for your tool for details.
| Detailed report for developers | Enable this option to generate customized detailed reports for each team member. These reports contain tasks assigned to the specific team member. |
|---|---|
| Overview of findings by authors | Enable this option to include an overview of the number and type of tasks assigned to each developer. |
| Overview of checked files and executed tests | Enable this option to include details about all checked files and executed tests. For static analysis, the report will include a list of all the files that were checked. For each file, thr report lists the number of rule violations and the number of suppressed violations. If the file has a violation, it also lists the line number, rule name, and rule ID for that violation. For test execution, the report will include a list of all executed test cases and their outcomes (pass or fail). For each test suite, the report lists the total number of test cases and the number of passed test cases. If a task is reported for a test case, additional details (stack trace, outcome, etc.) are presented. For code review, the report will include a list of all pending issues with messages between author - reviewer - monitor (filtered by session tag by default). You can also enable the Requirements/defects details option, which specifies whether the report shows requirements, defects, tasks, and feature requests that are associated with a test. |
| Findings details | Enable this option to include details about static analysis findings. |
| Suppression details | Enable this option to include information about suppressed static analysis violations. |
| Active rules | Enable this option to include a list of the rules enabled during analysis. |
| Highlight coverage below | Specify a percentage threshold for highlighting test coverage. |
| Setup problems | Choose an option for viewing setup problems. |