...
Report Limitations
| Info | ||||
|---|---|---|---|---|
| ||||
There are some limitations in the default reports produced by desktop installations from the GUI or command line. See the list below, for more details. |
| Anchor | ||||
|---|---|---|---|---|
|
Generating the Report
...
- After the test has completed, click the Generate Report button that is available in the Test Progress panel’s toolbar.
- Complete the Report dialog that opens. The Report dialog allows you to specify:
Preferences: Report preferences (by clicking the Preferences button and specifying settingsas explained in Configuring Reporting Settings).
Option file: Any localsettings/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 localsettings, see Configuring Localsettings.
- Report location: The location of the report file. Default is
<USER>\AppData\Local\Temp\parasoft\reports(Windows) or<USER>\parasoft\reports(macOS). - Open in browser: Whether the file is automatically opened in a browser.
- Delete on exit: Whether the the report is deleted upon exit.
- Generate reports: Whether a report should be created.
- Publish reports to Team Server: Whether the report should be uploaded to the Team Server (Server Edition only; requires Team Server). To enable this option, Team Server must be properly configured in the Team Server preferences.
- Click OK to to open the report.
Uploading the Report to Team Server
...
- 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). |
...