News
- 2025/03/10
- NEWS
Product Version Update Information (QTE)
Thank you for using Gaio Technology products.
The following Product Update has taken place.
The following Product Update has taken place.
Update Information
[Product Name] Quality Town for Embedded grade
[Product Version] R3.0.0.0 (R3A)
[Release Date] March 10 2025
*Functional Safety Standard [ISO 26262 2nd Edition / IEC 61508] Compliance Validation is scheduled for August 2025.
[Product Version] R3.0.0.0 (R3A)
[Release Date] March 10 2025
*Functional Safety Standard [ISO 26262 2nd Edition / IEC 61508] Compliance Validation is scheduled for August 2025.
Update Contents
Change to Supported Environments
• Added Support
– The following items are now supported by QTE
Host OS: Ubuntu 22.04
Native GCC Compiler: 11.4
Native Clang Compiler: 14.0.0
ARM GCC : 9.3.0 (32bit and 64bit)
Target OS : QNX SDP 8.0
Google Test：1.7.0
•Discontinued Support
– The following items are no longer supported by QTE
Host OS : Ubuntu 16.04
Native GCC Compiler : 5.4
– The following items are now supported by QTE
Host OS: Ubuntu 22.04
Native GCC Compiler: 11.4
Native Clang Compiler: 14.0.0
ARM GCC : 9.3.0 (32bit and 64bit)
Target OS : QNX SDP 8.0
Google Test：1.7.0
•Discontinued Support
– The following items are no longer supported by QTE
Host OS : Ubuntu 16.04
Native GCC Compiler : 5.4
Functional Improvements
• Added the ability to measure coverage for multiple combined functions executed in a multi-threaded environment.
– Added the ability to measure coverage for each function during integration tests that are run in multithreads.
• Added a function to detect "C++ syntax that cannot be measured by QTE" that corresponds to QTE restrictions and display an error/warning.
– We have added a function to detect when the source code to be tested contains "C++ constructs that cannot be measured with QTE," which corresponds to a QTE restriction, and display an error/warning.
• Improved the stability of serial communication when using "GTest target execution NonPOSIX/ArmClang option".
– When running tests in a NonPOSIX target environment, we have enhanced the functionality for checking whether serial communication packets have arrived and for detecting errors.
• Enabled the use of QTE-specific environment variables in the option "rcpt-dir-path" when used in non-POSIX environments.
– The option "rcpt-dir-path" (comm_serial.json), which specifies the directory path where the host PC receives test execution results from the target, has been improved so that QTE-specific environment variables can be used when running tests in a NonPOSIX target environment.
• Enabled the use of wildcards in the options "user-include-dir-list" and "system-include-dir-list".
– The build configuration file "build.json" now supports the use of wildcards in the options "user-include-dir-list" and "system-include-dir-list".
• Improvements made to prevent errors caused by insufficient JAVA heap memory when generating HTML test reports.
– The option "report_java_max_heap_size" has been added to "qte.conf" to specify the maximum size of JAVA heap memory.
• Added the ability for users to specify the JRE version on which QTE runs.
– The option "java_command_path" has been added to "qte.conf" to set the Java command path.
• Improved useability by changing the log directory name to "QTE_CA".
– The log directory name generated by QTE has been changed to "QTE_CA". Previously, the log directory name was "CA", but it was pointed out that it could be mistaken for some microcontroller names, so the naming rule was changed.
• Improved so that only Google Test execution results can be output to the HTML test report when coverage is not measured.
– We have improved the system so that if you set the execution mode (option "execution-mode") to "99" and run the program without measuring coverage, an HTML test report containing only the Google Test results will be generated without generating an error.
– Added the ability to measure coverage for each function during integration tests that are run in multithreads.
• Added a function to detect "C++ syntax that cannot be measured by QTE" that corresponds to QTE restrictions and display an error/warning.
– We have added a function to detect when the source code to be tested contains "C++ constructs that cannot be measured with QTE," which corresponds to a QTE restriction, and display an error/warning.
• Improved the stability of serial communication when using "GTest target execution NonPOSIX/ArmClang option".
– When running tests in a NonPOSIX target environment, we have enhanced the functionality for checking whether serial communication packets have arrived and for detecting errors.
• Enabled the use of QTE-specific environment variables in the option "rcpt-dir-path" when used in non-POSIX environments.
– The option "rcpt-dir-path" (comm_serial.json), which specifies the directory path where the host PC receives test execution results from the target, has been improved so that QTE-specific environment variables can be used when running tests in a NonPOSIX target environment.
• Enabled the use of wildcards in the options "user-include-dir-list" and "system-include-dir-list".
– The build configuration file "build.json" now supports the use of wildcards in the options "user-include-dir-list" and "system-include-dir-list".
• Improvements made to prevent errors caused by insufficient JAVA heap memory when generating HTML test reports.
– The option "report_java_max_heap_size" has been added to "qte.conf" to specify the maximum size of JAVA heap memory.
• Added the ability for users to specify the JRE version on which QTE runs.
– The option "java_command_path" has been added to "qte.conf" to set the Java command path.
• Improved useability by changing the log directory name to "QTE_CA".
– The log directory name generated by QTE has been changed to "QTE_CA". Previously, the log directory name was "CA", but it was pointed out that it could be mistaken for some microcontroller names, so the naming rule was changed.
• Improved so that only Google Test execution results can be output to the HTML test report when coverage is not measured.
– We have improved the system so that if you set the execution mode (option "execution-mode") to "99" and run the program without measuring coverage, an HTML test report containing only the Google Test results will be generated without generating an error.
Changes to the method of providing user manuals and support information
• Changed the method of providing the QTE user manual from a PDF file to an online web page
– Starting with this version, the way the QTE user manual is provided has been changed from the conventional PDF file to an online web page.
→「QTE user manual」
• The QTE restrictions web page has been abolished and integrated into the online manual page and bug information web page.
– Starting with this version, we have changed the way we provide QTE restriction information. The QTE restriction information web page that was previously provided separately from the user manual has been discontinued and has been consolidated into the online manual.
– Starting with this version, the way the QTE user manual is provided has been changed from the conventional PDF file to an online web page.
→「QTE user manual」
• The QTE restrictions web page has been abolished and integrated into the online manual page and bug information web page.
– Starting with this version, we have changed the way we provide QTE restriction information. The QTE restriction information web page that was previously provided separately from the user manual has been discontinued and has been consolidated into the online manual.
