QTE(Quality Town for Embedded grade)
 The next generation of Unit Test tools for C++ and Open Platforms

  • Target Industries : Automobile industry
  • Target Category : Embedded Software Development Division
  • Standard : ISO 26262 / IEC 61508
HOME ＞ Embedded Software Development and Verification tools ＞ QTE(Quality Town for Embedded grade)
QTE(Quality Town for Embedded grade)

The next generation of Unit Test tools for C++ and Open Platforms

QTE(Quality Town for Embedded grade) is a Unit Test tool designed for the AUTOSAR Adaptive Platform. It supports environments such as C++, Host-Linux, Target-Linux, and Open Source Software (OSS).

Performing Automotive Quality testing efficiently with Google Test resources

Automotive Quality testing can be performed by applying Google Test resources such as AUTOSAR AP C++ Source Code to QTE. QTE can use these resoures to measure Coverage (C0/C1/MCDC/Function/Function Call) of the Target Object as required by Functional Safety Standard ISO26262. Test evidence and reports are created automatically, leading to even greater improvements in efficiency.
  • Feature 1
    Efficiently bring your OSS Test Tool resources into compliance with Functional Safety Standards
    Automotive Software for Automated Driving/Centralized Electronic Control Units must be compatible with recent trends towards increased program size and complexity. Open Source development platforms are becoming the norm, and Continuous Integration is becoming more and more popular. However, performing Functional Safety testing on Open Source platforms poses problems, and leads to increased workload to carry out Automotive Quality testing. QTE is a tool that enables OSS Test Tool resources to be efficiently brought into line with Functional Safety standards.

  • Feature 2
    Even inexperienced users can implement Automotive Quality testing!
    More and more Enterprise Software (Non-Embedded) engineers are becoming involved in the development of Automotive Software for Automated Driving/Centralized Electronic Control Units. Automotive Quality testing is a new and difficult challenge for Non-Embedded software engineers, leading to an increase in the workload required to perform such testing. QTE allows engineers without experience of Automotive Quality Test development to perform such testing with less workload and burden.
Function
  • Function 01

    Non-Embedded Software engineers can also perform tests easily

    • Two test modes and coverage features are provided to match the testing process

      When testing with QTE, Native test mode uses PC-Native code and Target test mode uses the Target Microcontroller Code. Test design and coverage measurement can be performed at high speed with the Native test mode, while Functional Safety testing is done using the Target test mode, thus allowing greater efficiency. Coverage can also be done using the "GCC Coverage" or "Functional Safety Coverage" features, depending on the type of testing being done to give the greatest efficiency for the entire process.
  • Function 02

    Testing is possible on all data types for C++ Templates.

    • Included Coverage Measurement feature which is difficult for OSS Tools

      Most OSS tools measure coverage for each Template class when a C++ Template is used. Automotive Quality requires that Object-Level coverage be performed, but when a Template is used, multiple executable Objects may be created for each type, so even if coverage is measured for each class, Object Level coverage is incomplete. With QTE, coverage can be measured for each type of Template so the coverage measurement is more complete than for OSS tools.
  • Function 03

    Enhanced reporting capabilities

    • Reports can be generated for each stakeholder in agile/scrum development

      With the release of V1.2, we have included a report function that integrates test results from multiple workspaces. Previously, the results of tests performed by each team had to be integrated and checked separately, but this feature now allows the user to efficiently check the progress of the entire final product source code.
  • Function 04

    Supports various target test execution environments

    • Available in POSIX-OS/OS-less target environment

      QTE can run tests using cross-compiler generated MPU target objects. Actual devices (evaluation board or real product hardware) or microcomputer simulators can be used as the target environment.
      QTE supports QNX, and general-purpose embedded Linux as target environments with POSIX-OS such as AUTOSAR-AP. Furthermore it can be used on targets that do not have POSIX-OS such as AUTOSAR-CP, and OS-less (bare metal) target environments.

Main features

PC Native Execution Mode Executes tests on PC-Native code.
Target Execution Mode Executes tests on Target CPU Object Code.
GCC Coverage Feature Using the GCC option, deliver basic results in a shorter time. (No code analysis.)
Functional Safety Coverage Feature Analyses the source code, and provide detailed coverage measurement results suited to Functional Safety requirements.
Impact Confirmation Feature Compare the results of two different tests, to confirm the impact of changes made to improve coverage.
Test Results Reporting Output the results of the tests performed in a project.
Automatic Overall Report Creation Feature Create an overall report on a project.

Product Catalogues