System and method for managing a test for testing an embedded system of a vehicle

Patent metadata

Field	Value
Publication number	US-12596640-B2
Application number	US-202318393919-A
Country	US
Kind code	B2
Filing date	Dec 22, 2023
Priority date	Dec 22, 2023
Publication date	Apr 7, 2026
Grant date	Apr 7, 2026

Abstract

Provided are a system, method, and device for managing a test for testing software of an embedded system. According to embodiments, the method may be implemented by at least one processor and may include: receiving, from a user, at least one first user input associated with one or more test requirements; generating, based on the first user input, at least one test package; generating, based on the at least one test package, at least one test environment configuration file; validating the at least one test package and the at least one test environment configuration file; determining a change in the software; and based on determining the change in the software, executing the test according to the validated at least one test package and the validated at least one test environment configuration file, wherein the software of the embedded system may include an in-vehicle electronic control unit (ECU).

First claim

What is claimed is:

1 . A method, implemented by at least one processor, for managing a test for testing software of an embedded system, the method comprising:
receiving, from a user, at least one first user input associated with one or more test requirements; generating, based on the first user input, at least one test package; generating, based on the at least one test package, at least one test environment configuration file; validating the at least one test package and the at least one test environment configuration file; determining a change in the software; and based on determining the change in the software, executing the test according to the validated at least one test package and the validated at least one test environment configuration file, wherein the software of the embedded system comprises an in-vehicle electronic control unit (ECU).

2 . The method according to claim 1 , further comprising:
publishing the validated at least one test package and the validated at least one test environment configuration file by: storing the validated at least one test package and the validated at least one test environment configuration file to one or more storage mediums accessible by other users.

3 . The method according to claim 1 , wherein the first user input comprises information associated with at least one user-defined test case, wherein the generating the at least one test package comprises:
generating, based on the at least one user-defined test case, at least one test scenario template; obtaining, based on the at least one test scenario template, one or more test package artifacts; and combining the at least one test scenario template with the one or more test package artifacts to generate the at least one test package.

4 . The method according to claim 1 , wherein the generating the at least one test environment configuration file comprises:
receiving, from the user, at least one second user input associated with at least one user-defined test plan; generating, based on the second user input and the at least one test package, at least one test plan template; generating, by adding the at least one user-defined test case to the at least one test plan template, at least one test plan; receiving, from the user, at least one third user input associated with at least one user-defined test cycle; and generating, based on the third user input and the at least one test plan, the at least one test environment configuration file.

5 . The method according to claim 1 , wherein the at least one test environment configuration file comprises information defining configuration of at least one test bench.

6 . The method according to claim 1 , wherein the validating the at least one test package and the at least one test environment configuration file comprises:
performing a pre-testing on the software based on the at least one test package and the at least one test environment configuration file; presenting, to the user, a result of the pre-testing; receiving, from the user, at least one fourth user input associated with one of: an approval on the result of the pre-testing and a rejection on the result of the pre-testing; based on determining that the fourth user input is associated with the approval, determining that the at least one test package and the at least one test environment configuration file are valid; and based on determining that the fourth user input is associated with the rejection, determining that the at least one test package and the at least one test environment configuration file are invalid.

7 . The method according to claim 1 , wherein the determining the change in the software comprises:
obtaining a current status of the software; and comparing the current status with a last known status of the software to determine whether or not the change occurs in the software.

8 . The method according to claim 1 , wherein the change in the software comprises a breaking change satisfying one or more conditions defined in the at least one test package.

9 . The method according to claim 1 , wherein the executing the test comprises:
generating, based on the validated at least one test environment configuration file, at least one test bench associated with at least one test environment for testing the software; selecting, based on the at least one test bench, at least one node associated with at least one test environment defined in the at least one test bench; deploying the software to the selected at least one node; and performing, based on the validated at least one test package, the test for testing the software in the selected at least one node.

10 . The method according to claim 1 , further comprising:
collecting one or more test results associated with the test; generating at least one graphical user interface (GUI) including the one or more test results; and presenting, to the user, the at least one GUI.

11 . A system for managing a test for testing software of an embedded system, the system comprises:
a storage storing instructions; and at least one processor configured to execute the instructions to:
receive, from a user, at least one first user input associated with one or more test requirements;
generate, based on the first user input, at least one test package;
generate, based on the at least one test package, at least one test environment configuration file;
validate the at least one test package and the at least one test environment configuration file;
determine a change in the software; and
based on determining the change in the software, execute the test according to the validated at least one test package and the validated at least one test environment configuration file,
wherein the software of the embedded system comprises an in-vehicle electronic control unit (ECU).

12 . The system according to claim 11 , wherein the at least one processor is further configured to execute the instructions to:
publish the validated at least one test package and the validated at least one test environment configuration file by: storing the validated at least one test package and the validated at least one test environment configuration file to one or more storage mediums accessible by other users.

13 . The system according to claim 11 , wherein the first user input comprises information associated with at least one user-defined test case, and wherein the at least one processor is configured to execute the instructions to generate the at least one test package by:
generating, based on the at least one user-defined test case, at least one test scenario template; obtaining, based on the at least one test scenario template, one or more test package artifacts; and combining the at least one test scenario template with the one or more test package artifacts to generate the at least one test package.

14 . The system according to claim 11 , wherein the at least one processor is configured to execute the instructions to generate the at least one test environment configuration file by:
receiving, from the user, at least one second user input associated with at least one user-defined test plan; generating, based on the second user input and the at least one test package, at least one test plan template; generating, by adding the at least one user-defined test case to the at least one test plan template, at least one test plan; receiving, from the user, at least one third user input associated with at least one user-defined test cycle; and generating, based on the third user input and the at least one test plan, the at least one test environment c

Assignees

• Woven By Toyota Inc

Inventors

• Chen Beck
• Courtoy Cyril
• Ioller Benjamin
• Eccleston Jilada
• Fernandez Antonio Tienda
• Cumming James
• Ahmed Haitham

Classifications

• G06F11/3688 Primary

  for test execution, e.g. scheduling of test suites · CPC title

• G06F11/3692

  for test results analysis · CPC title

• G06F11/3684

  for test design, e.g. generating new test cases · CPC title

• G06F11/3698 Primary

  Environments for analysis, debugging or testing of software · CPC title

• G06F11/3672

  Test management · CPC title