Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space CPPTDESKDEV and version 10.4.2

...

After test execution, C++test generates a prioritized task list , organized by error categories and severities.   For tests run in the GUI, tasks are organized into the following categories in the Quality Tasks view:

...

For tests run from the command line interface, tasks are reported in the Test Generation and Test Execution section of the report. If results were sent to Team Server, you can import results can be imported into the GUI as described in the Importing Results into the UI.  They will then be available in  so that they appear in the Quality Tasks view—as if the tests were run from the GUIview.

Viewing Test Configurations

...

that Trigger Tasks

You can view Test configurations that trigger tasks can be opened from the Quality Tasks view: Right-click by right-clicking on a task in the Quality Tasks view and choose choosing View Test Configuration.

Image Added

Quickly accessing test configuration from the from the Quality Tasks view is useful for group architects who are customizing tests and want to quickly disable settings that aren’t applicable. Developers importing results from a server-based run may also need to open and review test configurations that trigger tasks.

...

To review one of the lines of code referenced in the stack trace, double-click the node that shows the line number, or right-click that the node and choose Go to from the shortcut menu. The editor will then open and highlight the designated line of code.

...

Any test case with reported post conditions can automatically be automatically validated for use in regression testing. Verification changes the *_POST_CONDITION_* macros into assertions that will fail if a subsequent test does not produce the expected (validated) value. This is especially useful for automated generation of  of a regression base for legacy code. For details on verification, see Verifying Test Cases for Regression Testing.

...

Within each category, tasks are organized according to severity to help you identify and focus on the most serious issues.

Tip

Tip

If you want the Quality Tasks view to display the severity of each task, go to the pull-down menu in the Quality Tasks view, then choose Configure Contents and set it to show Severity

...

The Test Case Explorer helps you manage a project’s test cases, test suites, and related data sources. It provides detailed test statistics (executed/passed/failed/skipped) and allows you to search/filter the test case tree.

The By default, the Test Case Explorer is open by default, in the left side of the UI. If it is not available, you can open it by choosing Parasoft> Show View> Test Case Explorer.

For details on the Test Case Explorer, see the Exploring the C++test UI.

Reviewing Test Case Details

To view test case details, enable the Show> Details option from the Test Case Explorer menu. This configures  C++test to report the following additional information  

Image Added

The following information will be displayed in the Test Case Explorer tree:

  • Information about the function tested by a given test case (. This information is collected from the CPPTEST_TEST_CASE_CONTEXT comment). Such comments are always added by comments, which C++test always adds for automatically-generated test cases and test cases created using Test Case Wizard.
  • Information about the test case description (. This information is collected from the CPPTEST_TEST_CASE_DESCRIPTION comment). Such comments can be added by comments, which C++test always adds for automatically-generated test cases (see General tab) and test cases created using Test Case Wizard (see Test Case Configuration Tips).
  • Information about the test execution details. Depending on test configuration (see Runtime tab Execution Tab Settings - Defining How Tests are Executed), this can include:
    • Test case reports / messages
    • Information about reported tasks (e.g., exceptions, failed assertions, unverified outcomes)
    • Information about checked and passed assertionsImage Removed

Opening the Source Code for a Test or Test Suite

To open the source code for a test suite or test case in the Test Case Explorer, right-click its Test Case Explorer node, then choose Open. Or, double-click its Test Case Explorer node.

 

Image Modified

 


Correlating Test Case Explorer Nodes to Quality Tasks View Results

...

To view detailed information about executed data source test cases, enable Show > Data source tests from the Test Case Explorer menu. This will make C++test display information about each executed iteration of the data source test case.

Image Added

The data source test case element of the tree presents statistics information about executed iterations (e.g., number of passed and failed iterations). Statistics shown for all parent nodes of the data source test case also include information about particular data source test case iterations.

 Image Added

Image Removed

Obtaining Traceability Details

There are several ways to create a report containing the maximum amount of unit test execution and traceability information:

Scroll Table Layout
orientationdefault
sortDirectionASC
repeatTableHeadersdefault
widths40%,60%
sortByColumn1
sortEnabledfalse
cellHighlightingtrue

From here...Perform these steps...
Generating test cases automatically
  1. Provide the test case description in the Test
Configuration >
  1. Configuration> Generation> General> Test case description field.
  2. Enable Test Configuration> Generation> Test case> Insert code to report test case inputs and outputs.
Creating test cases using Test Case Wizard
  1. Provide a test case description.
  2. Enable Insert code to report test case inputs and outputs.
Executing tests
  1. Enable Test Configuration> Execution> Runtime> Report unit test execution details.
  2. Enable Test Configuration> Execution> Runtime> Include tasks details.
  3. Enable Test Configuration> Execution> Runtime> Include passed assertions details.
Generating reports
  1. Enable Parasoft> Preferences> Reports > Overview of checked files and executed tests.
  2. Choose HTML (C++test's Unit Testing details) as the Report format.
Generating reports from the command line
  1. Set the report.contexts_details=true option in the localsettings file to enable the Executed Test Cases section.
  2. Set the report.format=html_ut_details option in the localsettings file to set up the report format.

Traceability Reporting Tips

  • To report additional messages from test cases, use  test case report macros (see Test Case Report Macros).
  • For data source test cases, reported messages might be read from the data source. For example,
    CPPTEST_REPORT_CSTR("Requirement number", CPPTEST_DS_GET_CSTR("req_no"))
  • If a test case description or test case message contains valid URLs (e.g. http:// or ftp://), they will be added into the generated HTML report as links.

 


 


Responding to Reported Tasks

Different types of findings require different response strategies. The following table lists the categories used to classify C++test’s test execution findings, and links to sections that will help you understand and respond to them.

Scroll Table Layout
sortDirectionASC
repeatTableHeadersdefault
widths33%,33%,34%
sortByColumn1
sortEnabledfalse
cellHighlightingtrue

CategorySubcategoryDescription and Recommended Response
Fix Unit Test ProblemsAssertion FailuresSee Assertion Failures and Timeouts
Runtime ExceptionsSee Runtime Exceptions
Review Unit Test OutcomesUnverified OutcomesSee Unverified Outcomes

Anchor
quick_fix
quick_fix
Using Quick Fix (R) to Respond to Test Execution Findings

...

  1. Select the problems you want to apply the action to.
  2. Right-click the selection, then choose the command for the desired response (for example, Verify All Outcomes).

Generating Test Execution Details Reports

The Test Execution Details report is an additional report you can generate from your regular report. It contains details about the following information:

  • about tested files
  • toolchain used for building test harnesses
  • additional configuration files
  • test suites
  • test cases (including Test Case Definition and Test Case Execution Log sections)

 See Generating the Test Execution Details Report for details.