How does it work?
Parasoft C/C++test helps teams efficiently understand results from software testing by reporting and analyzing results in multiple ways.
Directly in the developer’s IDE, users can view:
- Static analysis findings (warnings and coding standard violations)
- Unit testing details (passed/failed assertions, exceptions with stack traces, info/debug messages)
- Runtime analysis failures (with allocation stack traces)
- Code coverage details (percentage values, code highlights, including coverage-test case correlation)
- Change impact analysis that demonstrates the indicates which tests have failed or need retesting based on recent code changes.
From Parasoft’s centralized reporting dashboard, users can view all of the above plus the additional:
- Aggregated visual reporting of the entire project status through dynamic dashboards with customizable reporting widgets
- Deep-dive information from each dashboard element
- Granular filtering and advanced analytics
- File and source code access with traces for unit test results and static analysis warning and coding standard violations
- Report generation and compliance evaluation
The Quality Tasks view in the IDE makes it easy for developers to sort and filter the results (i.e. group per file, per rule, per project, etc.). Developers can make annotations directly in the source code editors to correlate issues with the source code, and for better understanding the context of reported issues and how to apply a fix. Code coverage information is presented as visual highlights displaying directing the code editors, together with percentage values (for project, file, and function) in a dedicated Coverage view.
Analysis results for both IDE and command line workflows can also be exported to standard HTML and PDF reports, for local reporting. For safety-critical software development, C/C++test provides an additional dedicated report format that provides details about unit test case configuration and the log of results from test execution, so the user has a complete report of how the test case was constructed and what happened during runtime.
For team collaboration, C/C++test publishes analysis results to a centralized server so developers can access results from automated runs and project managers can quickly assess the quality of the project. Reported results (static analysis findings, metric analysis details, unit testing details, code coverage details, and source code details) are stored with a build identifier, for full traceability between the results and the build.