...
| Detailed report for developers | Enable 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 to include an overview of the number and type of tasks assigned to each developer. For SOAtest reports, it is necessary to enable this option if you want to include details about failed tests. |
| Overview of checked files and executed tests | Enable 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, the 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, and so on) 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 Requirements/defects details, which specifies whether the report shows requirements, defects, tasks, and feature requests that are associated with a test. |
| Findings details | Enable to include details about static analysis findings. |
| Suppression details | Enable to include information about suppressed static analysis violations. |
| Active rules | Enable 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. |
...