The following views are standard across all Parasoft Test productsavailable:
|Table of Contents|
The C/C++ Projects view is typically on the left hand side of the workbench (GUI). It lists the available projects and elements related to those projects. You will use the C/C++ Projects view to indicate which resource or set of resources you want C/C++test to operate on.
In this guide, the C/C++ Projects view is also referred to as "the project tree."
This view is shown by default.
The Coverage view reports the amount of coverage obtained for the selected resource during the most recent test case execution.
For details on reviewing coverage, see Reviewing Coverage Information.
The Metrics view lets you review the metrics calculated for the selected project resource.
This view is not open by default. Choose Parasoft> Show View> Metrics to open it.
For details on reviewing metrics calculations, see Reviewing and Responding to Metrics Measurements.
The Stubs view provides details on the stub configuration based on the most recent run of a unit testing Test Configuration. It allows you to modify the configuration by adding user-defined stubs or automatically generating stubs for missing symbols.
Test Progress view
This is view is where Parasoft Test C/C++test reports test progress and status.
The Review tasks button displays the results in the Quality Tasks view.
A results summary for each analysis category is available in expandable sections.
The toolbar buttons allow you to enable you to:
- Enable Debug mode for pausing at breakpoints—Jtest and dotTEST only
- Generate reports (see Generating Reports)
- Show/hide details (including information on any setup problems related to building, compilation, etc.).
The following Scope metrics are reported for all types of tests and analysis:
The Quality Tasks view is where Parasoft Test C/C++test lists quality tasks and code review tasks. You can determine which type of task is displayed by clicking the appropriate button in the view’s toolbar or by choosing it from the view’s drop-down menu, as shown below.
To learn about the general strategies for reviewing the results reported in this view, see Reviewing Results. For details about exploring product-specific results (e.g., special right-click menu commands, more details about what details are presented for various results categories, etc.), see the related product’s user’s guide.
The Editor view is the largest panel in the workbench. This is where Parasoft Test C/C++test displays the source files and test files which you open for editing. In some cases, it also provides editors for configuring tools, test cases, objects, etc.
For details on using suppressions, see the Static Analysis section in the related product’s user’s guide.
Tasks Explorer view
If you do not have Mylyn, the Tasks Explorer view allows you to find, work with, and manage Concerto Report Center tasks directly in your IDE. If Myln is installed, you can perform these tasks in Mylyn.
This view is not open by default. Choose Parasoft> Show View> Tasks Explorer to open it.
For details on Tasks Explorer, see “Project Task Management”, page 260.
Task Assistant view
Once a Parasoft Concerto Project Center task is activated, the Task Assistant view tracks data related to that task (e.g., to compile a list of modified resources related to the given task).
This view is not open by default. Choose Parasoft> Show View> Task Assistant to open it.
For details on Task Assistant, see Connecting Concerto and Report Center and “Project Task Management”, page 260.
Code Review Issue view
The Code Review Issue view allows team members to add and review code comments about the submitted code modifications. This allows the author and reviewer to have a conversation about how to revise a submitted revision. To access this view, choose Parasoft> Show View> Code Review Issue.
The Console view is where Parasoft Test C/C++test lists the output of the entire test process. It displays details such as the process command lines, output, test case details, and logs. Test execution details are reported to the Console tab during test execution, and remain there until they are cleared or until another test is run.