In this section:

This topic explains how to import results into the IDE from DTP, Team Server or an XML file. Choose Parasoft> Import to specify where you want to import findings from. You can also import findings from the Quality Tasks view menu or use the Import from DTP toolbar button:

Parasoft C/C++test Professional 2021.2 (Visual Studio) > Importing Results into the UI > image2017-4-10 18:1:51.png

Importing Findings from DTP

If C/C++test is connected to DTP, team developers/testers can import test results into their IDEs. If project-wide/team-wide tests are run automatically each night on a central server machine and the results published to DTP (see Generating Reports for information how to send results to DTP), each developer or tester can import his or her assigned findings on their desktop and then review and respond to them in the Quality Tasks view.

Findings from DTP file, are imported according to the Import Settings configuration, see Configuring Import Options.

You need to ensure that:

Connection with your DTP Server is properly configured, see Connecting to DTP
The DTP filter is configured, see Configuring Import Options. If you cannot choose a filter from the filter configuration drop-down menu, verify that you have appropriate access in DTP (see "Project Creation and Configuration" in the DTP documentation for additional information).

To import findings from DTP:

Configure the Import Settings; see Configuring Import Options.
Choose Import> DTP from the Parasoft menu or the Quality Tasks view menu, or select DTP from the Import pull-down toolbar menu.
The import will begin immediately. An alert will tell you how many findings were imported.

The import will begin immediately. When finished, an alert will tell you how many findings were imported. The imported findings will be loaded into the Quality Tasks view.

If the imported findings are associated with a file that has been modified, a message appears specifying the file(s) that are out of sync. The markers associated with these findings (including the line numbers) may not match the location in the local resource files or may indicate findings that have already been resolved.
Findings associated with resources missing locally are not imported and the displayed message lists the files that are unavailable.

Parasoft C/C++test Professional 2021.2 (Visual Studio) > Importing Results into the UI > image2017-4-12 14:3:0.png

Accessing Results through DTP

To access Parasoft DTP reports based on information from C/C++test tests and other sources:

Choose Parasoft> Explore> Report Center Reports or open the reports as described in your DTP User’s Guide.

Importing Findings from a File

To import findings from an XML file:

Configure the Import Settings; see Configuring Import Options.
Choose Import> Local File or URL from the Parasoft menu or the Quality Tasks view menu, or select Local File or URL from the Import pull-down toolbar menu.
Enter the URL of the file or browse for the file when prompted to begin the import.

Importing Tasks from Team Server

Your tasks: The subset of all of your testing tasks that you are responsible for (based on code authorship calculations, which are discussed in Configuring Task Assignment and Code Authorship Settings).
Recommended tasks: The subset of all of your testing tasks that C/C++test has selected for you to review and address today (based on the settings in the executed Test Configurationв’s Goals tab).
Your recommended tasks: The subset of all of your testing tasks that 1) you are responsible for (based on the designated authorship and task assignment settings defined as described in Configuring Task Assignment and Code Authorship Settings) and 2) were selected for you to review and address today (based on the settings in the executed Test Configuration’s Goals tab).

Any team member whose C/C++test installation is connected to Team Server will be able to import the results stored on Team Server. When tasks are imported, test results are shown in the GUI as if the test were run in the GUI. After the import, you can drill down into findings in the normal manner, double-click task messages to open and edit the related line of source code, use any applicable "Quick Fixes" to correct reported problems, and so forth.

You can import a specific category of tasks, tasks for specific goals, or all tasks. You can only import results for projects that are currently in your workbench. If the tested project files were modified in your workbench since the test was run, the results will not be reported because they might not correspond to your modified version of the project files.

To import tasks from Team Server:

Choose Import> Team Server... from the Parasoft menu or the Quality Tasks view menu, or select Team Server... from the Import pull-down toolbar menu.
Specify what type of tasks you want to import. Available options are:
- All/Filtered: Specifies whether you want to import all tasks on Team Server, or only a subset of tasks (tasks that satisfy the criteria specified in the subsequent options).
- For goals: If global goals management (described in Configuring Task Goals) is enabled, this imports tasks related to the selected goal.
- Recommended tasks: Imports only recommended tasks.
- Selected resources: Imports only the set of tasks for the resource selected in the project tree.
- For single user: Imports only tasks for the specified user.
- For session tag: Imports only tasks marked with the specified session tag.
- Task types: Specify the product and results type of the tasks you want to be imported.
Click OK.

Note that the imported results are a static "snapshot" of the results at the time the test completed. They do not reflect changes were made since that test run (e.g., if tasks were reassigned or suppressed). If you want these updates to be propagated across the team, do one of the following:

Rerun the tests to update the results stored on Team Server
Enable the following setting on each connected team machine: Parasoft> Preferences> Quality Tasks> Revalidate tasks' suppressions and reassigns on startup or import.

In determining which tasks to recommend, C/C++test considers:

The severity of the issues reported (more severe violations are given priority).
The time when the file was modified (more recent modifications are given priority because they will be fresh in the developer’s mind).
Whether there are other issues reported for the same file (files with multiple violations are given priority because the developer will need to perform less testing this way — if you made 8 total corrections within 2 files, you would have to test only 2 files, but if you made 8 total corrections within 8 different files, you would have to test 8 files).

When importing results, C/C++test loads the latest report for each session tag and downloads the tasks related to files that are in open projects. The tag is set through the session tag setting — either in Parasoft> Preferences> Reports, or with the session.tag={name} in the local settings. For example, if you run static analysis standards and test execution separately on the same project, results for both runs will be imported as long as they have different session tags. If they have the same tag, only the results from the most recent run will be loaded — even when you choose the All option when importing from Team Server.

Here’s an alternative way to import all tasks:

Choose Parasoft> Explore> Team Server. The Browsing dialog will open.
Open the Reports tab of the Browsing dialog.
Select the XML report whose results you want to import, then click the Import Results button.

By default, C/C++test is configured to import tasks from tests performed within the past 2 days. If your team doesn’t run tests frequently and you try to import tasks more than 2 days after the test has run, nothing will be imported—unless you change the default settings.

To change the default test import settings:

Choose Parasoft> Preferences. The Preferences dialog will open.
In the left pane, select Parasoft> Quality Tasks.
Modify the setting for Import only tasks reported for tests ran in the last n days.

Accessing Team Server Reports through the GUI

Any team member whose C/C++test installation is connected to Team Server will be able to view and download the report files that are available on Team Server.

To download a report file:

Choose Parasoft> Explore> Team Server. The Browsing dialog will open.
Open the Reports tab of the Browsing dialog. Reports will be organized according to the date when they were generated.
Do one of the following:

- To view a report, select the report that you want to view, then click the View button. The report will open in a Web browser.
- To download a report, select the report that you want to download, then click the Download button. A file chooser will open. Specify a location for the downloaded report, then click Save. The report file will then be downloaded to the specified location.

If you want to delete reports stored on Team Server (for example, if you want to clear all old reports from Team Server or remove the report for a failed test run):

Choose Parasoft> Explore> Team Server. The Browsing dialog will open.
Open the Reports tab of the Browsing dialog.
Select the XML report whose results you want to delete, then click the Delete button.

If you want to keep the related test data on Team Server (for example, if you are cleaning out old reports, but you still want data from these tests used for graphs that show historical trends), enable Keep summary data for report graphs.

Accessing Team Server Reports through a Web Browser

Any team member who can access the Team Server’s Web server can directly browse to the report files that are available on Team Server. This allows team members to access reports outside of the C/C++test GUI. Moreover, in the reports available on Team Server, all links (for instance, links to Category) are active. All links are not active in emailed reports.

To directly access a report available on Team Server, choose Parasoft> Explore> Team Server Reports in the C/C++test GUI.