Home
QNX Momentics IDE User's Guide
This User's Guide describes version 8.0 of the Integrated Development Environment (IDE) that's part of the QNX Tool Suite.
Unit Testing
The IDE lets you use commercial test frameworks to write unit tests and then execute them by launching a project. While running a test program, you can use the Code Coverage tool to determine how much of the code is exercised (covered) by your tests.
Exporting Code Coverage results
Sometimes, it's useful to view coverage data outside of the IDE. The Code Coverage export feature lets you generate a report that contains the data of a coverage session and that can be viewed in a browser.

QNX Momentics IDE User's Guide
This User's Guide describes version 8.0 of the Integrated Development Environment (IDE) that's part of the QNX Tool Suite.
- Working with QNX Momentics IDE
  QNX Momentics IDE provides a graphical environment for developing, running, debugging, and profiling applications.
- Developing Projects with the IDE
  To use the QNX Momentics IDE to write applications targeted for QNX OS systems, you must define projects, which are containers that store your source code, configuration files, and binary files.
- Debugging Applications
  The IDE allows you to debug a running application, a library used by the application, or a core file.
- Unit Testing
  The IDE lets you use commercial test frameworks to write unit tests and then execute them by launching a project. While running a test program, you can use the Code Coverage tool to determine how much of the code is exercised (covered) by your tests.
  - Writing and building test programs
    The test frameworks supported by the IDE let you write programs in C++ that test C or C++ code. Here, we explain the QNX project setup required to write a test program using the GoogleTest (GTest) Framework. For the other frameworks, you should read their online documentation to learn the coding and building steps needed to write test programs.
  - Running test programs
    You can launch a unit test program on the target and the IDE will display the results of individual tests in a dedicated view as the program runs.
  - Measuring code coverage
    You can build and configure projects in the IDE to collect and display code coverage measurements as the program runs.
  - Importing Code Coverage results
    If you have coverage data generated outside of the IDE, you can import that data and view the results.
  - Exporting Code Coverage results
    Sometimes, it's useful to view coverage data outside of the IDE. The Code Coverage export feature lets you generate a report that contains the data of a coverage session and that can be viewed in a browser.
- Analyzing Memory Usage and Finding Memory Problems
  QNX Momentics IDE lets you run Memory Analysis and several Valgrind (pronounced val-grinned) tools to find memory problems such as leaks and corruption, and to measure memory usage of programs. It also provides the QNX System Information perspective so you can learn which processes are consuming memory or other resources excessively.
- Analyzing Performance
  QNX Momentics IDE works with the Application Profiler and Valgrind (pronounced val-grinned) Cachegrind tools, which measure the performance of programs running on QNX targets. It also offers the QNX System Information perspective for viewing performance-related metrics.
- Analyzing System Behavior
  Many IDE tools allow you to find errors and optimize applications, but to ensure that your embedded system behaves well, you need to use system-wide diagnostic tools. The QNX System Information and QNX System Profiler tools help you understand process and thread interaction on the target, reduce application and system startup times, and debug deadlock and improper CPU usage levels.
- Building QNX OS Images
  Using the IDE's QNX System Builder feature, you can generate OS images, which are bootable images that contain startup code, the QNX OS, your applications, and any data files used by your applications. The IDE supports image building by allowing you to transfer an image to a target board.
- Reference
  The reference topics provide information about QNX Momentics IDE features and workflows that isn't covered in the chapters related to developing projects or debugging, testing, and analyzing applications.
- JTAG: Debugging with Lauterbach TRACE32
  The Lauterbach TRACE32® In-Circuit Debugger (TRACE32-ICD) supports the JTAG onchip interface so you can perform hardware debugging of QNX OS systems through the QNX Momentics IDE.
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running the QNX OS 8.0.
QNX Software in the Cloud
QNX Software in the Cloud enables developers to use the QNX OS in the Amazon cloud environment.
QNX Toolkit for Visual Studio Code
This User's Guide describes the QNX^® Toolkit for Visual Studio Code. The guide introduces you to the QNX Toolkit by explaining the QNX development environment and how to build, run, and debug your QNX^® Operating System (OS) applications and systems.
QNX Hypervisor User's Guide
This User's Guide explains the QNX hypervisor architecture and provides instructions for installing and running a QNX Hypervisor system, changing system components and configuration, and using hypervisor features such as virtual devices (vdevs).
Typographical Conventions, Support, and Licensing
This section describes the typographical conventions used throughout the documentation, explains how to obtain technical support, and provides some information about licensing.

Exporting Code Coverage results

QNX Tool SuiteIntegrated Development Environment User's GuideDeveloperSetup

Sometimes, it's useful to view coverage data outside of the IDE. The Code Coverage export feature lets you generate a report that contains the data of a coverage session and that can be viewed in a browser.

In this release, there is no longer an action for saving session data to an XML file. Instead, you can export the results from a session into HTML files.

To export Code Coverage results:

In the Analysis Sessions view, right-click the session for which you want to save the results.
The session can still be in progress—in this case, the IDE just outputs the results gathered so far.
Select Export Session from the context menu.
In the Save Coverage Report window, specify the path for saving the report as well as the name of the root file.

For convenience, the IDE fills in a default path for saving the report. This path is a subdirectory within the project directory and is named project_name___GCC_Code_Coverage_. The root file (by default, index.html) contains the report summary.

You can set other report generation properties, as explained in How to set report properties.

The IDE exports the Code Coverage results into a new report and opens the root file in the default web browser. The report lets you see coverage measurements from the entire program to each source file and function, as explained in How to read reports.

Page updated: March 05, 2025