This topic explains how to You can generate HTML, PDF, or custom XSL reports for tests that you run from the GUI or command line.Sections include. In this section:
Table of Contents | ||
---|---|---|
|
Info | ||
---|---|---|
|
...
A known bug in |
...
older versions of Eclipse may cause the IDE to crash when displaying reports. |
...
If you are experiencing this issue, here are some workarounds:
|
...
|
...
Generating Reports from the GUI
Anchor | ||
---|---|---|
|
|
After the test has completed, click the Generate Report button
that is availablein the Test Progress panel’s toolbar.
Complete the Report dialog that opens. The Report dialog allows you to
specifyconfigure the following options:
Preferences:
Report preferences (by clicking the Preferences button and specifying settings as explained inSee Configuring Reporting Settings
).
Options file:
Any localsettings/options that specify reporting settingsIf you want to
use. These willoverride the report settings specified in the
GUI’s Preferences panel). For details on configuring reports through localsettings,GUI’s Preferences panel, you can specify a .properties file configured with your custom report settings. Also see Configuring Localsettings
Report location:
The location ofSpecify where to output the report file
(by. By default, reports are created
atin the
)<user_home_dir>\Local Settings\Temp\parasoft\xtest
directory.
Open in browser:
WhetherEnable/disable opening the report file
is automatically openedin
athe browser automatically.
Delete on exit:
Whether the report is deleted upon exitEnable/disable deleting the report upon exiting C++test.
Generate reports:
Whether a report should be createdEnable/disable generating a report. You cannot proceed if this setting is disabled.
Publish reports to Team Server:
Whether the report should be uploaded to the Team Server (Server Edition only; requires Team Server).Publish code reviews: Whether code review tasks/results should be uploaded to the Team Server (any edition; requires Team Server)Enable this option if C++test is connected to DTP and you are using Team Server to manage shared reports and configurations.
Click OK. The report will then open. For details on the format and contents, see Understanding Reports
Tip | ||
---|---|---|
| ||
You can also generate and configure reports from the bottom of the Test Progress panel. Proceed immediately generates the report using the existing options. Configure allows you to review and modify reporting options before generating the report. |
Anchor | ||||
---|---|---|---|---|
|
You can generate an additional Test Execution Details report linked to your regular report (see Understanding Reports for details). To generate this report, configure the following settings in the test configuration before executing it:
- Choose Parasoft> Test Configurations... and select a test configuration.
- Open the Execution> Runtime tab and enable the following options:
- Report unit test execution details
- Include tasks details
- Include passed assertion details
- Generate detailed test execution report
- (Optional) Enable the Generate detailed coverage report for option and choose a coverage metric.
- Apply changes and close the test configuration.
- Choose Parasoft> Preferences... > Reports.
- In the Report Format section, choose HTML (C/C++test’s Unit Testing details) from the drop-down menu.
Click Generate Report after the test completes (see Generating the Report). The link to the Test Execution Details report will be available in the Test Execution Details column included in the Additional Reports section at the bottom of main report (see Understanding Reports).
You can also generate the Test Execution Details report in XML format. This enables you to apply additional post-processing workflows to the test execution results. The XML file is available in the same location as the original Test Execution Details HTML file, for example:
<REPORT_DIR>/<EXECUTION_DIR>/report_TestSuiteFoo_cpp.xml
<REPORT_DIR>/<EXECUTION_DIR>/report_TestSuiteFoo_cpp.html
In addition, XML Schema for Test Execution Details XML file is available:
<CPPTEST_INSTALL_DIR>/manuals/examples/ut_details_report_schema.xsd
Uploading the Report to DTP
To upload the report to DTP:
Ensure that C++test is connected with a DTP Server (See Connecting to DTP).
Go to Parasoft> Preferences... > DTP and enable the Enable reporting results to DTP option in the Reports area.
Publishing reports to DTP requires the "DTP Publish" or "Automaton" license feature to be enabled.
Uploading the Report to Team Server
To upload the report to Team Server (Server Automation Edition only):
Follow the above procedure, but be sure to enable Publish Reports to Team Server before clicking OK.
Info | ||
---|---|---|
| ||
Team Server uses the following criteria to identify unique reports:
If your team performs multiple cli runs per day—and you want all reports included on Team Server—you need to use a different session tag for each run. You can do this in the Test Configuration’s Common tab (using the Override Session Tag option). |
Uploading the Report to Development Testing Platform
To upload the report to DTP:
- Ensure that C++test is connected with a DTP Server (See Connecting to DTP).
- Go to Parasoft> Preferences... > Development Testing Platform and enable the Enable reporting results to DTP option in the Reports area.
Publishing reports to DTP requires the "DTP Publish" or "Automaton" license feature to be enabled.
...
Generating Reports from the Command Line
To generate a report of command line test results, use the -report %REPORT_FILE%
option with your cli command.
...
Command-line interface testing details are explained Testing from the Command Line Interface. This topic also discusses how to setup and configure email notifications.
Scroll Pagebreak |
---|