This topic describes viewing SOAtest results. In this section:
By default, the Quality Tasks view shows cumulative results for all tested resources. For example, if you imported results from DTP, then ran two tests from the GUI, the Quality Tasks view would show all imported tasks, plus all results from the subsequent two tests.
If you prefer to see only results from the last test session or from selected resources, you can filter results.
The Quality Tasks view links directly to the Test Configuration that resulted in the task. You can right-click on a task and choose View Test Configuration to review the configuration, which will open directly to the Test Configuration controls related to the task. For instance, if a static analysis task was selected, the Static tab will be opened and the corresponding rule will be highlighted.
This enables you to review or modify the Test Configuration setting, as well as verify the Test Configuration used if the results are imported from a server execution.
There are several ways to customize the results display to preferences and needs for reviewing quality tasks and/or peer code review tasks.
You can change the Quality Tasks view’s format and contents by:
There are several available layout templates:
To select the layout best suited to your current goal:
Open the pull-down menu on the top right of the Quality Tasks view.
To customize one of these preconfigured layouts:
To add a new layout template:
To re-order, hide, and remove categories directly from the Quality Tasks view:
You might want to clear messages from the Quality Tasks view to help you focus on the findings that you are most interested in. For example, if you are fixing reported errors, you might want to clear each error message as you fix the related error. That way, the Quality Tasks view only displays the error messages for the errors that still need to be fixed.
Messages that you clear will only be removed temporarily. If the same findings are achieved during subsequent tests, the messages will be reported again.
You can clear individual messages, categories of messages represented in the Quality Tasks view, or all reported messages.
To clear selected messages shown in the Quality Tasks view:
The selected messages will be removed from the Quality Tasks view.
To clear all messages found:
This topic explains how to generate HTML, PDF, or custom XSL reports for tests that you run from the GUI or command line.
Sections include:
There are some limitations in the default reports produced by desktop installations from the GUI or command line. For more details, see Legacy Report Format. |
To generate a report immediately after a test completes:
Preferences: Report preferences (by clicking the Preferences button and specifying settings as explained in Configuring Report Settings).
Option file: Any settings/options that specify reporting settings you want to use. These will override settings specified in the GUI’s Preferences panel).For details on configuring reports through settings, see Configuring Settings.
<USER>\AppData\Local\Temp\parasoft\reports
(Windows) or <USER>\parasoft\reports
(macOS).To generate a report of command line test results, use the -report %REPORT_FILE%
option with your cli command. See Testing from the Command Line Interface - soatestcli for details.
If you want your report to show details about every test that ran, including tests that did not fail, configure reporting preferences with the Only tests that failed and Only top-level test suites options disabled. |
In the Quality Tasks view, SOAtest results are presented as a task list that helps you determine how to proceed in order to ensure the quality of your system.
Functional test results are organized by test suite. See Reviewing Functional Test Results for details.
Static analysis results should be reviewed in one of the layouts designed especially for static analysis. For details on enabling these layouts and reviewing static analysis results, see Reviewing Static Analysis Results.