Polyspace Test

 

Polyspace Test

Develop, manage, and execute tests for C and C++ code in embedded systems

Have questions? Contact sales.

Polyspace Test provides tools for developing, managing, and executing unit and integration tests for C and C++ code in embedded systems. You can create tests with the Polyspace xUnit API or graphical test authoring editor and stubs or mocks to isolate and verify code under test. Polyspace Test lets you execute tests on host computers or embedded targets, automate test execution, and link tests to requirements for traceability.

You can perform code coverage analysis to measure test completeness with metrics such as decision, condition, and modified condition/decision coverage (MC/DC). You can use automatic test generation to achieve desired code coverage, test boundary values, and extend requirements-based test cases.

Polyspace Test includes a common user interface that enables you to configure, run, and review results from Polyspace static analysis tools. You can use those results to justify missing code coverage and verify robustness of tests.

Support for industry standards is available through IEC Certification Kit (for ISO 26262 and IEC 61508) and DO Qualification Kit (for DO-178).

Polyspace dashboard summarizing static code analysis results, test status, and code coverage metrics.
Screen showing the addition of a test parameter using the graphical editor.

Develop and Execute Unit and Integration Tests

Develop and run tests for C and C++ code using the Polyspace Test xUnit API or interactively using a graphical test authoring editor. Create stubs and mocks to isolate components under test and integrate with third-party mocking libraries such as gMock.

Documentation

Table showing code coverage results for reachable and unreachable code alongside source code.

Measure Code Coverage and Profile Execution

Generate and review code coverage for industry standard metrics, including decision, condition, and MC/DC. Run tests with code execution profiling to identify code sections that require memory and run-time performance improvements.

Documentation

Dialog for linking a test to a software requirement.

Link Tests to Software Requirements

Link C and C++ tests in the user interface to test requirements authored in an external editor or tool such as IBM® DOORS®, IBM DOORS Next, Microsoft® Word, or Microsoft Excel®.

Documentation

Polyspace dashboard with test execution summary and detailed results.

Run Tests on Host Computers and Target Hardware

Execute tests, collect code coverage metrics, and profile memory and execution on both host and target hardware.

Documentation

Dialog showing options to generate tests for coverage or boundary values.

Generate Tests to Meet Coverage and Boundary Value Objectives

Automatically generate tests to augment manually created test cases and address incomplete code coverage and boundary value testing.

Documentation

Colored shapes labeled ISO 26262, DO-178, EC 61508, IEC 62304, ISO 25119, EN 50128, and EN 50657.

Certification Support

Create artifacts needed to complete certification processes for industry standards. Polyspace Test has been certified by TÜV SÜD for use with IEC 61508 and ISO 26262 standards. Use reports and artifacts for DO-178C processes.

Documentation

Cyclical workflow diagram for DevOps showing development activities (plan, design, build, test) linked with operations activities (deploy, operate, monitor) via continuous integration and continuous delivery.

Automate and Integrate into DevOps

Support modern software development practices by plugging Polyspace Test into existing DevOps workflows and automated processes. Polyspace Test works with popular continuous integration tools, including Jenkins and Bamboo®.

Documentation

Menus to run both dynamic tests and static code analysis.

Centrally Manage Static Analysis and Dynamic Testing

Configure, run, and view results of Polyspace Bug Finder, Polyspace Code Prover, and Polyspace Test from a common user interface.

Documentation

User interface showing analysis results from Polyspace Code Prover being used to justify missing coverage.

Use Static Analysis to Complement Dynamic Testing

Justify missing coverage for code proven unreachable by Polyspace Code Prover. Ensure the reliability and consistency of tests by analyzing them to find defects and run-time errors.

Documentation

Product Resources:

Documentation Examples Videos Requirements Release notes

Interested in Polyspace Test?

Request a trial Request a quote

Have Questions?

Contact the Polyspace Test technical team.