Structure of HTML Reports Generated from C/C++ Test Results

Using Polyspace^® Test™, you can export test results to HTML reports for archiving and certification. This topic walks through the structure of HTML reports generated from C/C++ test results.

Organization of Reports

When you generate an HTML report in the user interface, the generated report opens automatically in your default web browser. To open reports outside this context, navigate to the folder where you generated the reports.

The report folder contains the following HTML files:

• index.html — This file contains the test summary report which shows the number of passing suites and tests. Start exploring your test results from this file.

• Suite-specific HTML files including pst_default_suite.html — An HTML file is generated for each test suite that you created. Any test that is not a member of a suite is added to the suite pst_default_suite in the report.

Summary Report

The summary report consists of the following sections:

• Summary – Total number of suites and tests, and the percentage of suites and tests with passing results.

• Product and Version – Information about when the report was generated and the Polyspace Test product version that was used to generate the results and the report.

• Project Information – Project information such as:

  • Path, which states the full path to the project.

  • Created By, which states the author name. For more information, see Author.

  • Create Date, which states the date and time of creation of the project. For more information, see Created.

  • Last Save Date, which states the date and time when the project was last modified and saved. For more information, see Last modified.

• Environment Information – Build-specific information such as:

  • Build Configuration, which states the name of the build configuration used for building the tests.

  • Configuration Description, which states any description you supplied in the build configuration.

  • Toolchain, which states the compilation toolchain used for building the tests. For more information, see Compilation toolchain (Testing).

  • Board, which states the hardware board on which the tests were run.

  Note that the environment information is automatically populated using information in your Polyspace Platform project configuration. If you generate reports without using a Polyspace Platform project, for instance, using the polyspace-code-profiler -report command, you have to explicitly specify this information using the option -add-environment-info.

• Suites Summary – Number of tests and percentage of passing tests per suite.

Report per Suite

The report for each test suite contains these sections:

• Summary — The total number of tests, how many tests passed, and how many completed.

• Tests Summary —The tests in the suite, the number of assessments, and a pass/fail status. If a test fails, the Details column contains information on the number of failures and type of failure. For instance, VerifyFail=1, Exception shows that there is a single verify assessment failure and an exception.

• Details — Details of each test in the suite, including:

  • Status — Whether the test passed, failed or is incomplete.

  • Location — The file and line number of the test.

  • Requirements — Any requirements that are linked to the list (applicable only to graphically authored tests).

  • Failed assessments — The assessments that failed when the test failed. This section does not appear for a passing test.