HMI Testing via Segmented Primitive Executables
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing testing methodologies for human machine interface (HMI) applications are inefficient and resource-intensive, particularly on target devices with limited computing resources, leading to inadequate test coverage and potential termination of testing sessions due to dynamic resource availability.
Innovation Solution
A method and system for testing HMI applications using a set of mutually independent primitive executables that simulate triggers or conditions corresponding to business logic components and verify outputs using view or platform components, transmitted to the target device for execution, allowing for efficient and scalable testing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing testing methodologies are used on target devices, then testing can be performed, but the limited computing resources (memory, processing capability) cause insufficient test coverage and potential termination of testing sessions
Solution Approach 1:
The patent segments the testing system into two parts: a lightweight test agent that runs on the resource-constrained target device and a powerful host machine that performs the actual testing operations. This segmentation allows the target device to initiate and coordinate tests without requiring full testing capabilities, thus resolving the contradiction between limited resources and adequate test coverage
Solution Approach 2:
The patent introduces a communication interface as an intermediary between the test agent on the target device and the testing framework on the host machine. This intermediary enables the target device to leverage external computing resources while maintaining control over the testing process, effectively overcoming its resource limitations
2Adaptability or versatility
If frequent updates are made to HMI applications, then product differentiation and user engagement are maintained, but testing becomes less effective and time to market is impacted
Solution Approach 1:
The patent implements preliminary action by automatically generating test cases from application source code before deployment. This allows testing to be prepared in advance alongside application development, ensuring that frequent updates can be validated quickly without delaying time to market
Solution Approach 2:
The testing system performs self-service by automatically creating test cases from the application's own source code and business logic. This eliminates manual test creation overhead and enables rapid adaptation to application updates, maintaining both product differentiation and fast time to market
3Reliability
If a full-fledged device agent is deployed on the target device, then comprehensive testing can be performed, but the limited memory and processing capability are exceeded
Solution Approach 1:
The patent extracts the heavy testing framework from the target device and places it on the host machine. Only a minimal test agent remains on the target device to communicate test requirements and results, thereby achieving comprehensive testing capability without exceeding the device's memory constraints
4Ease of operation
If dynamic resource availability is accommodated in testing, then testing can continue on resource-constrained devices, but test execution may be terminated due to resource fluctuations
Solution Approach 1:
The communication interface acts as a mediator that manages the interaction between the resource-constrained test agent and the resource-abundant host machine. This allows the system to accommodate dynamic resource availability on the target device while maintaining stable test execution on the host, preventing test termination due to resource fluctuations
Data Source
AI summary
This disclosure relates generally to a human machine interface (HMI) application, and more particularly to method, system, and framework for testing the HMI application on a target device. In one embodiment, the method may include accessing a test script corresponding to a test case for testing the HMI application on the target device. The test script may include a set of mutually independent primitive executables. Each primitive executable may be configured to simulate at least one of a trigger or a condition corresponding to a business logic (BL) component of the HMI application and to verify an output using at least one of a view component or a platform component of the HMI application. The method may further include transmitting each of the set of primitive executables to the target device for execution, and receiving a result corresponding to the execution of the each of the set of primitive executables.


