This topic explains installation and basic setup instructions for the C++test plugin into QNX Momentics. In this section:
Use the Eclipse plug-in mechanism to integrate C++test into your QNX Momentics IDE. A link file will be added to the following location:
<QNX Installation Root>/QNX Momentics/com.parasoft.xtest.cpptest.link.
The link file contains the path to the C++test plugin, which informs the QNX Momentics IDE that the plug-in should be loaded at startup. After installation, a dedicated C++test perspective will be added in Workbench. C++test views will also be added to the C/C++ perspective.
During the installation process, C++test attempt to create a link file in the following QNX Momentics IDE’s embedded Eclipse location:
<QNX Installation Root>/QNX Momentics/com.parasoft.xtest.cpptest.link
The link will contain the path to the C++test installation directory. This is the only change that the C++test installation makes inside the QNX Software Development platform distribution.
Launch the QNX Momentics IDE (with the C++test plugin installed) as you normally would.
Use the Control Panel’s Add or Remove Program functionality to uninstall the C++test QNX Momentics IDE plug-in. Alternatively, you can run the Windows C++test installation executable and enable the Remove option.
You cannot uninstall the C++test plug-in by removing the <QNX Installation Root>/QNX Momentics
/com.parasoft.xtest.cpptest.link
link file. If you remove the file, you will still need to manually remove the C++test installation. The Windows registry’s Install Shield information will still remain.
You can run the C++test plug-in using a local (machine-locked) license or a network license served from Parasoft DTP or from a standalone instance of Parasoft License Server. See Licensing for details on how to configure the license.
In order to perform static analysis or unit testing, C++test must collect the following information from your QNX project:
The information is collected from the QNX Momentics IDE project structure description by scanning make files.
qcc <options> <file>
options_scanner <options> qcc <options> <file>
After the build process is completed, C++test will have all the necessary data collected.
Before you start testing, ensure that the project’s compiler/linker options source is correctly set. In most cases, C++test automatically detects the necessary settings. The compiler/linker flags source settings are specified in the Build Settings screen. To access the build settings:
The following configuration options are available:
Choose a strategy for collecting compiler/linker switches from the drop-down menu.
For testing of QNX projects directly, choose Use Options from QNX build system. The C++test options extractor is designed to scan QNX make files. The compiler/linker executable name, compiler/linker command lines, and the system environment used to start the compilation/linking process are scanned. All these settings are later used during the C++test analysis.
The Compiler settings area lets you specify the compiler set/tools used for compiling the project's sources and building the test executable. Settings include:
Specify any additional compiler or linker options you want to include, as well as the location of the runtime library.
DPARASOFT_CPPTEST
is added to the compiler options by default. You can add any additional options after that. ${cpptest:original_options}
variable can be used to access the original project options.Also see Specifying Options in the C++test Project or File Options Panel.
Before you start static analysis, verify that the appropriate compiler settings are used in the Project Properties panel's Parasoft> C++test> Build Settings area. In most cases, it is best to set the Options source as Use Options from QNX build system. After confirming that compiler settings are correct, you can start the analysis.
For general information on performing static analysis with C++test, see Static Code Analysis and Flow Analysis. |
This section covers both Unit Testing and Application Monitoring.
For embedded testing, the C++test runtime library must be cross-compiled for the chosen platform before you can perform unit testing. The built-in "Run QNX Momentics Tests" Test Configuration does this building automatically.
If you need to build C++test runtime library manually, follow the instructions in Working with the C++test Runtime Library — using QNX_5.mk
as the target configuration.
C++test provides a Test Configuration template designed specifically for testing QNX Projects. This Test Configuration is in Builtin> Embedded Systems> QNX> Run QNX Momentics Tests. It covers all steps required for full unit testing of QNX Projects:
This Test Configuration is only a template; it needs to be customized to reflect your remote QNX system configuration as follows:
This test configuration is based on rcp (allow remote copy) and rsh (allow remote shell execution) tools available in Windows. The remote QNX system needs to be configured to allow remote calls from rcp and rsh. It is also possible to modify test execution flow and use different tools instead of rcp and rsh.
Use Eclipse Internal debugging mode. For more details see:
For general information on generating and executing unit test cases with C++test, Test Creation and Execution. |
C++test provides a Test Configuration template designed especially for running a QNX application with memory monitoring: Builtin> Embedded Systems> QNX> Build and Run Application with Memory Monitoring for QNX Momentics. This Test Configuration provides all steps required for running QNX application monitoring, including:
This Test Configuration is only a template; it needs to be customized to reflect your remote QNX system configuration. To customize it:
This Test Configuration is based on scp (allow remote copy) and rsh (allow remote shell execution) tools available in Windows. The remote QNX system needs to be configured to allow remote calls from rcp and rsh. It is also possible to modify test execution flow and use different tools in place of rcp and rsh.
For general information on performing application monitoring and runtime error detection with C++test, see Runtime Error Detection. |