Test information synchronization system and method

Abstract

The present disclosure provides a test information synchronization system and method for automatically synchronizing test information for testing software of an embedded system. According to an embodiment, a method of automatically synchronizing test information of a test is implemented by at least one processor that may include processes of collecting at least one test result of the test, determining at least one test case associated with the at least one test result, and synchronizing the at least one test case to the at least one test result. And determining at least one test element associated with the at least one test result from a plurality of test elements of the at least one test case, and synchronizing the at least one test result with the at least one test element.

Description

Technical Field

[0001] Systems and methods consistent with exemplary embodiments of the present disclosure relate to test information management, and more particularly, to automatically synchronizing test information for testing software associated with a vehicle system. Background Art

[0002] Testing of software is required to ensure that the software functions as expected, meets specified requirements, and functions reliably in various scenarios. Software testing is an important part of the software development life cycle (SDLC), and is performed to identify defects, errors, or bugs in the software before it is deployed in an actual system.

[0003] Whenever software includes complex features and / or needs to interact with another software, the testing of the software can become complex and involve multiple processes and users / stakeholders. For example, in the context of development related to features associated with vehicle systems such as Lane Change Assist, Mobile Smart Key, and like functions, multiple electronic control units (ECUs) are sometimes developed and interact with each other to perform the expected features.

[0004] For example, each of the multiple ECUs can be managed by different users located in different geographical locations. For example, a first ECU can be developed by a first developer located at a first location (e.g., a development engineer within a vehicle manufacturer's company), and the first ECU may need to interact with a second ECU developed by a second developer located at a second location (e.g., a supplier). As another example, a first ECU can be tested by a third user located at a third location (e.g., a test engineer). In addition, the first ECU can interact with hardware (e.g., a physical ECU, etc.) managed by a fourth user located at a fourth location, and thus, the testing of the first ECU requires the participation of the hardware.

[0005] Given the above, it is important to ensure that information associated with the testing, such as information on test requirements, test results, or like information, is synchronized in a timely manner and presented appropriately to the users, such that the users involved in the testing are always on the same page regarding the test information and have a coherent understanding of the testing.

[0006] However, in the related art, especially, the testing involves a significant amount of test artifacts (e.g., ECUs developed by different users, etc.) and / or a significant number of users. In the case where the associated users are located in different geographical locations (which may cause communication delays due to time zone differences, etc.) and / or the associated users have different levels of technical backgrounds, it is extremely difficult to ensure that all test information is synchronized timely and appropriately.

[0007] Moreover, in the related art, in most cases, the process of synchronizing test results for specific test cases and corresponding test requirements requires manual intervention by users, which may lead to human errors, delays, and reduced productivity. For example, the user performing the test (e.g., the aforementioned third user) may need to prepare the test results in a readable format. Then, in order to map the test results to the corresponding test cases and establish associated test requirements, the user manually collects information or data associated with the test results (e.g., test logs, metadata, etc.) and studies the data. After that, the data is further processed.

[0008] Moreover, in the related art, especially, in the case where the number of users participating in the test is huge, it is difficult to appropriately present the test information to all users associated with the test. For example, the test information can be prepared to include a significant amount of technical details, which sometimes cannot be understood by users without sufficient technical backgrounds. On the contrary, the test information can be prepared to include only general information with little technical details, which sometimes is not beneficial to users with sufficient technical backgrounds who want to study the test information in detail.

[0009] Considering the above situations, the test information management methods and processes in the related art are time-consuming and ineffective, and become a burden for users. As a result, it is extremely difficult to ensure that all test information is synchronized timely and appropriately (even if not impossible). Therefore, the testing of software in the related art may be time-consuming and inefficient, and may delay the development of the software. Summary of the Invention

[0010] Exemplary embodiments consistent with the present disclosure provide methods and systems for efficiently and effectively managing test information of tests. Specifically, the exemplary embodiments of the present disclosure provide systems, methods, devices, or the like for efficiently and effectively synchronizing and presenting test information. Moreover, the exemplary embodiments of the present disclosure enable test information to be synchronized timely and appropriately, and enable the synchronized test information to be effectively and efficiently presented to users with different levels of technical backgrounds.

[0011] According to an embodiment, a method for automatically synchronizing test information of a test can be provided. The method can be implemented by at least one processor. The processor can include the following processes: collecting at least one test result of a test, determining at least one test case associated with the at least one test result, determining at least one test requirement associated with the at least one test result from among a plurality of test requirements of the at least one test case, and synchronizing the at least one test result having the at least one test requirement. The test can include a test of software of a vehicle system, and the software can include a virtual electronic control unit (ECU).

[0012] According to an embodiment, the synchronization of the at least one test result having the at least one test requirement can include: generating a mapping of the at least one test result and the determined at least one test requirement. Alternatively or further, the synchronization of the at least one test result having the at least one test requirement can include: updating the mapping of the at least one test result and the determined at least one test requirement.

[0013] According to an embodiment, the collection of the at least one test result can include: establishing communication with at least one test execution environment, collecting more than one test data from the at least one test execution environment, and extracting information associated with the test result from the more than one test data.

[0014] According to an embodiment, the determination of the at least one test case can include: processing the at least one test result to obtain at least one identification information parameter associated with the at least one test case, and identifying the at least one test case based on the at least one identification information parameter. The at least one identification information parameter can include at least one of the following parameters: a keyword associated with the at least one test case, an inherent identifier (ID: identifier) associated with the at least one test case, and a label associated with the at least one test case.

[0015] According to an embodiment, the determination of the at least one test requirement can include: processing the at least one test result to obtain at least one test parameter associated with the at least one test requirement; and determining at least one test requirement from among a plurality of test requirements of the at least one test case based on the at least one test parameter. The at least one test parameter can include at least one of the following parameters: a keyword associated with the at least one test requirement, a description prescribing at least a part of the at least one test requirement, and a label associated with the at least one test requirement.

[0016] According to an embodiment, the processor may further include the following processing: obtaining information associated with more than one user, determining a presentation format based on the information of the more than one user, and presenting the synchronized test information to the more than one user based on the mapping and the presentation format. The presentation of the synchronized test information may include: generating a first graphical user interface (GUI) based on the mapping and the presentation format and presenting the first GUI to a first user. Moreover, the presentation of the synchronized test information may include: generating a second GUI based on the mapping and the presentation format and presenting the second GUI to a second user. The presentation format may be a general format or a specific format.

[0017] According to an embodiment, a system for automatically synchronizing test information of a test may be provided. The system may include: a storage memory that stores instructions; and at least one processor communicatively connected to the storage memory. The at least one processor may be configured to execute the instructions to: collect at least one test result of the test, determine at least one test case associated with the at least one test result, determine at least one test requirement associated with the at least one test result from among a plurality of test requirements of the at least one test case, and synchronize the at least one test result having the at least one test requirement. The test may include a test of software of a vehicle system, and the software may include a virtual electronic control unit (ECU).

[0018] According to an embodiment, the at least one processor may be configured to execute the instructions to generate a mapping of the at least one test result and the determined at least one test requirement, thereby synchronizing the at least one test result having the at least one test requirement. Further or alternatively, the at least one processor is configured to execute the instructions to update the mapping of the at least one test result and the determined at least one test requirement, thereby synchronizing the at least one test result having the at least one test requirement.

[0019] According to an embodiment, the at least one processor may be configured to execute the instructions to: establish communication with at least one test execution environment, collect more than one test data from the at least one test execution environment, and extract information associated with the test result from the more than one test data, thereby collecting at least one test result.

[0020] According to an embodiment, at least one processor may be configured to execute instructions to: process at least one test result to obtain at least one identification information parameter associated with at least one test case, identify at least one test case based on the at least one identification information parameter, and thereby determine at least one test case. The at least one identification information parameter may include at least one of the following parameters: a keyword associated with at least one test case, an inherent identifier (ID) associated with at least one test case, and a label associated with at least one test case.

[0021] According to an embodiment, at least one processor may be configured to execute instructions to: process at least one test result to obtain at least one test parameter associated with at least one test requirement, determine at least one test requirement from among a plurality of test requirements of at least one test case based on the at least one test parameter, and thereby determine at least one test requirement. The at least one test parameter includes at least one of the following parameters: a keyword associated with at least one test requirement, a description that defines at least a part of at least one test requirement, and a label associated with at least one test requirement.

[0022] According to an embodiment, at least one processor may further be configured to execute instructions to: obtain information associated with one or more users, determine a presentation format based on the information of the one or more users, and present the synchronized test information to the one or more users based on the mapping and the presentation format. At least one processor may be configured to execute instructions to: generate a first graphical user interface (GUI) based on the mapping and the presentation format, present the first GUI to a first user, and thereby present the synchronized test information. Further, at least one processor may be configured to execute instructions to: generate a second GUI based on the mapping and the presentation format, present the second GUI to a second user, and thereby present the synchronized test information. The presentation format may be a general format or a specific format.

[0023] Additional aspects will be described in part in the following description, may be partially apparent from the description, or may be realized by the implementation of the presented embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Hereinafter, features, advantages, and importance of preferred embodiments of the present disclosure will be described with reference to the drawings, in which like reference numerals denote like elements.

[0025] Figure 1 A block diagram showing an exemplary system architecture for managing test information associated with testing of test software for one or more embodiments.

[0026] Figure 2 Block diagram of exemplary components of a test information management system representing more than one embodiment.

[0027] Figure 3 Flowchart of an exemplary method for automatically synchronizing test information of a test of test software representing more than one embodiment.

[0028] Figure 4 Exemplary test cases and associated test requirements representing more than one embodiment.

[0029] Figure 5 Diagram of an exemplary use case of method 300 representing more than one embodiment.

[0030] Figure 6 Flowchart of an exemplary method for presenting synchronized test information representing more than one embodiment.

[0031] Figure 7 Exemplary graphical user interface (GUI) representing more than one embodiment.

[0032] Figure 8 Another exemplary GUI representing more than one embodiment. Detailed Description

[0033] The following detailed description of the preferred embodiments refers to the accompanying drawings. The above disclosure provides examples and illustrations, but is not intended to be exhaustive nor to limit the implementations to the exact forms disclosed. Modifications and variations can be obtained in view of the above disclosure or in accordance with the implementation of the embodiments. Moreover, one or more features or components of one embodiment can be incorporated into another embodiment (or one or more features of another embodiment) or can be combined therewith. Also, it is understood that in the flowcharts and descriptions of operations provided below, one or more operations can be omitted, one or more operations can be added, one or more operations can be performed (at least partially) simultaneously, and the order of one or more operations can be switched.

[0034] Even if a particular combination of features is recited in the claims and / or disclosed in the specification, such combination is not intended to limit the disclosure of possible implementations. In fact, many of these features can be combined in ways not specifically recited in the claims and / or not disclosed in the specification. Each of the dependent claims listed below can only directly depend on one claim, but the disclosure of possible implementations includes each dependent claim combined with all other claims within the set of claims.

[0035] Unless otherwise expressly specified, elements, acts, or instructions used in this specification should not be construed as critical or essential. In addition, the articles "a" and "an" used in this specification are intended to include more than one item and may be used interchangeably with "more than one". In cases where only one item is meant, terms such as "one" or equivalent terms are used. In addition, the terms "has", "have", "having", "include", "including", or similar terms used in this specification are meant to be open-ended terms. Moreover, unless otherwise expressly stated, the phrase "based on..." means "at least partially based on...". Also, expressions such as "at least one of [A] and [B]" or "at least one of [A] or [B]" should be understood to include only A, only B, or both A and B.

[0036] References throughout this specification to "one embodiment", "an embodiment", "a non-limiting preferred embodiment", or similar terms mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the solution. Thus, the phrases "in one embodiment", "in an embodiment", "in a non-limiting preferred one embodiment", and similar terms throughout this specification may all refer to the same embodiment, but not necessarily so.

[0037] Moreover, the features, advantages, and characteristics described in this disclosure may be combined in any suitable manner in one or more embodiments. Given the description of this specification, those skilled in the art should recognize that this disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in a particular embodiment that may not necessarily be present in all embodiments of this disclosure.

[0038] In addition, the term "vehicle" or similar terms used in this specification may refer to any powered and / or mechanical machine capable of transporting or conveying people and / or goods, e.g., cars, trucks, motorcycles, buses, bicycles, mobility scooters, and the like.

[0039] The terms "testing information", "test information" and similar terms as described in this specification may refer to information associated with the establishment of tests for test software, where the software is associated with a vehicle system. This information may include information on one or more test requirements, information on one or more test cases, information on one or more test results, and / or any other suitable information involved in the test.

[0040] The terms "test artifacts", "testing artifacts" and similar terms as described in this specification may refer to one or more components that make up a test. For example, test artifacts may include one or more software-based components (such as virtual ECUs, simulation ECUs, vehicle models, etc.), one or more hardware-based components (such as physical ECUs, vehicle hardware components, etc.), one or more test configurations (such as test environment configurations, test cycles, test executions, etc.), one or more test scenarios, one or more test cases, one or more test packages, and the like.

[0041] Exemplary embodiments consistent with the present disclosure provide methods, systems, and apparatuses for efficiently and effectively managing the test information of tests. Specifically, the exemplary embodiments of the present disclosure provide systems, methods, devices, or the like for efficiently and effectively synchronizing and presenting test information.

[0042] According to an embodiment, the systems, methods, or the like provided by the exemplary embodiments may automatically collect one or more test results, automatically determine the test cases and test requirements associated with the one or more test results, and automatically synchronize the one or more test results for the corresponding test requirements. Moreover, the systems, methods, or the like provided by the exemplary embodiments may automatically determine an appropriate presentation format according to user information, and present the synchronized test information to one or more users in the appropriate presentation format. The test information may be associated with the testing of one or more software for one or more vehicle systems, such as the testing of one or more in-vehicle ECUs.

[0043] Furthermore, the exemplary embodiments of the present disclosure enable the timely and matching synchronization of test information, and enable the synchronized test information to be effectively and efficiently presented to users with different levels of technical backgrounds. Therefore, the testing of software can be carried out and managed more efficiently, the burden on users can be significantly reduced, and the time required to develop software can be significantly reduced.

[0044] It is assumed that the features, advantages, and importance of the above-described exemplary embodiments in this specification are only a part of the present disclosure, and are not intended to be exhaustive or to limit the scope of the present disclosure. Hereinafter, further explanations of the features, components, configurations, operations, implementation schemes, and associated technical advantages and importance of the exemplary embodiments of the present disclosure are provided.

[0045] Figure 1 A block diagram of an exemplary system architecture 100 for managing test information associated with testing software, representing one or more embodiments. According to an embodiment, the software may include one or more in-vehicle electronic control units (ECUs: Electronic Control Unit), for example, physical ECUs, simulation ECUs, virtualized ECUs, or combinations thereof. As Figure 1 shown, the system architecture 100 may include a test information management system 110, a plurality of user devices (UEs: User Equipment) 120-1 to user device 120-N, a plurality of nodes 130-1 to nodes 130-N, and a network 140.

[0046] Generally, the test information management system 110 may be communicatively connected to the plurality of UEs 120-1 to UEs 120-N and the plurality of nodes 130-1 to nodes 130-N via the network 140, and may be configured to interact with the plurality of UEs 120-1 to UEs 120-N and the plurality of nodes 130-1 to nodes 130-N to manage test information for one or more associated users. Hereinafter, with reference to Figure 2 descriptions of exemplary components that may be included in the test information management system 110 are provided. Hereinafter, with reference to Figures 3 to 8 descriptions of associated operations and use cases are provided.

[0047] Each of the plurality of UEs 120-1 to UEs 120-N may include one or more machines, devices, or the like that can receive, generate, store, process, and / or provide information when used by an associated user. For example, one or more of the plurality of UEs 120-1 to UEs 120-N may include computing devices (e.g., desktop computers, laptop computers, tablet computers, handheld computers, smart speakers, servers, etc.) that can be associated with one or more users participating in the testing of the software, mobile devices (e.g., smartphones, etc.), wearable devices (e.g., a pair of smart glasses or a smart watch), SIM (Subscriber Identity Module)-based devices, or any other suitable devices.

[0048] Multiple UEs 120-1 to 120-N can be utilized by more than one associated user to access the test information management system 110 and utilize the test information management system 110. For example, a user can access the test information management system 110 via the associated UE, view one or more available test artifacts and / or one or more available test requirements, and manage one or more test requirements based thereon. Further, the user can also utilize the test information management system 110 to obtain (e.g., view, download, etc.) information associated with one or more test results.

[0049] According to an embodiment, at least a portion of the multiple UEs 120-1 to 120-N can be located in different geographical locations. For example, a first portion of the multiple UEs 120-1 to 120-N can be utilized by a first user (e.g., a business manager) having a first role, and the first user can be located at a first location. On the other hand, a second portion of the multiple UEs 120-1 to 120-N can be utilized by a second user (e.g., a test engineer) having a second role, and the second user can be located at a second location different from the first location.

[0050] On the other hand, each of the multiple nodes 130-1 to 130-N can include one or more devices, apparatuses, systems, or any other suitable components that can receive, host, store, deploy, process, provide, or perform similar actions on information and data associated with a test.

[0051] According to an embodiment, at least a portion of the plurality of nodes 130-1 to 130-N may be configured to host, deploy, store, provide, or perform similar actions on more than one test artifact or component. For example, a portion of the plurality of nodes 130-1 to 130-N may include a device or apparatus that can be used for more than one computer-executable software application, such as more than one virtualized ECU of a vehicle system, more than one simulation ECU, and / or any other suitable software-based component (e.g., a vehicle model, a data communications module (DCM) model, a heating, ventilation, and air conditioning (HVAC) model, etc.) to build, store, execute, simulate, or perform similar actions. As another example, a portion of the plurality of nodes 130-1 to 130-N may include more than one fully developed physical ECU, more than one partially developed physical ECU, more than one vehicle hardware component (e.g., a powertrain, an engine, etc.) or similar hardware components, or may be communicatively connected to such hardware components.

[0052] According to an embodiment, at least a portion of the plurality of nodes 130-1 to 130-N may be associated with more than one test execution environment. For example, this portion of the nodes may have at least one software-based test execution environment (e.g., a software-in-the-loop (SIL) test environment, a virtual ECU (V-ECU) test environment, a model-in-the-loop (MIL) test environment, a processor-in-the-loop (PIL) test environment, etc.) and / or be communicatively connected (e.g., a wired connection, a wireless connection, etc.) to this portion of the nodes or at least one hardware-based test execution environment (e.g., a hardware-in-the-loop (HIL) test environment, etc.) deployed on this portion of the nodes.

[0053] Moreover, at least a portion of the plurality of nodes 130-1 to 130-N may include more than one storage medium such as a server or a server cluster, which may be configured to store, disclose, or perform similar actions on more than one data or information provided by the test information management system 110, more than one of the plurality of UEs 120-1 to 120-N, and / or another portion of the plurality of nodes 130-1 to 130-N.

[0054] According to an embodiment, the plurality of nodes 130-1 to 130-N may include a test management system, which may be configured to specify one or more test requirements, create test cases, view test information, and perform similar operations by more than one user.

[0055] According to an embodiment, one or more of the plurality of nodes 130-1 to 130-N may include one or more interfaces, and each interface may be configured to connect the associated nodes in a communicable manner to the test information management system 110. For example, one or more of the plurality of nodes may include a hardware interface, a software interface (e.g., a programmatic interface, an application program interface (API)), and / or a similar interface.

[0056] According to an embodiment, at least a part of the plurality of nodes 130-1 to 130-N is located in a geographical location different from that of the test information management system 110, a geographical location different from that of one or more of the plurality of UEs 120-1 to 120-N, and / or a geographical location different from that of another part of the plurality of nodes 130-1 to 130-N.

[0057] The network 140 may include one or more wired and / or wireless networks, which may be configured to connect the test information management system 110, the plurality of UEs 120-1 to 120-N, and the plurality of nodes 130-1 to 130-N to each other. For example, the network 140 may include a cellular network (e.g., a fifth-generation (5G) network, a long-term evolution (LTE) network, a third-generation (3G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., a public switched telephone network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber-based network, or a similar network and / or a combination of these types or other types of networks.

[0058] According to an embodiment, network 140 may include a virtual network, which may include one or more physical network components (e.g., Ethernet, WiFi (Wireless Fidelity) module, telecommunication network hardware, etc.) that implement one or more virtualized network functions (e.g., a controller area network (CAN) bus, etc.).

[0059] Figure 2 Block diagram of exemplary components of a test information management system 200 representing one or more embodiments. The test information management system 200 may be the same as Figure 1 the test information management system 110.

[0060] As Figure 2 shown, the test information management system 200 may include at least one communication interface 210, at least one storage 220, and at least one processor 230. However, it can be understood that without departing from the scope of the present disclosure, the test information management system 200 may include more components or fewer components than those shown, and / or the components included therein may be configured in any method different from the method shown.

[0061] The communication interface 210 may include components such as a transceiver (e.g., a transceiver, a separate receiver and transmitter, etc.) that enable the test information management system 200 (or one or more components included therein) to communicate with one or more components external to the test information management system 200 via a wired connection, a wireless connection, or a combination of wired and wireless connections. For example, the communication interface 210 may connect the test information management system 200 (or one or more components included therein) to multiple UEs (e.g., Figure 1 UE120-1 to UE120-N, etc.) and multiple nodes (e.g., Figure 1 node 130-1 to node 130-N, etc.), thereby enabling them to communicate with each other and operate with each other. As another example, the communication interface 210 may enable the components of the test information management system 200 to communicate with each other. For example, the communication interface 210 may connect the storage 220 to the processor 230, thereby enabling them to communicate with each other and operate with each other.

[0062] According to an embodiment, the communication interface 210 may include a hardware-based interface, such as a bus interface, an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, a software interface, or the like. According to an embodiment, the communication interface 210 may include at least one controller area network (CAN) bus, which may be configured to communicatively connect components of the test information management system 200 (such as the memory 220, the processor 230, etc.) to a plurality of UEs (such as UE120-1 to UE120-N) and a plurality of nodes (such as node 130-1 to node 130-N). Further or alternatively, the communication interface 210 may include a software-based interface, such as an application programming interface (API), a virtualized network interface (such as a virtualized CAN bus, etc.), or the like.

[0063] According to an embodiment, the communication interface 210 may be configured to receive information from one or more components external to the test information management system 200, provide the information to the processor 230 for further processing, and / or provide the information to the memory 220 for storage. For example, the communication interface 210 may receive from a plurality of UEs one or more user inputs specifying one or more test requirements (such as test scenarios, test cases, test plans, test cycles, etc.), and may provide the user input to the processor 230 and / or the memory 220. Similarly, the communication interface 210 may be configured to enable the processor 230 of the test information management system 200 to provide one or more pieces of information to one or more components external to the test information management system 200. For example, the communication interface 210 may enable the processor 230 to present one or more graphical user interfaces (GUIs) on a plurality of UEs.

[0064] At least one memory 220 may include one or more storage media suitable for storing data, information, and / or computer-readable instructions / computer-executable instructions therein. According to an embodiment, the memory 220 may include a random access memory (RAM), a read-only memory (ROM), and / or another type of dynamic or static storage device (such as flash memory, magnetic memory, and / or optical memory) for storing information and / or instructions for use by the processor 230.

[0065] Further or alternatively, the memory 220 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optical disk, and / or a solid state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cassette tape, a magnetic tape, and / or another type of non-transitory computer-readable medium, and include a corresponding drive.

[0066] According to an embodiment, the memory 220 may be configured to store information to be utilized by the processor 230 to facilitate automatic synchronization of test information. For example, the memory 220 may be configured to store one or more test requirements specified by one or more users, store information associated with one or more users participating in a test, store one or more test results, and perform similar operations.

[0067] At least one processor 230 may include one or more processors that can be programmed to perform functions or operations to facilitate automatic synchronization of test information. For example, the processor 230 may be configured to execute computer-readable instructions stored in a storage medium (e.g., the memory 220, etc.), thereby performing one or more actions or one or more operations described in this specification. Hereinafter, with reference to Figure 3 and Figure 6 an explanation of exemplary operations that can be performed by the processor 230 is provided.

[0068] According to an embodiment, the processor 230 may be configured to receive one or more signals that define one or more instructions to perform one or more operations (e.g., via the communication interface 210, etc.). Moreover, the processor 230 may be implemented by hardware, firmware, or a combination of hardware and software. The processor 230 may include a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and / or another type of processing or computing component.

[0069] Figure 3Flowchart of an exemplary method 300 for automatically synchronizing test information of a test of test software representing more than one embodiment. When computer-executable instructions stored in at least one storage (e.g., storage 220) are executed, more than one action of method 300 can be performed by at least one processor (e.g., processor 230) of the test information management system of the exemplary embodiment. The software under test may include an in-vehicle electronic control unit (ECU) associated with a vehicle system and / or any other software component.

[0070] Generally, a test information management system (or at least one processor associated therewith) may be configured to collect more than one test result, determine more than one test case associated with the collected more than one test result, and synchronize more than one test result of more than one test requirement having more than one test case. Hereinafter, Figure 3 description of the actions will be provided together with Figures 4 to 5 description of an exemplary use case.

[0071] Figure 4 Exemplary test cases and associated test requirements representing more than one embodiment. In this exemplary use case, the test case with ID "#ABC" includes multiple test requirements. The test requirements are associated with a test scenario for testing the function of an ECU (represented as "Function A" and "ECU A" respectively in Figure 4 ) (represented as "Scenario D" in Figure 4 ), and on the other hand, the test also involves testing a service (represented as "Service E"). As Figure 4 shown, the characteristics of the function and the content of the test scenario are specified in a general format (hereinafter, refer to Figure 6 and Figure 7 for further description). It can be understood that in addition to the test scenario (as Figure 4 shown), other test requirements such as test plans, test executions, test configurations, test cycles, and the like can also be specified in the same way.

[0072] Figure 4Test cases can be specified or created by a first user through the utilization of a test information management system and / or a test management system separate from the test information management system. When test cases are specified and associated test requirements are established, tests can be executed based on this. In this regard, tests can include multiple tasks such as tasks associated with hardware-based tests and / or tasks associated with software-based tests, and each task can be assigned to each test execution environment. For example, tasks associated with hardware-based tests are assigned to one or more hardware-based test execution environments (e.g., HIL test environment, etc.), while on the other hand, tasks associated with software-based tests are assigned to one or more software-based test execution environments (e.g., SIL test environment, etc.). Therefore, tests for multiple test requirements can be conducted in multiple test execution environments, and multiple test results (each associated with a test requirement) can be generated.

[0073] Return and refer to Figure 3 In operation S310, at least one processor of the test information management system can be configured to collect at least one test result. Specifically, at least one processor can establish communication with at least one node associated with at least one test execution environment (via the communication interface of the test information management system), obtain test data from at least one node, and extract information / data associated with at least one test result from the test data. Information associated with at least one test result can include identification information parameters (further described below with reference to operation S320), test parameters (further described below with reference to operation S330), the status of the test (e.g., success, failure, etc.), log information of the test, images of the test (e.g., screenshots, etc.), and the like.

[0074] According to an embodiment of conducting multiple tests in multiple test execution environments, at least one processor can, in the same manner as described above, establish communication with multiple nodes associated with multiple test execution environments simultaneously or sequentially, thereby collecting multiple test results from the multiple nodes. Hereinafter, refer to Figure 5 Provide an explanation of an exemplary use case associated with this.

[0075] According to an embodiment, at least one processor of the test information management system can be configured to communicate continuously (or periodically) with a node associated with a test execution environment in such a way as to collect test results from the node in real time or substantially real time and continuously (or periodically).

[0076] Considering the above situation, at least one processor of the test information management system can be configured to collect test results according to test requirements. Therefore, without waiting for the completion of tests related to all test requirements, it is possible to process the test results immediately when the test results can be utilized, synchronizing the corresponding test results for each test requirement.

[0077] Still referring to Figure 3 , when at least one test result is collected in operation S310, method 300 can proceed to operation S320, in which at least one processor of the test information management system can be configured to determine at least one test case associated with the at least one collected test result.

[0078] Specifically, at least one processor can be configured to process the collected test results to obtain at least one identification information parameter associated with at least one test case. In this regard, the "identification information parameter" described in this specification can refer to a parameter that can be used by at least one processor to identify a target test case. The identification information parameter associated with at least one test case can include one or more of the following parameters: keywords associated with at least one test case, an inherent identifier (ID) associated with at least one test case, the name or label of at least one test case, and custom tags associated with at least one test case.

[0079] At least one processor can be configured to process the obtained at least one test result through various operations to obtain one or more identification information parameters of at least one test case. For example, at least one processor can perform natural language processing (NLP) operations to extract one or more keywords of at least one test case from the test results, can perform a retrieval operation to determine the ID and / or custom tags of at least one test case from the test results, and can perform similar operations.

[0080] When at least one identification information parameter is obtained, at least one processor can be configured to identify at least one test case associated with the at least one collected test result based on the at least one identification information parameter. For example, if it is assumed that at least one processor obtains the ID "#ABC" from the test results, then at least one processor retrieves any test case with the same ID "#ABC" from among the multiple test cases stored in the memory (e.g., memory 220) and / or managed by the test management system. It is assumed that at least one processor can identify at least one test case with other identification information parameters (e.g., name, label, tag, etc.) in the same manner.

[0081] When at least one test case is identified based on at least one identification information parameter, at least one processor may be configured to obtain information about the identified at least one test case. For example, at least one processor may obtain the identified at least one test case from a storage of a test information management system. As another example, at least one processor may obtain the identified at least one test case from a test management system (via more than one API call, etc.).

[0082] It can be understood that, in some implementations, at least one processor may be configured to perform action S320 before action S310 without departing from the scope of the present disclosure. For example, at least one processor may first receive at least one test case, may determine parameters associated with more than one test requirement of the at least one test case, and may collect more than one test result associated with more than one test requirement based on the determined parameters.

[0083] Moreover, in action S330, at least one processor of the test information management system may be configured to determine at least one test requirement associated with at least one test result from among a plurality of test requirements of the at least one test case.

[0084] Specifically, at least one processor may be configured to process the collected at least one test result to obtain at least one test parameter. In this regard, the "test parameter" described in this specification may refer to a parameter that can be used by at least one processor to identify a target test requirement. The test parameter may include more than one of the following parameters: a keyword associated with at least one test requirement, a description defining the test requirement, and a custom label associated with at least one test requirement. At least one processor may be configured to obtain more than one test parameter in the same manner as the method for obtaining more than one identification information parameter (e.g., performing NLP actions, performing retrieval actions, etc.).

[0085] When at least one test requirement is determined, method 300 may proceed to action S340, in which at least one processor of the test information management system may be configured to synchronize at least one test result having at least one test requirement. According to an embodiment, at least one processor may synchronize at least one test result having at least one test requirement by generating a mapping between the at least one test result and the at least one test requirement. According to an embodiment in which a mapping is generated by the above actions, at least one processor may obtain the generated mapping (from a storage of the test information management system, etc.) and may update the generated mapping with the latest test result. Hereinafter, refer to Figure 5 A description of an exemplary mapping is provided.

[0086] According to an embodiment, when synchronizing at least one test result having at least one test requirement, at least one processor of the test information management system may be configured to present the synchronized information to more than one user. For example, at least one processor may generate at least one GUI including the mapped information based on the mapping of at least one test result to at least one test requirement, and may send at least one GUI to at least one UE associated with the user, whereby at least one GUI is presented to the associated user. Alternatively or additionally, at least one processor may provide the mapping to the test management system, and thereafter, the test management system may be configured to generate and present at least one GUI for the user. According to an embodiment, at least one GUI may be generated based on user information (e.g., the role of the user, etc.). Hereinafter, with reference to Figure 7 and Figure 8 an exemplary GUI including the synchronized information will be described.

[0087] Hereinafter, with reference to Figure 5 an exemplary use case of Method 300 will be described. Generally, the test information management system 510 (or at least one processor associated therewith) may be configured to collect a plurality of test results 520, may determine and obtain a test case 530 associated with the collected test results, and may synchronize the collected test results having the associated test requirements of the test case 530 by generating / updating a mapping 540. The test information management system 510 may be the same as the test information management system described in this specification with reference to other figures.

[0088] The test results 520 may include Test Result 1 to Test Result 4, and each test result may be associated with a test requirement of a test case (e.g., Figure 4 the test case). At least a part of Test Result 1 to Test Result 4 may be associated with tests performed in different test execution environments and may be collected from different nodes by the test information management system 510 (or at least one processor associated therewith). In this regard, the test information management system 510 (or the associated processor) may be configured to perform operation S310 and communicate with a plurality of nodes simultaneously (or sequentially) to collect a plurality of test results from the plurality of nodes.

[0089] When at least one of Test Result 1 to Test Result 4 is obtained, the Test Information Management System 510 (or at least one processor associated therewith) can be configured to associate the obtained test result with the corresponding test case. Specifically, the Test Information Management System 510 (or at least one processor associated therewith) can perform Action S320 to obtain the identification information parameter from the test result, and (based on the identification information parameter) determine at least one test case associated with at least one test result, and then obtain the information of at least one test case. For example, when at least one of Test Result 1 to Test Result 4 is collected, the Test Information Management System 510 (or at least one processor associated therewith) can be configured to obtain at least one identification information parameter from the collected test result. In Figure 5 In an exemplary use case of Figure 5 , Test Result 1 and Test Result 2 include the keyword of the test case (represented as "ABC" in Figure 5 ), and Test Result 3 and Test Result 4 include the ID of the test case (represented as "#ABC" in

[0090] . Based on the identification information parameter, at least one processor can determine that the collected test result is associated with the ID of "#ABC", or is associated with the test case having a name / ID / description associated with the keyword of "ABC". Therefore, at least one processor can be configured to obtain the information of the determined test case. It can be understood that in some implementation solutions, the Test Information Management System 510 (or at least one processor associated therewith) can be configured to first obtain the information of the test case (for example, obtain from the storage of the Test Information Management System 510, obtain from the test management system, etc.) without departing from the scope of the present disclosure, and then collect the test results associated with the test case.

[0091] When the information of the obtained test result and the associated test case is obtained, the Test Information Management System 510 (or at least one processor associated therewith) can be configured to associate the obtained test result with the corresponding test requirement of the test case. Specifically, the Test Information Management System 510 (or at least one processor associated therewith) can perform Action S330 to obtain the test parameter from the test result, and determine at least one test requirement associated with at least one test result from multiple test requirements of the test case (based on the test parameter). For example, in Figure 5In an exemplary use case, test case 530 includes multiple test requirements 1 to test requirement N, each test requirement having a parameter associated therewith. Test results 1 and test results 2 include keywords that define the respective test requirements. On the other hand, test results 3 and test results 4 include descriptions of the test requirements. Based on the test parameters, at least one processor can determine the test requirements associated with the collected test results.

[0092] Thereafter, the test information management system 510 (or at least one processor associated therewith) can be configured to perform action S340 to synchronize the obtained test results having the corresponding test requirements. For example, at least one processor can generate a new mapping 540 containing the synchronized information (or can update the generated mapping 540).

[0093] When synchronizing test information (e.g., information on test results and corresponding test requirements), the test information management system 510 (or at least one processor associated therewith) can be configured to present the synchronized test information to more than one user. Hereinafter, with reference to Figure 6 An exemplary method associated therewith will be described. Hereinafter, with reference to Figure 7 and Figure 8 An exemplary GUI associated therewith will be described.

[0094] Figure 6 A flowchart showing an exemplary method 600 for presenting synchronized test information representing more than one embodiment. One or more actions of method 600 can be performed by at least one processor of the test information management system and / or by a system / device different from the test information management system (e.g., a test management system, etc.).

[0095] As Figure 6 shown, in action S610, mapping information is obtained. According to an embodiment in which action S610 is performed by the test information management system (or at least one processor associated therewith), the mapping information can be obtained in real time or substantially in real time via method 300, or can be obtained from the storage of the test information management system (e.g., storage 220). According to an embodiment in which action S610 is performed by the test management system, the mapping information can be obtained by the test management system from the test information management system via one or more API calls.

[0096] When the mapping information is obtained, method 600 may proceed to action S620, in which information of one or more users associated with the test case or the test is obtained. For example, the test information management system (or at least one processor associated therewith) may determine one or more users associated with the test case or the test based on the test case information (e.g., identification information parameters such as test case ID, keyword, tag, etc.) included in the mapping information, and then, the information of the one or more users may be obtained later (e.g., from the memory 220, the node hosting the user information, etc.). The information of the user may include the user's role, the user's position, the user's job description, previous presentation information, and / or the like. In an implementation where action S620 is performed by the test management system, it is assumed that the test management system may be configured to obtain user information in the same manner.

[0097] When the user information is obtained, method 600 may proceed to action S630, in which the presentation format associated with the user is determined. For example, the test information management system (or at least one processor associated therewith) may determine the presentation format including information suitable for the user based on the user information (e.g., the user's role / attribute / job information).

[0098] According to an implementation, the presentation format may include a general format or a specific format. In this regard, the term "general format" as described in this specification may refer to any format including a presentation with descriptions that can be understood by users without (or with limited) specific technical background. On the contrary, the term "specific format" as described in this specification may refer to any format including a presentation with descriptions that can be understood by users with a specific level of technical background. For example, the specific format may refer to a specific type of programming code or a programming code that can be understood by users with knowledge of the system or any other computer-executable language. In an implementation where action S630 is performed by the test management system, it is assumed that the test management system may be configured to determine the presentation format in the same manner.

[0099] When the presentation format is determined, method 600 may proceed to action S640, in which the synchronized test information is presented. For example, the test information management system (or at least one processor associated therewith) may generate a GUI including the synchronized test information based on the mapping information and the presentation format, and then, the GUI may be presented to the user. The generated GUI may present the synchronized test information in the presentation format associated with the user. In an implementation where action S640 is performed by the test management system, it is assumed that the test management system may be configured to present the synchronized test information in the same manner.

[0100] Therefore, the synchronized test information can be presented to the user efficiently and effectively. Specifically, the GUI presented to the user may include appropriate content suitable for the user in consideration of the level of the user's technical background. Hereinafter, referring to Figure 7 an explanation of an exemplary GUI generated in a general format will be provided. Hereinafter, referring to Figure 8 an explanation of an exemplary GUI generated in a proprietary format will be provided.

[0101] Figure 7 An exemplary GUI 700 representing more than one embodiment. The GUI 700 can be generated by at least one processor of a test information management system (or test management system) in a manner that presents the synchronized test information in a general format to a first user and presented to the first user (via a UE associated with the first user).

[0102] As Figure 7 shown, the GUI 700 may include a first part 710 and a second part 720. The first part 710 may include a description of one or more test requirements of a test case, while the second part 720 may include the synchronized test information (i.e., the corresponding one or more test requirements and one or more test results) and a plurality of interactive elements 721.

[0103] According to an embodiment, one or more test requirements in the first part 710 may be presented in the form of one or more interactive elements (e.g., selectable text, etc.). As a result, whenever the first user interacts with the expected test requirement, at least one processor may present the associated test result to the first user (e.g., presenting the test result in an overlay window, highlighting the test result in the second part 720, etc.). In some implementations, the interactive elements associated with one or more test requirements may be presented according to the associated test results. For example, in Figure 7 the example of, the test requirement "set status is warning" is presented in italic format to notify the user that this requirement has a different test result (e.g., failure) from other test requirements (e.g., success).

[0104] Moreover, in Figure 7In the example, more than one test result is presented as respective icons in the second part 720 (e.g., a check icon indicates a "success" test result, an x icon indicates a "failure" test result, etc.). It is understandable that instead of or further to the icon-based presentation, the test result can be presented in the form of a text-based presentation (e.g., terms such as "success", "failure", or similar terms can be presented), a color-based presentation (e.g., green indicates a "success" test result, red indicates a "failure" test result, etc.).

[0105] Moreover, the test requirement can be presented together with more than one interactive element (e.g., selectable text, button, etc.), and as a result, when interacting with the first user, at least one processor can further present details associated with the test result. For example, in Figure 7 the example, the test requirement "its set state is a warning" is presented together with the selectable text "further refer to details". When a user interaction in the selectable text is determined, at least one processor can update the GUI 700 to present further information (e.g., the reason for failure, etc.) of the associated test result (e.g., in a pop-up window, etc.).

[0106] In addition, when each of the multiple interactive elements 721 is interacted with by the first user, one or more actions for managing the test result can be performed. For example, in Figure 7 the example, when the "download" button is interacted with by the first user, the "download" button can provide the test result and the information associated therewith (e.g., test log, etc.) to the UE associated with the first user. Moreover, when the "refer to test log" button is interacted with by the first user, the "refer to test log" button can cause at least one processor to present the test log (e.g., in a pop-up window) to the first user. Moreover, when the "end" button is interacted with by the first user, the "end" button can enable the first user to end the current process (e.g., close the GUI 700, return the first user to the previous page of the GUI 700, etc.). It is understandable that the GUI 700 can include any other suitable interactive elements associated with any other suitable actions without departing from the scope of the present disclosure.

[0107] Figure 8 Another exemplary GUI 800 representing more than one embodiment. The GUI 800 can be generated by at least one processor of a test information management system (or test management system) in a manner that presents the synchronized test information in a unique format to a second user and is presented to the second user (via the UE associated with the second user).

[0108] The components of the GUI800 can be the same as those of the (refer to Figure 7 above-mentioned) GUI700. For example, the GUI800 may further include a first part 810, which may include a description of one or more test requirements of a test case. On the other hand, the second part 820 may include the synchronized test information (i.e., one or more test requirements and one or more test results) and a plurality of interactive elements 821. Moreover, the GUI800 may also be generated and presented by at least one processor in the same manner as the method described above in this specification with reference to Figure 7 . The content of the GUI800 is different from that of the GUI700 in the following points: The test requirements are presented in a specific format in the first part 810, and the test results are presented in a specific format together with the associated test requirements in the second part 820. Therefore, for the sake of brevity, the redundant descriptions associated with the components in the GUI800 may be omitted below.

[0109] Therefore, the exemplary embodiments of the present disclosure provide a test information management system (and a method using the test information management system) that can automatically collect, process, and synchronize test information. Moreover, the test information management system can present the synchronized test information to multiple users in a presentation format suitable for each user. And the exemplary embodiments of the present disclosure enable the test information to be automatically, effectively, and efficiently synchronized and presented, thereby addressing the problems of the related art as described above.

[0110] It should be understood that the specific order or hierarchy of the function boxes in the process / flowcharts disclosed in this specification is an example of an exemplary method. It can be understood that based on design preferences, the specific order or hierarchy of the function boxes in the process / flowcharts can be reconfigured. Moreover, some function boxes can be combined, or some function boxes can be omitted. The appended method claims present the elements of the various function boxes in a exemplary order and are not intended to limit the elements of the various function boxes to the specific order or hierarchy presented.

[0111] In some embodiments, it may relate to systems, methods, and / or computer-readable media at any possible technical detail level of integration. Moreover, in this specification, as described above, one or more of the above-mentioned components can be implemented as instructions stored in a computer-readable medium and executable by at least one processor (and / or include at least one processor). The computer-readable medium may include a computer-readable non-transitory storage medium (or media) having computer-readable program instructions for causing the processor to perform actions.

[0112] A computer-readable storage medium can be a tangible device that can hold and store instructions for use by an instruction execution device. A computer-readable storage medium can be, for example, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing, but is not limited to these. A non-exhaustive list of more specific examples related to a computer-readable storage medium includes the following, namely, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM (Erasable Programmable Read Only Memory) or flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disc (DVD), a memory stick, a floppy disk, a mechanically encoded device such as a punched card or a raised structure in a groove that records instructions, and any suitable combination of the foregoing. The computer-readable storage medium used in this specification should not be construed as a transient signal itself, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagated through a waveguide or other transmission medium (e.g., an optical pulse passing through an optical fiber cable), or an electrical signal transmitted through a wire.

[0113] The computer-readable program instructions described in this specification can be downloaded from a computer-readable storage medium to various computing / processing devices, or can be downloaded to an external computer or an external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter or network interface in each computing / processing device receives the computer-readable program instructions from the network and transmits the computer-readable program instructions for storage in the computer-readable storage medium in each computing / processing device.

[0114] The computer-readable program code / instructions for performing the actions can be assembly instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuits, or source code or object code written in any combination of one or more programming languages, the one or more programming languages including object-oriented programming languages such as Smalltalk, C++, or the like, and procedural programming languages such as the "C" programming language or the like. The computer-readable program instructions can be executed entirely on the user's computer, can be partially executed on the user's computer, can be executed as a stand-alone software package, can be partially executed on the user's computer and partially on a remote computer, or can be executed entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer via any type of network including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., by using an Internet service provider via the Internet). In some embodiments, in order to perform a solution or an action, an electronic circuit including, for example, a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA) can utilize the state information of the computer-readable program instructions to personalize the electronic circuit, thereby executing the computer-readable program instructions.

[0115] The computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus for generating a machine, and as a result, the instructions executed via the processor of the computer or other programmable data processing apparatus generate a component that implements the functions / acts specified in the function box or boxes of the flowchart and / or block diagram. The computer-readable program instructions can also be stored in a computer-readable storage medium, which can direct a computer, a programmable data processing apparatus, and / or other devices to function in a particular manner, and as a result, the computer-readable storage medium storing the instructions therein comprises an article of manufacture that includes instructions for a solution that implements the functions / acts specified in the function box or boxes of the flowchart and / or block diagram.

[0116] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to generate a computer-implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other devices implement the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0117] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer-readable media according to various embodiments. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that comprises one or more executable instructions for implementing the specified logical function. The methods, computer systems, and computer-readable media may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the figures. In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may be executed in the reverse order, depending upon the functionality associated with them. It should also be noted that each block of the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

[0118] It will be apparent that the systems and / or methods described in this specification can be implemented in various forms of hardware, firmware, or a combination of hardware and software. The actual special control hardware or software code used to implement the systems and / or methods is not limiting of the implementations. Thus, it is understood that the operations and behavior of the systems and / or methods have been described herein without reference to specific software code, and that software and hardware can be designed to implement the systems and / or methods based on the description herein.

Claims

1. A test information synchronization method is a method implemented by at least one processor, the method automatically synchronizes the test information of the test, wherein: The processor performs the following processing: collecting at least one test result of said test, determining at least one test case to be associated with the at least one test result, determining at least one test requirement associated with at least one test result from among a plurality of test requirements of at least one test case, At least one of the test results having at least one of the test elements is synchronized.

2. The method according to claim 1, wherein: The synchronization of at least one of the test results with at least one of the test requirements includes generating a mapping of at least one of the test results and the determined at least one of the test requirements.

3. The method according to claim 1 or 2, wherein: The synchronization of at least one of the test results with at least one of the test requirements includes updating a mapping between at least one of the test results and the determined at least one of the test requirements.

4. The method according to claim 1 or 2, wherein: The collecting of at least one of the test results comprises: establishing communication with at least one test execution environment, collecting one or more test data from the at least one test execution environment, Information associated with the test result is extracted from the one or more test data.

5. The method according to claim 1 or 2, wherein: A determination of at least one of said test cases comprises: processing at least one of the test results to obtain at least one identification information parameter associated with at least one of the test cases, identifying at least one of the test cases based on at least one of the identification information parameters, At least one of the identification information parameters includes at least one of the following parameters: a keyword associated with at least one of the test cases, an inherent identifier ID associated with at least one of the test cases, and a tag associated with at least one of the test cases.

6. The method according to claim 1 or 2, wherein: Determination of at least one of the test elements comprises: processing at least one of the test results to obtain at least one test parameter associated with at least one of the test elements, determining the at least one test requirement from a plurality of test requirements of at least one of the test cases based on at least one of the test parameters, At least one of the test parameters includes at least one of the following parameters: a keyword associated with at least one of the test requirements, a description defining at least a part of at least one of the test requirements, and a tag associated with at least one of the test requirements.

7. The method according to claim 2, further comprising: Get information associated with more than one user. determining a presentation format based on the information of one or more of the users, Based on the mapping and the presentation format, the synchronized test information is presented to more than one of the users.

8. The method according to claim 7, wherein: The presentation of the synchronized test information includes: generating a first graphical user interface GUI based on the mapping and the presentation format, presenting the first GUI to a first user, The presentation format is a universal format.

9. The method according to claim 8, wherein: The presentation of the synchronized test information further includes: generating a second GUI based on the mapping and the presentation format, presenting the second GUI to a second user, The presentation format is a unique format.

10. The method according to claim 1 or 2, wherein: The testing includes testing of software of a vehicle system, the software being provided with a virtual electronic control unit ECU.

11. A test information synchronization system is a system for automatically synchronizing test information of a test, wherein: The system has: a storage memory storing instructions; and at least one processor, At least one of the processors is configured to execute the instructions to: collecting at least one test result of said test, determining at least one test case to be associated with at least one of the test results, determining at least one test requirement associated with at least one test result from among a plurality of test requirements of at least one test case, At least one of the test results having at least one of the test elements is synchronized.

12. The system according to claim 11, wherein: At least one of the processors is configured to execute the instructions to generate a mapping of at least one of the test results and the determined at least one of the test elements, thereby synchronizing at least one of the test results with the at least one of the test elements.

13. The system according to claim 11 or 12, wherein: At least one of the processors is configured to execute the instructions to update a mapping between at least one of the test results and at least one of the determined test elements, thereby synchronizing at least one of the test results with at least one of the test elements.

14. The system according to claim 11 or 12, wherein: At least one of the processors is configured to execute the instructions to: establishing communication with at least one test execution environment, Collecting one or more test data from at least one of the test execution environments, extracting information associated with the test result from one or more of the test data, At least one of said test results is thereby collected.

15. The system according to claim 11 or 12, wherein: At least one of the processors is configured to execute the instructions to: processing at least one of the test results to obtain at least one identification information parameter associated with at least one of the test cases, identifying at least one of the test cases based on at least one of the identification information parameters, thereby determining at least one of said test cases, At least one of the identification information parameters includes at least one of the following parameters: a keyword associated with at least one of the test cases, an inherent identifier ID associated with at least one of the test cases, and a tag associated with at least one of the test cases.

16. The system according to claim 11 or 12, wherein: At least one of the processors is configured to execute the instructions to: processing at least one of the test results to obtain at least one test parameter associated with at least one of the test elements, determining at least one of the test requirements from a plurality of test requirements of at least one test case based on at least one of the test parameters, At least one of the test elements is determined thereby, At least one of the test parameters includes at least one of the following parameters: a keyword associated with at least one of the test requirements, a description defining at least a part of at least one of the test requirements, and a tag associated with at least one of the test requirements.

17. The system of claim 12, wherein: At least one of the processors is further configured to execute the instructions to: Get information associated with more than one user. determining a presentation format based on the information of the one or more users, Based on the mapping and the presentation format, the synchronized test information is presented to the one or more users.

18. The system of claim 17, wherein: At least one of the processors is configured to execute the instructions to: generating a first graphical user interface GUI based on the mapping and the presentation format, presenting the first GUI to a first user, Thus, the synchronized test information is presented. The presentation format is a universal format.

19. The system of claim 18, wherein: At least one of the processors is further configured to execute the instructions to: generating a second GUI based on the mapping and the presentation format, presenting the second GUI to a second user, Thus, the synchronized test information is presented. The presentation format is a unique format.

20. The system according to claim 11 or 12, wherein: The testing includes testing of the vehicle system's software, The software includes a virtual electronic control unit ECU.

Images