The following views are available:
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.
This view is open by default. If this view is not available, choose Parasoft> Show View> Coverage to open it.
For details on reviewing coverage, see Reviewing Coverage Information.
The Coverage Advisor view displays pre-conditions required to cover uncovered code lines. To display this view, choose Parasoft> Show View> Coverage Advisor.
See Working with Coverage Advisor for details.
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.
To display this view, choose Parasoft> Show View> Stubs.
For details on this view, see Adding and Modifying Stubs.
This is view is where C/C++test reports test progress and status.
When a test runs, the view label changes from "Test Progress" to "[Test Configuration name]".
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:
The following Scope metrics are reported for all types of tests and analysis:
The Quality Tasks view is where C/C++test lists quality 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 Test Case Explorer helps you manage a project’s test cases, test suites, and related data sources. It provides detailed test statistics and allows you to search/filter the test case tree.
To display this view, choose Parasoft> Show View> Test Case Explorer.
For details on this view, see About the Test Case Explorer.
The Editor view is the largest panel in the workbench. This is where 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.
To create an editor for a file or other test artifact, double-click the related node in the project tree.
If you right-click within a file open in the Editor view, relevant commands will be available in a Parasoft shortcut menu. For Eclipse, Parasoft-specific commands are added to the Show In shortcut menu (for example, Show In> Quality Tasks).
The Suppressions view lists any suppressed static analysis tasks from suppressions that were defined in the GUI (as opposed to suppressions defined directly in the code; those suppressions are not shown in this view).
This view is not open by default. Choose Parasoft> Show View> Suppressions to open it.
For details on using suppressions, see the Static Analysis section in the related product’s user’s guide.
The Console view is where 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.
To display this view, choose Window Show View> General> Console.
The Requirements view displays requirements and test definitions imported from a requirements management system. For details on importing, see Importing Requirements.