This topic describes the preconfigured "built-in" Test Configurations that are included with C++test.
C++test includes a set of preconfigured "built-in" Test Configurations representing most common test scenarios. You can further customize these configurations as needed by copying and modifying the built-in configurations, or by creating new user-defined configurations from scratch. User-defined Test Configurations can be placed in the User-defined or Team category. User-defined Test Configurations are stored on the local machine and are available for all tests performed by the local C++test installation. Team Test Configurations are stored on the team’s Team Server and can be accessed by all team members.
Static Analysis Group
This group includes universal static analysis test configurations. See Compliance Packs for test configurations that enforce coding standards
| Test Configuration | Description |
|---|---|
| Recommended Rules | The default configuration of recommended rules. Covers most Severity 1 and Severity 2 rules. Includes rules in the Flow Analysis Fast configuration. |
| Flow Analysis Standard | Detects complex runtime errors without requiring test cases or application execution. Defects detected include using uninitialized or invalid memory, null pointer dereferencing, array and buffer overflows, division by zero, memory and resource leaks, and dead code. This requires a special Flow Analysis license option. See Introducing Built-in Flow Analysis Test Configurations for more details on Flow Analysis Test Configurations. |
| Flow Analysis Fast | The fast configuration uses "Shallowest" depth of analysis and runs faster than the standard and aggressive configurations. The fast configuration finds a moderate amount of problems and prevents violation number explosion. See Introducing Built-in Flow Analysis Test Configurations for more details on Flow Analysis Test Configurations. |
| Flow Analysis Aggressive | The aggressive option reports any suspicious code as a violation. See Introducing Built-in Flow Analysis Test Configurations for more details on Flow Analysis Test Configurations. |
| Effective C++ | Checks rules from Scott Meyers’ "Effective C++" book. These rules check the efficiency of C++ programs. |
| Effective STL | Checks rules from Scott Meyers’ "Effective STL" book. |
| Modern C++ (11, 14 and 17) | Checks rules that enforce best practices for modern C++ standards (C++11, C++14, C++17). |
| Find Duplicated Code | Detects duplicated functions, code fragments, string literals, and #include directives. |
| Find Unused Code | Includes rules for identifying unused/dead code. |
| Metrics | Reports metrics statistics and detects metric values out of acceptable ranges. |
| Global Analysis | Checks the Global Static Analysis rules. |
| Sutter-Alexandrescu | Checks rules based on the book "C++ Coding Standards," by Herb Sutter and Andrei Alexandrescu. |
| The Power of Ten | Checks rules based on Gerard J. Holzmann’s article "The Power of Ten - Rules for Developing Safety Critical Code." (http://spinroot.com/gerard/pdf/Power_of_Ten.pdf) |
Compliance Packs
Compliance Packs include test configurations tailored for particular compliance domains to help you enforce industry-specific compliance standards and practices.
Aerospace Pack
| Test Configuration | Description |
|---|---|
| Joint Strike Fighter | Checks rules that enforce the Joint Strike Fighter (JSF) program coding standards. |
| DO178C Software Level A Unit Testing | Executes unit tests with appropriate configuration of coverage metrics and reporting settings for DO178C Software Level A |
| DO178C Software Level B Unit Testing | Executes unit tests with appropriate configuration of coverage metrics and reporting settings for DO178C Software Level B |
| DO178C Software Level C and D Unit Testing | Executes unit tests with appropriate configuration of coverage metrics and reporting settings for DO178C Software Level C and D |
Automotive Pack
| Test Configuration | Description |
|---|---|
| AUTOSAR C++14 Coding Guidelines | Checks rules that enforce the AUTOSAR C++ Coding Guidelines (Adaptive Platform, version 17-10).
|
| High Integrity C++ | Checks rules that enforce the High Integrity C++ Coding Standard. |
| HIS Source Code Metrics | Checks metrics required by the Herstellerinitiative Software (HIS) group. |
| MISRA C 1998 | Checks rules that enforce the MISRA C coding standards. |
| MISRA C 2004 | Checks rules that enforce the MISRA C 2004 coding standards. |
| MISRA C++ 2008 | Checks rules that enforce the MISRA C++ 2008 coding standards. |
| MISRA C 2012 | Checks rules that enforce the MISRA C 2012 coding standards.
|
| ISO26262 ASIL A Unit Testing | Executes unit tests with appropriate configuration of coverage metrics and reporting settings for ISO26262 ASIL A |
| ISO26262 ASIL B and C Unit Testing | Executes unit tests with appropriate configuration of coverage metrics and reporting settings for ISO26262 ASIL B and C |
| ISO26262 ASIL D Unit Testing | Executes unit tests with appropriate configuration of coverage metrics and reporting settings for ISO26262 ASIL D |
This test configuration is part of Parasoft Compliance Pack solution that allows you to monitor compliance with industry standards using the "Compliance" extensions on DTP. It requires dedicated license features to be activated. Contact your Parasoft representative for details.Medical Devices Pack
| Test Configuration | Description |
|---|---|
| Recommended Rules for FDA (C) | Checks rules recommended for complying with the FDA General Principles for Software Validation (test configuration for the C language). |
| Recommended Rules for FDA (C++) | Checks rules recommended for complying with the FDA General Principles for Software Validation (test configuration for the C++ language). |
Security Pack
| Test Configuration | Description |
|---|---|
| CWE-SANS Top 25 Most Dangerous Programming Errors | Checks for the 2011 CWE/SANS Top 25 Most Dangerous Software Errors— a list of the most widespread and critical errors that can lead to serious vulnerabilities in software. They are often easy to find, and easy to exploit. They are dangerous because they will frequently allow attackers to completely take over the software, steal data, or prevent the software from working at all. (http://cwe.mitre.org/top25/index.html) For more details, see 2011 CWE/SANS Top 25 Most Dangerous Software Errors Mapping. |
| OWASP Top 10 2017 | Includes rules that find issues identified in OWASP’s Top 10 standard. |
| Payment Card Industry Data Security Standard | Checks rules for the security issues referenced in section 6 of the Payment Card Industry Data Security Standard (PCI DSS) (https://www.pcisecuritystandards.org/security_standards/pci_dss.shtml) Issues detected include input validation (to prevent cross-site scripting, injection flaws, malicious file execution, etc.) and validation of proper error handling. |
| Security Rules | Checks rules designed to prevent or identify security vulnerabilities. |
| SEI CERT C Coding Guidelines | Checks rules and recommendations for the SEI CERT C Coding Standard. This standard provides guidelines for secure coding. The goal is to facilitate the development of safe, reliable, and secure systems by, for example, eliminating undefined behaviors that can lead to undefined program behaviors and exploitable vulnerabilities. |
| SEI CERT C Rules | Checks rules for the SEI CERT C Coding Standard. This standard provides guidelines for secure coding. The goal is to facilitate the development of safe, reliable, and secure systems by, for example, eliminating undefined behaviors that can lead to undefined program behaviors and exploitable vulnerabilities.
|
| SEI CERT C++ Rules | Checks rules for the SEI CERT C++ Coding Standard. This standard provides guidelines for secure coding. The goal is to facilitate the development of safe, reliable, and secure systems by, for example, eliminating undefined behaviors that can lead to undefined program behaviors and exploitable vulnerabilities.
|
| UL 2900 | Includes rules that find issues identified in the UL-2900 standard. |
Unit Testing Group
| Test Configuration | Description |
|---|---|
| File Scope> Build Test Executable (File Scope) | Builds test executable for "trial builds." Only the selected file(s) will be instrumented. |
| File Scope> Collect Stub Information (File Scope) | Collects symbols data to populate the Stubs view. Only the selected file(s) will be instrumented. |
| File Scope> Debug Unit Tests (File Scope) | Executes unit tests under the debugger. Only the selected file(s) will be instrumented. |
| File Scope> Generate Stubs (File Scope) | Generates stubs for missing function and variable definitions. Only the selected file(s) will be instrumented. |
| File Scope> Run Unit Tests | Executes the available test cases. Only the selected file(s) will be instrumented. |
| Build Test Executable | Builds test executable for "trial builds." All project files will be instrumented. |
| Collect Stub Information | Collects symbols data to populate the Stubs view. All project files will be instrumented. |
| Debug Unit Tests | Executes unit tests under the debugger. All project files will be instrumented. |
| Generate Regression Base | Generates a baseline test suite that captures the project code’s current functionality; to detect changes from this baseline, you run your evolving code base against this test suite on a regular basis. Outcomes are automatically verified. |
| Generate Stubs | Generates stubs for missing function and variable definitions. All project files will be instrumented. |
| Generate Test Suites | Generates test suites (without generating test cases) for the selected resources. |
| Generate Unit Tests | Generates unit tests for the selected resources. |
| Run Unit Tests | Executes the available test cases. All project files will be instrumented. |
| Run Unit Tests with Memory Monitoring | Executes the available test cases and collects information about memory problems. All project files will be instrumented. |
Application Monitoring Group
| Test Configuration | Description |
|---|---|
| Build Application with Coverage Monitoring | Builds the tested application with coverage monitoring enabled. |
| Build Application with Full Monitoring | Builds the tested application with coverage and memory monitoring enabled. |
| Build Application with Memory Monitoring | Builds the tested application with memory monitoring enabled. |
| Build and Run Application with Coverage Monitoring | Builds and executes the tested application with coverage monitoring enabled. |
| Build and Run Application with Full Monitoring | Builds and executes the tested application with coverage and memory monitoring enabled. |
| Build and Run Application with Memory Monitoring | Builds and executes the tested application with memory monitoring enabled. |
Embedded Systems Group
| Test Configuration | Description |
|---|---|
| ARM > Run ADS 1.2 Application with Memory Monitoring | Builds and executes the tested application on the AXD Debugger with coverage and memory monitoring enabled. |
| ARM > Run ADS 1.2 Tests | Builds and executes unit tests using the AXD Debugger and collects results. |
| ARM > Run ARM Embedded Linux Application with Memory Monitoring | Builds and executes tested applications on ARM Embedded Linux systems (on real target devices or simulators) with coverage and memory monitoring enabled. Test execution results are saved on the target machine file system and are copied to the host using the scp command. |
| ARM > Run ARM Embedded Linux Test Executable | Builds and executes unit tests using the SSH protocol (on real target devices or simulators). Test execution results are saved on the target machine file system and are copied to the host using the scp command. |
| ARM > Run DS-5 2.2 Application with Memory Monitoring | Builds and executes the tested application on the DS-5 Debugger with coverage and memory monitoring enabled. |
| ARM > Run DS-5 2.2 Tests | Builds and executes unit tests using the DS-5 Debugger and collects results. |
| ARM > Run DS-5 3.x 4.x Application with Memory Monitoring | Builds and executes the tested application on the DS-5 Debugger with coverage and memory monitoring enabled. It generates a temporary debugger script with information about how the test binary should be started and starts the debugger with the generated script. You may need to customize the debugger connection name that is passed to the debugger script via the "Target connection configuration" test flow property. |
| ARM > Run DS-5 3.x 4.x Tests | Builds and executes unit tests using the DS-5 Debugger and collects results. It generates a temporary debugger script with information about how the test binary should be started and starts the debugger with the generated script. You may need to customize the debugger connection name that is passed to the debugger script via the "Target connection configuration" test flow property, |
| Arm > Run DS-5 Application with Memory Monitoring (Software Model) | Builds and executes the tested application on the Software Model simulator. With coverage and memory monitoring enabled. You may select the name (executable) of the Model. |
| Arm > Run DS-5 Test Executable (Software Model) | Builds and executes unit test using the Software Model simulator. You may select the name (executable) of the Model. |
| Altium> Run Altium TASKING CTC Application with Mem Monitoring | Builds and executes the tested application using the TASKING standalone debugger (dbgtc) on the TriCore instruction set simulator. Coverage and memory monitoring is enabled. Results from test execution on the simulator are saved on the host machine file system. |
| Altium> Run Altium TASKING CTC Application with Mem Monitoring - CrossView | Builds and executes the tested application using the TASKING Cross View Pro debugger (by default on the TriCore instruction set simulator). Coverage and memory monitoring is enabled. Results from test execution on the simulator are saved on the host machine file system. |
| Altium> Run Altium TASKING CTC Tests | Builds and executes the unit tests using the TASKING standalone debugger (dbgtc) on the TriCore instruction set simulator. Results from test execution on the simulator are saved on the host machine file system. |
| Altium> Run Altium TASKING CTC Tests - CrossView | Builds and executes the unit tests using the TASKING Cross View Pro debugger (by default on the TriCore instruction set simulator). Results from test execution on the simulator are saved on the host machine file system. |
| Spansion> Build and Run Application with Memory Monitoring for Spansion FR Softune - Simulator | Builds and runs the Softune application on the simulator with memory monitoring enabled. Results from test execution are saved on the host machine file system. |
| Spansion> Run Spansion FR Softune Tests - Simulator | Builds and executes unit tests using the Softune debugger on the simulator. Results from test execution are saved on the host machine file system. |
| Green Hills Software> Run GHS Tests | An all-in-one configuration for GHS MULTI Embedded that builds the test binary, launches it, and reads the runtime logs. |
| Green Hills Software> Run GHS Application with Mem Monitoring | An all-in-one configuration for GHS MULTI Embedded that builds the test binary in application mode with memory monitoring enabled, launches it, and reads the runtime logs. |
| Green Hills Software> Run GHS Tests with Assembly Coverage Monitoring | An all-in-one configuration for GHS MULTI Embedded that builds the test binary, launches it, and reads the runtime logs. Assembly coverage is collected in addition to unit tests results |
| IAR Systems> Run IAR ARM Application with Mem Monitoring | An all-in-one configuration that builds the test binary in application mode with memory monitoring enabled, launches it, and reads the runtime logs. Uses manual simulator configuration. |
| IAR Systems> Run IAR ARM Tests | An all-in-one configuration that builds the test binary, launches it, and reads the runtime logs. Uses manual simulator configuration. |
| IAR Systems> Run IAR EW Application with Mem Monitoring (Batch Template) | An all-in-one configuration that builds the test binary in application mode with memory monitoring enabled, launches it, and reads the runtime logs. Uses EW-generated batch scripts. |
| IAR Systems> Run IAR EW Tests (Batch Template) | An all-in-one configuration that builds the test binary, launches it, and reads the runtime logs. Uses EW-generated batch scripts. |
| IAR Systems> Run IAR MSP430 Application with Mem Monitoring | An all-in-one configuration that builds the test binary in application mode with memory monitoring enabled, launches it, and reads the runtime logs. Uses manual simulator configuration. |
| IAR Systems> Run IAR MSP430 Tests | An all-in-one configuration that builds the test binary, launches it, and reads the runtime logs. Uses manual simulator configuration. |
| IAR Systems > Run IAR RX Application with Mem Monitoring | An all-in-one configuration that builds the test binary in application mode with memory monitoring enabled, launches it and reads the runtime logs. Uses manual simulator configuration. |
| IAR Systems > Run IAR RX Tests | An all-in-one configuration that builds the test binary, launches it and reads the runtime logs. Uses manual simulator configuration. |
| Keil uVision > Run Keil uVision Tests - ULINK2 (UART) | Builds and executes unit tests using the uVision Debugger and collects results via the RS232 connection. Serial port listener is used to capture the results transmission. You may need to customize the serial connection parameters |
| Keil uVision > Run Keil uVision Tests - ULINKPro or Simulator (ITM) | Builds and executes unit tests using the uVision Debugger and collects results via the ITM based communication channel. |
| Keil uVision > Run Keil uVision Tests - Simulator (UART) | Builds and executes unit tests using the uVision Debugger and simulator. Results are collected and sent via the simulated UART. You may need to customize the serial connection parameters |
| Keil uVision > Run Keil uVision Application with Memory Monitoring - ULINK2 (UART) | Builds and executes the tested application using the uVision Debugger with coverage and memory monitoring enabled. Results are collected via the RS232 connection. Serial port listener is used to capture the results transmission. You may need to customize the serial connection parameters |
| Keil uVision > Run Keil uVision Application with Memory Monitoring - ULINKPro or Simulator (ITM) | Builds and executes the tested application using the uVision Debugger with coverage and memory monitoring enabled. Results are collected via the ITM-based communication channel. |
| Lauterbach Trace32 > Run Application with Memory Monitoring using Trace32 (FDX) | Builds and executes the tested application using the Lauterbach Trace32 debugger. Coverage and memory monitoring is enabled. Results from test execution are saved on the host machine file system (sent via the FDX protocol). By default, the debugger is set to work with the TriCore TC1796 processor. |
| Lauterbach Trace32 > Run Tests using Trace32 (FDX) | Builds and executes the unit tests using the Lauterbach Trace32 debugger. Results from test execution are saved on the host machine file system (sent via the FDX protocol). By default, the debugger is set to work with the TriCore TC1796 processor. |
| QNX > Build and Run Application with Memory Monitoring for QNX Momentics | Builds and executes the tested application on a remote QNX system. You need to customize the remote system properties (remote host, user name and test directory). Communication with the remote system is based on rsh and rcp tools. |
| QNX > Run QNX Momentics Tests | Builds and executes unit tests on a remote QNX system. You need to customize the remote system properties (remote host, user name and test directory). Communication with the remote system is based on rsh and rcp tools. |
| Renesas HEW> Run HEW 4.x Tests (simulated IO) | Builds and executes the unit tests using the HEW debugger on the SH simulator. Results from test execution on the simulator are saved on the host machine file system. |
| Renesas HEW> Run HEW 4.x Application with Mem Monitoring (simulated IO) | Builds and executes the tested application using the HEW debugger on the SH simulator. Coverage and memory monitoring is enabled. Results from test execution on the simulator are saved on the host machine file system. |
| Texas Instruments > Run TI CCS 3.x Application with Memory Monitoring | Builds and executes the tested application in the Code Composer Debugger with coverage and memory monitoring enabled. You may need to customize the target configuration name that is used to initialize the connection with CCS Debugger via the "Target name" test flow property |
| Texas Instruments > Run TI CCS 3.x Tests | Builds and executes unit tests using the Code Composer Debugger and collects results. You may need to customize the target configuration name that is used to initialize the connection with CCS Debugger via the "Target name" test flow property. |
| Texas Instruments > Run TI CCS 4.x Application with Memory Monitoring | Builds and executes the tested application in the Code Composer Debugger with coverage and memory monitoring enabled. It will automatically detect the CCS project's active target configuration. |
| Texas Instruments > Run TI CCS 4.x Tests | Builds and executes unit tests using the Code Composer Debugger and collects results. It will automatically detect the CCS project's active target configuration. |
| Wind River> Tornado> Build VxWorks Test Object (PassFS) | Builds a test object that uses the Pass-through File System for storing results. This includes generating and reading static coverage data (if enabled), but not launching the test object or reading any dynamic data. |
| Wind River> Tornado> Build VxWorks Test Object (Socket) | Builds a test object that uses Sockets for transferring and storing results. This includes generating and reading static coverage data (if enabled), but not launching the test object or reading any dynamic data. |
| Wind River> Tornado> Build VxWorks Test Object (TSFS) | Builds a test object that uses the Target Server File System. This includes generating and reading static coverage data (if enabled), but not launching the test object or reading any dynamic data. |
| Wind River> Tornado> Load and Run VxWorks Test Object | Launches your test object using the Wind River Shell. Use with PassFS and TSFS build configurations. |
| Wind River> Tornado> Load and Run VxWorks Test Object (Socket) | Launches the socket listener and then your test binary using the Wind River Shell. Use with the Socket build configuration. |
Wind River> Tornado> Run VxWorks Application with Mem Monitoring (PassFS) | An all-in-one configuration that builds the test binary in application mode with memory monitoring enabled, launches it, and reads the runtime logs. |
| Wind River> Tornado> Run VxWorks Unit Tests (PassFS) | An all-in-one configuration that builds the test object, launches it and reads the runtime logs. |
Wind River> Workbench 3.x> Build VxWorks Test Executable - RTP (PassFS) | Used to prepare a test binary in the form of a Real Time Process executable file. PassFS will be used to store test results. |
| Wind River> Workbench 3.x> Build VxWorks Test Executable - RTP (Socket) | Used to prepare a test binary in the form of a Real Time Process executable file. TCP/IP sockets will be used to send test results. |
| Wind River> Workbench 3.x> Build VxWorks Test Executable - RTP (TSFS) | Used to prepare a test binary in form of Real Time Process executable file. TSFS will be used to store test results. |
| Wind River> Workbench 3.x> Build VxWorks Test Module - DKM (PassFS) | Builds the test binary in the form of a downloadable kernel module, including ctdt.c file generation. When testing with C++test, you may need to exclude the original cdtd.c file from the build to avoid conflicts between the original build ctdt.c and the C++test-generated one. PassFS will be used to store test results. |
| Wind River> Workbench 3.x> Load and Run VxWorks Test Executable (RTP) | Runs the test binary on VxSim. |
| Wind River> Workbench 3.x> Load and Run VxWorks Test Object (DKM) | Runs the test binary on VxSim. |
| Wind River> Workbench 3.x> Run VxWorks Application with Mem Monitoring - DKM (PassFS) | An all-in-one configuration that builds the test binary in the form of a Downloadable Kernel Module in application mode with memory monitoring enabled, launches it and reads the runtime logs. PassFS is used to store test results. |
| Wind River> Workbench 3.x> Run VxWorks Application with Mem Monitoring - DKM (TSFS) | An all-in-one configuration that builds the test binary in the form of a Downloadable Kernel Module in application mode with memory monitoring enabled, launches it, and reads the runtime logs. TSFS is used to store test results. |
| Wind River> Workbench 3.x> Run VxWorks Application with Mem Monitoring - RTP (PassFS) | An all-in-one configuration that builds the test binary in the form of a Real Time Process in application mode with memory monitoring enabled, launches it, and reads the runtime logs. PassFS is used to store test results. |
| Wind River> Workbench 3.x> Run VxWorks Application with Mem Monitoring - RTP (TSFS) | An all-in-one configuration that builds the test binary in the form of a Real Time Process in application mode with memory monitoring enabled, launches it, and reads the runtime logs. TSFS is used to store test results. |
| Wind River> Workbench 4.x> Run VxWorks DKM Application with Full Monitoring (File System, WRWB 4.x) | An all-in-one configuration for WRWB 4.x that builds the test binary in the form of a Downloadable Kernel Module in application mode, loads the binary into the target, runs the test binary, unloads the binary from the target, and collects coverage and runtime monitoring results. |
| Wind River> Workbench 4.x>Run VxWorks DKM Unit Tests (File System, WRWB 4.x) | An all-in-one configuration for WRWB 4.x that builds the test binary in the form of a Downloadable Kernel Module, loads the binary into the target, executes unit tests, unloads the binary from the target, and collects coverage and test results. |
| Wind River> Workbench 4.x> Run VxWorks RTP Application with Full Monitoring (File System, WRWB 4.x) | An all-in-one configuration for WRWB 4.x that builds the test binary in the form of a Real Time Process in application mode, loads the binary into the target, runs the test binary, unloads the binary from the target, and collects coverage and runtime monitoring results. |
| Wind River> Workbench 4.x> Run VxWorks RTP Unit Tests (File System, WRWB 4.x) | An all-in-one configuration for WRWB 4.x that builds the test binary in the form of a Real Time Process, loads the binary into the target, executes unit tests, unloads the binary from the target, and collects coverage and test results. |
| Wind River> Extract Symbols from VxWorks Image | Extracts symbols from a selected VxWorks image. The extracted symbols should be used when testing DKM projects with test configurations from the Wind River> Workbench 3.x group. |
| Windows Mobile> Build Test Executable for Windows Mobile | Builds a test executable that you need to manually transfer to the target device and run. This Test Configuration is very similar to the "Build Test Executable" Test Configuration; the only difference is that it is configured to use an external storage card to generate post-run artifacts (coverage and results). |
| Windows Mobile> Build and Run Application with Memory Monitoring for Pocket PC | Builds the application, deploys it to the emulator and runs it with memory monitoring enabled. After execution completes, you need to close the emulator to prompt C++test to read and display test results. |
| Window Mobile> Build and Run Test Executable for Pocket PC | Builds the test executable, deploys it to the emulator and runs it with memory monitoring enabled. After execution completes, you need to close the emulator to prompt C++test to read and display test results. |
| Window Mobile> Build and Run Test Executable with Memory Montoring for Smartphone | Builds the test executable, deploys it to the emulator and runs it with memory monitoring enabled. After execution completes, you need to close the emulator to prompt C++test to read and display test results. |
| Window Mobile, Windows CE> Build and Run Test Executable for Pocket PC | Builds the test executable, then deploys it to the emulator and runs it. After execution completes, you need to close the emulator to prompt C++test to read and display test results. |
| Window Mobile> Build and Run Test Executable with for Smartphone | Builds the test executable, deploys it to the emulator and runs it. After execution completes, you need to close the emulator to prompt |
| Window Mobile, Windows CE>Build and Run Application with Memory Monitoring for WMobile or Windows CE (ActiveSync) | Builds the applicaiton, then deploys it to the emulator and runs it with memory monitoring enabled. ActiveSync is used as a communication channel. To use this flow, both host and target machines must support ActiveSync. The target can be a real device connected in ways supported by ActiveSync, or it can be an emulator. |
Window Mobile, Windows CE>Build and Run Test Executable for Windows Mobile or Windows CE | Builds the test executable, then deploys it to the emulator and runs it. ActiveSync is used as a communication channel. To use this flow, both host and target machines must support ActiveSync. The target can be a real device connected in ways supported by ActiveSync, or it can be an emulator. |
| Build Test Executable - Generic Embedded System |
Utilities Group
| Test Configuration | Description |
|---|---|
| Load Test Results (File) | Used to collect test results via the file channel. By default, this configuration assumes that logs are located inside |
| Load Test Results (Sockets) | Used for "on the fly" collection of test results sent through TCP/IP sockets. It starts a java utility program to listen to and capture test results. You can customize the port numbers for test and coverage results. Port numbers are defined with the results_port and coverage_port properties. |
| Extract Library Symbols | Used to extract a list of symbols from external libraries (or object files). It should be used whenever C++test’s standard algorithm for collecting information about symbols from binaries is not sufficient. For example if you use a Wind River DKM type of project, you may want to have all symbols from the VxWorks image collected in this way. You will probably need to enter the location of the binaries you want to extract symbols from, as well as the name of the nm-like utility that can be used to dump the content of library/object file. |
| Generate Stubs Using External Library Symbols | Used to generate stubs after the "Extract Library Symbols" Test Configuration has been run. It assumes that a file with a list of symbols from external libraries is stored in the project temporary data. |
Code Review Group
| Name | Scope | Code Review |
|---|---|---|
| Pre-Commit | Only files added or modified locally | For teams who want to review code before it is committed to source control. To use this Test Configuration, the Code Review Preference Show user assistant during scanner run setting must be enabled so that the author can designate the appropriate reviewer(s). See the Code Review for details. |
| Post-Commit | All project files modified in the previous day | For teams who want to review code after it is committed to source control. This Test Configuration must be duplicated and customized prior to use (e.g, to specify author-reviewer mappings). See Code Review for details. |
See Configuring Test Configurations and Rules for Policies to learn how to develop custom Test Configurations that are tailored to your projects and team priorities.
2011 CWE/SANS Top 25 Most Dangerous Software Errors Mapping
| CWE ID | CWE Name | Parasoft ID | Parasoft Name |
|---|---|---|---|
| CWE-89 | Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') | BD-SECURITY-TDSQL | Protect against SQL injection |
| CWE-78 | Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') | BD-SECURITY-TDCMD | Protect against command injection |
| CWE-120 | Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') | BD-PB-OVERFFM | Avoid buffer overflow due to defining incorrect format limits |
| BD-PB-OVERFNZT | Avoid overflow due to reading a not zero terminated string | ||
| BD-PB-OVERFWR | Avoid overflow when writing to a buffer | ||
| BD-SECURITY-OVERFWR | Avoid buffer write overflow from tainted data | ||
| CWE-22 | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') | BD-SECURITY-TDFNAMES | Protect against file name injection |
| CWE-676 | Use of Potentially Dangerous Function | PB-37 | The unbounded functions of library shall not be used |
| SECURITY-11 | Avoid using unsecured shell functions that may be affected by shell metacharacters | ||
| SECURITY-12 | Avoid using unsafe string functions which may cause buffer overflows | ||
| SECURITY-13 | Avoid using unsafe string functions that do not check bounds | ||
| SECURITY-14 | Do not use scanf and fscanf functions without specifying variable size in format string | ||
| SECURITY-16 | Never use gets() | ||
| SECURITY-22 | Do not use mbstowcs() function | ||
| SECURITY-30 | Avoid using 'getpw' function in program code | ||
| SECURITY-31 | Do not use 'cuserid' function | ||
| CWE-327 | Use of a Broken or Risky Cryptographic Algorithm | SECURITY-02 | Avoid functions which use random numbers from standard C library |
| SECURITY-28 | Standard random number generators should not be used to generate randomness for security reasons | ||
| SECURITY-37 | Do not use weak encryption functions | ||
| CWE-131 | Incorrect Calculation of Buffer Size | BD-PB-ARRAY | Avoid accessing arrays out of bounds |
| BD-PB-OVERFRD | Avoid overflow when reading from a buffer | ||
| BD-SECURITY-ARRAY | Avoid tainted data in array indexes | ||
| MRM-45 | Do not use sizeof operator on pointer type to specify the size of the memory to be allocated via 'malloc', 'calloc' or 'realloc' function | ||
| CWE-134 | Uncontrolled Format String | SECURITY-05 | Avoid using functions printf/wprintf with only one variable parameter |
| SECURITY-08 | Avoid using functions fprintf/fwprintf with only two parameters, when second parameter is a variable | ||
| CWE-190 | Integer Overflow or Wraparound | BD-SECURITY-INTOVERF | Protect against integer overflow/underflow from tainted data |
| MISRA-051 | Evaluation of constant unsigned integer expressions should not lead to wrap-around |
