QTE(Quality Town for Embedded grade)
 Next-generation testing tools for modern-style development

  • Target Industries : Automotive/Robotics/FA/medical and other industries
  • Target Category : Embedded Software Development Department
  • Standard : ISO 26262 / IEC 61508 tool certification

HOME ＞ Embedded Software Development and Verification tools ＞ QTE(Quality Town for Embedded grade)
Problem

Challenges for in-vehicle software aiming for
modern-style development

  • Unlike conventional edge control, software has become large-scale, increasing testing man-hours and development resources.
  • Struggling to create the best tool environment for modern-style development.
  • OSS (Open Source Software) tools have difficulty in achieving functional safety (ISO 26262) requirements. They have issues with quality, test man-hours, functional safety certification, etc.
Solution

Next generation testing tool for modern-style development
QTE (Quality Town for Embedded grade) is the solution
to your challenges.

Our product "QTE" is a high-quality testing tool for embedded software aimed at modern development.

Features of QTE

Testing tool for reasonably priced functional safety compliance with modern-style development

QTE can fulfill the missing elements in Google Test and meet the requirements for functional safety certification.

Seamlessly leverage Google Test assets from advanced development to volume development

By introducing QTE, the transition from advanced development to mass production development will be seamless, significantly reducing man-hours and costs.
  • Feature 1
    Obtained functional safety standards
    We have obtained tool certification for ISO 26262 (TCL1 to TCL3) and IEC 61508 from TÜV SÜD, a third-party certification organization.
  • Feature 2
    Cloud environment available
    QTE is available in a Cloud environment that allows for a rapid development environment. By utilizing containers and K8S, QTE provides a flexible and scalable development environment.
  • Feature 3
    Efficiently transfer OSS test tool assets to functional safety standards
    In recent years, software has been developed in a continuous integration style, based on open source software (OSS) development platforms in order to accommodate the increasing scale and complexity of software. However, the general OSS environment makes it difficult to conduct functional safety level testing, leading to an increase in man-hours required to conduct in-vehicle quality testing. QTE can efficiently adapt assets from Google test, an OSS testing tool, to meet functional safety standards.
  • Feature 4
    In-vehicle quality testing can be easily performed even by inexperienced embedded engineers.
    For non-embedded engineers, conducting in-vehicle quality testing is challenging due to the use of tools specific to in-vehicle software, resulting in increased test execution man-hours. QTE makes it easier for inexperienced engineers to conduct in-vehicle quality testing.
Functions of QTE
  • Function 01

    Two execution modes to suit your testing process

    • Non-embedded engineers can also efficiently conduct testing

      QTE offers two test execution modes: Native execution mode, which executes as PC-Native code, and Target execution mode, which executes microcontroller target code. Efficient test execution is possible for each test process by using PC-Native execution mode for high-speed test design and code coverage measurement, and using Target execution mode when functional safety level test execution is required.
  • Function 02

    Code coverage measurement functionality

    • Two types of coverage functions, GCC Coverage Function and Functional Safety Coverage Function, are provided.

      As with the test execution mode, they can be used in different ways according to the test process to achieve efficient test execution.

      The Functional Safety Coverage function measures statement coverage (C0), branch coverage (C1), MC/DC coverage, function coverage, and function call coverage.
  • Function 03

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

    • Measurement of execution coverage of multiple objects for Template

      In-vehicle quality testing requires object-level execution coverage, but Template generates multiple execution objects for each type from a single source, so even if code coverage is measured for each class, it does not cover all execution objects.
      QTE enables code coverage measurement for each Template type, which is not possible with OSS tools.
  • Function 04

    Supports a variety of target test execution environments

    • POSIX-OS equipped, available in OS-less target environment

      Tests can be executed using MPU target objects generated by the cross-compiler. The target environment can be an actual device (evaluation board or real product hardware) or a microcontroller simulator.
      In addition, QNX and embedded Linux are supported as target environments with POSIX-OS. In addition, targets without POSIX-OS or OS-less (bare-metal) target environments can also be used.
  • Function 05

    Generate reports for each stakeholder in Agile/Scrum development

    • Enhanced reporting functions

      Equipped with a report function that integrates test results.
      Previously, it was necessary to separately integrate and check the test results conducted by each team, but with this function, it is now possible to efficiently check the progress management of the entire final product source code.
  • Function 06

    Support for distributed/parallel test operations

    • Merges multiple code coverage results and reports comprehensive results

      Code coverage results from multiple Google Test drivers can be merged, making it easy to understand the code coverage rate and unexecuted test coverage for the each team or the entire product.

      Enables flexible test execution planning and work sharing
      Tests can be distributed and parallelized to reduce test execution time. In addition, it is also possible to augment and supplement the unexecuted portions of tests with additional testing in other projects.
  • Function 07

    Provides QTE reference workflow (safety manual)

    • The reference workflow explains the specific use of QTE to develop safety-related software compliant with the base standards IEC 61508 and ISO 26262.

      The workflows for unit and integration testing in relation to the content of ISO 26262 Part 6 (product development at software level), how to create test cases using Google Test, as well as how to evaluate test results and analyze structural coverage are explained in detail. The book also provides detailed information on how to evaluate test results and perform structural coverage analysis.

Main features

PC-Native execution mode PC-Native code is used for test execution
Target execution mode Test execution using objects on the actual machine
GCC Coverage Function Quick and simple code coverage measurement (no source analysis required) using GCC's proprietary functions
Functional Safety Coverage Function Analyzes source code and outputs highly accurate code coverage measurement results that are compatible with functional safety.
Code coverage can be obtained even during multi-threaded operation.
Impact check function Ability to retrieve Google Test execution results and compare them with each other (PC-Native execution results vs. Target execution results / code coverage measurement assertion code impact)
Test Result Report Report output of test results conducted by developer/tester units
Automatic Integrated Report Generation Automatic output of integrated reports of test results from each developer/tester
Functional Safety Certification Tool certification for ISO 26262 (TCL1 to TCL3) and IEC 61508, and issue reference workflow (safety manual) to users

Product Catalogues