Product Version Update Information (QTE)

Thank you for using Gaio Technology products.
The following Product Update has taken place.

[Product Name] Quality Town for Embedded grade
[Product Version] R3.1.0.0(R3B)
[Release Date] September 29 2025

*Functional safety [ISO 26262 2nd Edition/IEC 61508] certification planned for March 2026.

• Newly Supported
– The following items have been added to the list of supported QTE operating environments
Host OS: Ubuntu 24.04
Native GCC Compiler: 13.3
Native Clang Compiler: 18.1.3
Google Test：v1.12.0

•Discontinued Support
– Support for the following items in the QTE operating environment has ended
Host OS : Ubuntu 18.04
Native GCC Compiler : 5.4 7.5(we support only for gcc coverage mode)
*Reference: QTE Manual [4.3 Supported operating environment]

– Support for the following baud rates, which are practically unused, has been discontinued
1200 / 1800 / 2400 / 4800 / 9600 / 19200
*Reference: QTE Manual [12.2.4.2.3 Serial communication setting file options list]

• Efficiently Resolve Uncovered Code Coverage through VSCode Integration
– QTE's VSCode integration feature streamlines the task of resolving uncovered code coverage.
You can directly check the logical combinations and execution status of MC/DC within VSCode. An overview of unexecuted test conditions is available in a list, and necessary test cases can be added directly to the Google Test driver on the spot. This provides a consistent workflow, from coding to test result verification and test case addition, all within VSCode.
*Reference: QTE Manual [10. Feature Details(VSCode Integration)]

• Standardization of Configurable Ranges for Target Execution
– The configurable ranges for QTE's target (QNX, Linux) execution have been standardized.
1) Specifying Arguments for Test Execution Binaries
Previously, specifying arguments for test execution binaries using the environment variable "QTE_ARG_TO_TESTBIN" was only applicable to the native environment, but it can now be used in Linux/QNX environments as well. This enables specific tests to be run with GoogleTest.
*Reference: QTE Manual [16.9 Passing Arguments to the Test Run Binary]
2) Specifying Arguments and Communication Intervals for ssh/scp Commands
The functionality to specify options for ssh/scp commands and set communication intervals using environment variables like "QTE_SSH_OPTION" and "QTE_SCP_INTERVAL" was previously limited to the QNX target but is now available for the Linux target as well. This allows options and communication intervals to be set according to the communication environment.
*Reference: QTE Manual [16.6 Specifying options when connecting to the target using SSH/SCP]

• Manual Revisions for Better Understanding of Build Procedures
– Sections 9.6 and 9.7 of the manual have been revised.
1) The descriptions, which were not in chronological order, have been re-written to be sequential.
2) The descriptions and examples of settings have been separated.
3) Explanations for CMake have been added due to previous insufficient coverage.
4) Descriptions unrelated to building have been moved to separate chapters.
– 9.4.12 Code processing library and additional header files for coverage measurement
– 16.14 How to build without using QTE "build" command
*Reference: QTE Manual [9.6 Build system configuration steps] and [9.7 Preparation before test execution]

• Enabling Arbitrary Environment Variables to be Set in the Test Execution Binary Environment
– A new function has been added to set arbitrary environment variables before the test execution binary is run. This addresses situations where the test execution binary needs to reference shared libraries located in a path that isn't included in the system's path, and therefore requires an environment variable like "LD_LIBRARY_PATH" to be set before execution. By setting arbitrary environment variables in the "target-runtime-env-variable-list" option, you can set them before running the test execution binary for each target.
*Reference: QTE Manual [16.8 Setting environment variables during test execution binaries]

• Addition of Functional Safety Coverage Measurement Criteria to the Manual
– A new explanation for functional safety coverage measurement methods has been added to the manual.
*Reference: QTE Manual [14.Appendix-C (Functional Safety Coverage Measurement)]

→「QTE user manual」