Test Execution in Polyspace Platform User Interface

Configure project, build tests, check tests for run-time errors, run tests

You can build and run tests in a Polyspace Platform project, after setting appropriate options in your project.

If you encounter errors during the build, you can resolve them by using error messages in the build logs. You can also run a quick test validation before building your project.
If you encounter errors during test execution, you can run static analysis on your tests to make sure that your test data does not lead to run-time errors.

Polyspace Options

`Source code language (-lang)`	Specify language of source files
`C standard version (-c-version)`	Specify C language standard followed in source code
`C++ standard version (-cpp-version)`	Specify C++ language standard followed in source code
`Compilation toolchain (Testing)`	Specify the compiler that you use to build your source code and tests for dynamic testing

`Preprocessor definitions (-D)`	Replace macros in preprocessed code
`Disabled preprocessor definitions (-U)`	Undefine macros in preprocessed code
`Implicit C(C++) compiler defines`	View implicit compiler defines extracted from your build command (Since R2024b)
`Extra C flags`	Specify C compilation flags required for building project (Since R2023b)
`Extra C++ flags`	Specify C++ compilation flags required for building project (Since R2023b)

`Include paths (-I)`	Specify paths to folders containing include files
`Additional include paths (-I)`	Specify build-specific include paths in addition to project-wide include paths (Since R2024a)
`Implicit C(C++) compiler include paths`	View implicit compiler include paths extracted from your build command (Since R2024b)
`Forced includes (-include)`	Specify files to be #include-d by every source file. (Since R2023b)

`Library paths`	Specify folders containing precompiled libraries for building tests (Since R2023b)
`Libraries`	Specify precompiled libraries for building tests (Since R2023b)
`Extra flags for linking`	Specify linker flags required for building project (Since R2023b)

`Processor`	Select the processor for the current build configuration
`Enable portable word sizes`	Allow compilation of code on host computer while retaining word sizes of target processor on which code is intended to run (Since R2023b)
`Pack alignment value (-pack-alignment-value)`	Specify default structure packing alignment for code developed in Visual C++

`Check undefined symbols`	Specify whether to check for undefined symbols (Since R2023b)
`External symbols`	Specify symbol names that are not defined in code (Since R2023b)

Artifacts directory Specify folder for storing project artifacts such as generated test code and build information (Since R2025a)

Polyspace Platform Settings	Settings for Polyspace Platform user interface (Since R2023b)
Toolchain	Create, validate, and register a custom toolchain for building C/C++ sources and tests

Configure Project for Testing in Polyspace Platform User Interface
Specify targets and build information to build and run tests.
Specify C/C++ Compilers for Testing in Polyspace Platform User Interface
Specify a supported compiler for initial code analysis and test building.

Build and Run Tests in Polyspace Platform User Interface
Validate tests, compile sources and tests into executables, run test executables.
Check for Bugs and Run-Time Errors in C/C++ Tests and Functions Under Test
Using Polyspace^® Bug Finder™ or Polyspace Code Prover™, check for undefined behavior that might make test results suspect.
Difference Between Code Prover Analysis of Tests and Full Code Prover Analysis
A Code Prover analysis of tests analyzes the function under test only with respect to test inputs.