Review Code Profiling Results
After test execution with code profiling enabled, you can review code profiling results in the Polyspace Platform user interface. The results consist of one of these metrics:
Code coverage — How much of your code is covered by existing tests.
Code execution time — The time each function takes to execute.
Memory use — Stack memory used by each function.
Code sanitizer results – Run-time errors during test execution.
For instance, if you computed code coverage with respect to existing tests, you can see a summary of coverage results on a dashboard or drill down to coverage of files, functions, decisions, and conditions in a list view. You can justify missing coverage manually or use other mechanisms such as coverage filters or unreachable code information.
Polyspace Results
Statement Coverage | Percentage of statements that current test cases cover (Since R2023b) |
Condition Coverage | Percentage of condition outcomes that current test cases evaluate (Since R2023b) |
Decision Coverage | Percentage of decision outcomes that current test cases cover (Since R2023b) |
Modified Condition/Decision Coverage (MCDC) Coverage | Percentage of conditions that current test cases evaluate for independent impact on outcome (Since R2023b) |
Cyclomatic Complexity | Number of linearly independent paths in function body (Since R2023b) |
Relational Boundary Coverage | Percentage of relational operations that are tested by current test cases (Since R2023b) |
Function Coverage | Percentage of unique functions that current test cases execute at least once (Since R2023b) |
Function Call Coverage | Percentage of function calls that current test cases execute at least once (Since R2023b) |
Function Exit Coverage | Percentage of function exit points that current test cases reach (Since R2023b) |
Execution Time | Measures execution time and number of calls for various callable entities of your code (Since R2023b) |
Memory Use | Measures stack memory usage of various callable entities of your code (Since R2023b) |
Tools
| Polyspace Platform Settings | Settings for Polyspace Platform user interface (Since R2023b) |
Topics
Open Results
- Open Polyspace Results in Polyspace Platform User Interface
See all the ways you can open Polyspace® results.
Review Code Coverage Results
- Review C/C++ Code Coverage Results in Polyspace Platform User Interface
Review condition, decision, MC/DC, and other coverage metrics in Polyspace Platform user interface or Polyspace Access™ web interface. - Improve or Justify Missing Code Coverage Results
After reviewing code coverage results, either add tests or justify the missing coverage.
- Compare Code Coverage Results After Adding New xUnit API-Based Tests
After adding new Polyspace Test™ xUnit API based tests, assess the impact of the changes by comparing the coverage results. - Structure of HTML Reports Generated from C/C++ Code Profiling Results
Code profiling reports in HTML format contain a summary of code profiling, along with detailed breakdown per file and function.
Review Execution Time Results
- Review and Address Execution Time Results
After calculating the execution time of your code, review the results and address bottlenecks in execution time. - Structure of HTML Reports Generated from C/C++ Code Profiling Results
Code profiling reports in HTML format contain a summary of code profiling, along with detailed breakdown per file and function.
Review Memory Use Results
- Review and Address Memory Use Results
After calculating the stack memory use of your code, review the results and address possible stack overflow. - Structure of HTML Reports Generated from C/C++ Code Profiling Results
Code profiling reports in HTML format contain a summary of code profiling, along with detailed breakdown per file and function.
Review Code Sanitizer Results
- Run C/C++ Code Sanitizer and Review Results in Polyspace Platform User Interface
Enable code sanitizer, view sanitizer results as test failures or in sanitizer profiling report. - Issues Detected Using Polyspace Test Code Sanitizer
Find out which issues can be detected at runtime when executing tests with code sanitizer enabled. - Structure of HTML Reports Generated from C/C++ Code Sanitizer Results
Code sanitization reports in HTML format contain a summary of code profiling, along with detailed breakdown per file, function and flagged expression.
Polyspace Access Workflows
- Upload Results to Polyspace Access
Upload analysis results from the Desktop or Server products. - Create Bug Tracking Tool Tickets from the Polyspace Access Web Interface (Polyspace Access)
Track findings with Jira software or Redmine from the Polyspace Access interface.