System and method for automatically synchronizing test information

Abstract

To provide a system, method, and device for automatically synchronizing test information of a test for testing a software of an embedded system.SOLUTION: A method for automatically synchronizing test information of testing may be implemented by at least one processor and may include the steps of: collecting at least one test result of the testing; determining at least one test case associated with the at least one test result; determining, from among a plurality of test requirements of the at least one test case, at least one test requirement associated with the at least one test result; and synchronizing the at least one test result having the at least one test requirement.SELECTED DRAWING: Figure 1

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 necessary to ensure that the software functions as intended, meets specified requirements, and operates 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 the software is deployed to an actual system.

[0003] As software includes complex features and / or needs to interact with other software, the testing of the software can become complex and involve multiple procedures and users / stakeholders. For example, in the context of development related to vehicle-related features in a vehicle system such as lane change assistance, mobile smart keys, and the like, multiple electronic control units (ECUs) can be developed to perform the intended features and interact with each other.

[0004] For example, each of a plurality of 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), 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 vendor). As another example, the 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, testing of the first ECU requires the involvement of the hardware.

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

[0006] Nevertheless, in the related art, especially when testing involves a significant number of test artifacts (e.g., ECUs developed by different users) and / or a significant number of users, the associated users are located in different geographical locations (which can cause communication delays due to time zone differences, etc.) and / or the associated users have different levels of technical background, it is overly difficult to ensure that all testing information is timely and consistently synchronized.

[0007] Furthermore, in the related art, the process of synchronizing test results for specific test cases and corresponding test requirements often requires manual intervention by users, which can lead to human errors, delays, and reduced productivity. For example, a user performing testing (e.g., the aforementioned third user) may prepare the test results in a machine-readable format and then manually collect information or data related to the test results (such as test logs, metadata, etc.) to map the test results to the corresponding test cases and associated test requirements, review the data, and then may need to further process the data.

[0008] Furthermore, in the related art, especially when the number of users involved in testing is extremely large, it is difficult to appropriately present test information to all users associated with the testing. For example, the test information may be prepared to include a significant amount of technical details, which may not be understandable by users without sufficient technical background. Conversely, the test information may be prepared to include little technical detail and only general information, which may not be beneficial to users with sufficient technical background who want to examine the test information in detail.

[0009] Considering the above, the test information management methods and processes in the related art are time-consuming, ineffective, and burdensome to users. As a result, it is (if not impossible) overly difficult to ensure that all test information is timely, consistent, and synchronized. Therefore, software testing in the related art can be time-consuming, inefficient, and may delay software development. SUMMARY OF THE INVENTION

[0010] Exemplary embodiments consistent with the present disclosure provide a method and a system for efficiently and effectively managing test information for testing. Specifically, exemplary embodiments of the present disclosure provide a system, a method, a device, or the like that efficiently and effectively synchronizes and presents test information. And exemplary embodiments of the present disclosure enable test information to be timely and consistently synchronized, 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 for testing may be provided. The method may be implemented by at least one processor. The processor may collect at least one test result of the testing, 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 at least one test result having the at least one test requirement. The testing may include testing software of a vehicle system, and the software may include a virtual electronic control unit (ECU).

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

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

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

[0015] According to an embodiment, the determination of at least one test requirement may include processing 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 at least one test case based on the at least one test parameter. The at least one test parameter may include at least one of a keyword associated with the at least one test requirement, a description defining at least a part of the at least one test requirement, and a tag associated with the at least one test requirement.

[0016] According to an embodiment, the processor may further include obtaining information associated with one or more users, determining a presentation format based on the information of the one or more users, and presenting synchronized test information to the one or more users 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. Further, 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 testing may be provided. The system may include a memory storage for storing instructions and at least one processor communicatively connected to the memory storage. The at least one processor is configured to execute instructions to collect at least one test result of testing, 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 at least one test result having the at least one test requirement. The testing may include testing 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 instructions to synchronize at least one test result having the at least one test requirement by generating a mapping of the at least one test result and the determined at least one test requirement. Further or alternatively, the at least one processor is configured to execute instructions to synchronize at least one test result having the at least one test requirement by updating a mapping of the at least one test result and the determined at least one test requirement.

[0019] According to an embodiment, the at least one processor may be configured to execute instructions to establish communication with at least one test execution environment, collect one or more test data from the at least one test execution environment, and extract information associated with the test result from the one or more 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, obtain at least one identification information parameter associated with at least one test case, and identify at least one test case based on the at least one identification information parameter, thereby determining at least one test case. The at least one identification information parameter may include at least one of a keyword associated with the at least one test case, a unique identifier (ID) associated with the at least one test case, and a tag associated with the 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, obtain at least one test parameter associated with at least one test requirement, and 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, thereby determining at least one test requirement. The at least one test parameter comprises at least one of a keyword associated with the at least one test requirement, a description defining at least a part of the at least one test requirement, and a tag associated with the at least one test requirement.

[0022] According to an embodiment, at least one processor is further 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 synchronized test information to the one or more users based on the mapping and the presentation format. The at least one processor may be configured to present the synchronized test information by executing instructions to generate a first graphical user interface (GUI) based on the mapping and the presentation format and presenting the first GUI to a first user. Further, the at least one processor may be further configured to present the synchronized test information by executing instructions to generate 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.

[0023] Additional aspects are described in part in the following description, become apparent in part from the description, or may be realized by practice of the presented embodiments of the disclosure.

Brief Description of the Drawings

[0024] The features, advantages, and significance of the preferred embodiments of the present disclosure are described below with reference to the accompanying drawings, in which like reference numerals indicate like elements.

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

[0025] The following detailed description of the preferred embodiments refers to the accompanying drawings. The above disclosure provides examples and explanations, but is not intended to be comprehensive or to limit the implementation aspects to the exact forms disclosed. Modifications and variations are possible in view of the above disclosure or may be obtained from the implementation of the implementation aspects. Furthermore, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, in the flowcharts and descriptions of operations provided below, one or more operations may be omitted, one or more operations may be added, one or more operations may be performed (at least partially) simultaneously, and the order of one or more operations may be switched.

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

[0027] Elements, acts, or instructions used in this specification should not be construed as important or essential unless specifically described otherwise. Also, the articles "a" and "an" as used in this specification are intended to include one or more items and may be used interchangeably with "one or more." When only one item is intended, the term "one" or similar terms are used. Also, the terms "has," "have," "having," "include," "including," or the like as used in this specification are intended to be open-ended terms. Further, the phrase "based on" is intended to mean "at least partially based on" unless specifically stated otherwise. Further, 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.

[0028] 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.

[0029] Furthermore, the features, advantages, and characteristics described in this disclosure may be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize, in view of the description herein, that the disclosure may be practiced without one or more of the specific features or advantages particular to a given embodiment. In other instances, additional features and advantages may be recognized in a given embodiment that may not be present in all embodiments of the disclosure.

[0030] In addition, the term "vehicle" or the like as used herein may refer to any powered and / or mechanical machine capable of transporting or transferring people and / or goods, such as a passenger car, a truck, a motorcycle, a bus, a bicycle, a moving scooter, and the like.

[0031] The terms "testing information", "test information", and the like as described herein may refer to information associated with tests for testing software associated with a vehicle system. Such information may include information on one or more test requirements, information on one or more testing cases, information on one or more testing results, and / or any other suitable information involved in testing.

[0032] The terms "test artifact", "testing artifact", and the like as described herein 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, emulated 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.

[0033] Exemplary embodiments consistent with the present disclosure provide a method, system, and apparatus for efficiently and effectively managing test information for testing. Specifically, exemplary embodiments of the present disclosure provide a system, method, device, or the like for efficiently and effectively synchronizing and presenting test information.

[0034] According to an embodiment, a system, a method, or the like provided by an exemplary embodiment can automatically collect one or more test results, automatically determine test cases and test requirements associated with the one or more test results, and automatically synchronize the one or more test results with corresponding test requirements. Further, a system, a method, or the like provided by an exemplary embodiment can automatically determine an appropriate presentation format according to user information, and present the synchronized test information to one or more users according to the appropriate presentation format. The test information can be associated with a test of one or more software of one or more vehicle systems, for example, testing one or more in-vehicle ECUs.

[0035] And, the exemplary embodiments of the present disclosure enable test information to be timely, consistently synchronized, and enable the synchronized test information to be effectively and efficiently presented to users with different levels of technical backgrounds. Thus, software testing can be performed and managed more efficiently, the burden on users can be significantly reduced, and the time required to develop software can be significantly reduced.

[0036] It is assumed that the features, advantages, and importance of the exemplary embodiments described above in this specification are merely a part of the present disclosure, not intended to be comprehensive, nor intended to limit the scope of the present disclosure. Further explanations of the features, components, configurations, operations, and implementation manners of the exemplary embodiments of the present disclosure, as well as the associated technical advantages and importance, are provided below.

[0037] FIG. 1 shows a block diagram of an exemplary system architecture 100 for managing test information associated with tests for testing software, according to one or more embodiments. According to an embodiment, the software may include one or more in-vehicle electronic control units (ECUs), such as a physical ECU, an emulated ECU, a virtualized ECU, or a combination thereof. As shown in FIG. 1, the system architecture 100 may include a test information management system 110, a plurality of user devices (UEs) 120-1 to 120-N, a plurality of nodes 130-1 to 130-N, and a network 140.

[0038] Generally, the test information management system 110 may be communicatively connected to the plurality of UEs 120-1 to 120-N and the plurality of nodes 130-1 to 130-N via the network 140, and may be configured to interact with the plurality of UEs 120-1 to 120-N and the plurality of nodes 130-1 to 130-N to manage test information for one or more associated users. An explanation of exemplary components that may be included in the test information management system 110 is provided below with reference to FIG. 2, and an explanation of associated operations and use cases is provided below with reference to FIGS. 3 to 8.

[0039] Each of the plurality of UEs 120-1 to 120-N may include one or more machines, devices, or the like that can receive, generate, store, process, and / or provide information when utilized by an associated user. For example, one or more of the plurality of UEs 120-1 to 120-N may be associated with one or more users involved in software testing, and may include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server, etc.), a mobile device (e.g., a smartphone, etc.), a wearable device (e.g., a pair of smart glasses or a smartwatch), a SIM-based device, or any other suitable device.

[0040] The plurality of UEs 120-1 to 120-N can be used by one or more associated users 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 an associated UE to 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 use the test information management system 110 to obtain (e.g., view, download, etc.) information associated with one or more test results.

[0041] According to an embodiment, at least some of the plurality of UEs 120-1 to 120-N can be located at different geographical locations. For example, a first portion of the plurality of UEs 120-1 to 120-N can be used by a first user (e.g., a business manager) having a first role, and the first user can be located at a first location, while a second portion of the plurality of UEs 120-1 to 120-N can be used 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.

[0042] On the other hand, each of the plurality of 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 the like with respect to information and data associated with testing.

[0043] According to an embodiment, at least a part of the plurality of nodes 130-1 to 130-N may be configured to host, deploy, store, provide, or the like, one or more test artifacts or components. For example, a part of the plurality of nodes 130-1 to 130-N may include a device or equipment, and the device or equipment may be used to build, store, execute, simulate, execute, or the like, one or more computer-executable software applications, such as one or more virtualized ECUs of a vehicle system, one or more emulated ECUs, and / or any other suitable software-based components (such as a vehicle model, a data communication module (DCM) model, a heating, ventilation, and air conditioning (HVAC) model, etc.). As another example, a part of the plurality of nodes 130-1 to 130-N may include or be communicably connected to one or more hardware components, such as one or more fully developed physical ECUs, one or more partially developed physical ECUs, one or more vehicle hardware components (such as a powertrain, an engine, etc.), or the like.

[0044] According to an embodiment, at least a part of the plurality of nodes 130-1 to 130-N may be associated with one or more test execution environments. For example, the said part of the nodes may have at least one software-based test execution environment (such as 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 communicably connected (such as a wired connection, a wireless connection, etc.) to or deployed on at least one hardware-based test execution environment (such as a hardware-in-the-loop (HIL) test environment, etc.).

[0045] Furthermore, at least some of the plurality of nodes 130-1 to 130-N may include one or more storage media such as a server or a server cluster, and the storage media may be configured to store, disclose, or perform similar operations on one or more data or information provided by the test information management system 110, one or more of the plurality of UEs 120-1 to 120-N, and / or another part of the plurality of nodes 130-1 to 130-N.

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

[0047] According to an embodiment, one or more of the plurality of nodes 130-1 to 130-N may include one or more interfaces, each of which may be configured to communicably connect the associated node 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 programming interface, an application programming interface (API), etc.), and / or the like.

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

[0049] Network 140 may include one or more wired and / or wireless networks, and the wired and / or wireless networks 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, 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, an optical fiber-based network, or the like, and / or a combination of these types or other types of networks.

[0050] According to an embodiment, Network 140 may include a virtual network, and the virtual network may include one or more physical network components (e.g., Ethernet, a WiFi module, telecommunications network hardware, etc.) on which one or more virtualized network functions (e.g., a control area network (CAN) bus, etc.) are implemented.

[0051] FIG. 2 shows a block diagram of exemplary components of a test information management system 200 according to one or more embodiments. The test information management system 200 may be similar to the test information management system 110 of FIG. 1.

[0052] As shown in FIG. 2, 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, without departing from the scope of the present disclosure, the test information management system 200 may include more or fewer components than those shown, and / or the components included therein may be arranged in any manner different from those shown.

[0053] The communication interface 210 may include a component such as a transceiver (e.g., a transceiver, separate receivers and transmitters, etc.) that enables 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 a plurality of UEs (e.g., UEs 120-1 to 120-N in FIG. 1, etc.) and a plurality of nodes (e.g., nodes 130-1 to 130-N in FIG. 1, 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.

[0054] 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, and the CAN bus may be configured to communicatively connect components of the test information management system 200 (e.g., the storage 220, the processor 230, etc.) to a plurality of UEs (e.g., UEs 120-1 to 120-N) and a plurality of nodes (e.g., nodes 130-1 to 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 (e.g., a virtualized CAN bus, etc.), or the like.

[0055] 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 and provide the information to the processor 230 for further processing and / or provide the information to the storage 220 for storage. For example, the communication interface 210 may receive one or more user inputs specifying one or more test requirements (e.g., a test scenario, a test case, a test plan, a test cycle, etc.) from a plurality of UEs and provide the user input to the processor 230 and / or the storage 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 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) to a plurality of UEs.

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

[0057] Additionally or alternatively, the storage 220, along with a corresponding drive, 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 disk (CD), a digital versatile disk (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium.

[0058] According to an embodiment, the storage 220 may be configured to store information utilized by the processor 230 to facilitate automatic synchronization of test information. For example, the storage 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 involved in testing, store one or more test results, and the like.

[0059] At least one processor 230 may include one or more processors that are programmable 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., such as storage 220) to thereby perform one or more acts or one or more operations described herein. An explanation of exemplary operations that can be performed by the processor 230 is provided below with reference to FIGS. 3 and 6.

[0060] 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 or the like). Further, the processor 230 may be implemented in 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.

[0061] FIG. 3 shows a flowchart of an exemplary method 300 for automatically synchronizing test information of a test for testing software according to one or more embodiments. When executing computer-executable instructions stored in at least one memory storage (e.g., storage 220), one or more operations of the method 300 may be performed by at least one processor (e.g., processor 230) of the test information management system of the exemplary embodiment. The software to be tested may include an in-vehicle electronic control unit (ECU) associated with a vehicle system and / or any other software component.

[0062] Generally, a test information management system (or at least one processor associated therewith) may be configured to collect one or more test results, determine one or more test cases associated with the one or more collected test results, and synchronize one or more test results having one or more test requirements of the one or more test cases. The description of the operations in FIG. 3 is provided below along with the description of the exemplary use cases in FIGS. 4-5.

[0063] FIG. 4 shows an exemplary test case and associated test requirements according to one or more embodiments. In this exemplary use case, the test case with ID "#ABC" and ID "#ABC" includes a plurality of test requirements. The test requirements are associated with a test scenario that tests the functions of the ECU (shown as "Function A" and "ECU A" respectively in FIG. 4), while the testing involves testing a service (shown as "Service E"). As shown in FIG. 4, the functional characteristics and the content of the test scenario are specified in a general format (further described below with reference to FIGS. 6 and 7). In addition to the test scenario (as shown in FIG. 4), it can be understood that other test requirements such as test plans, test executions, test configurations, test cycles, and the like can be specified in a similar manner.

[0064] The test case in FIG. 4 can be specified or created by a first user through the use of a test information management system and / or a test management system separate from the test information management system. Once the test case and associated test requirements are specified, testing can be executed based thereon. In this regard, testing can include a plurality of tasks such as tasks associated with hardware-based testing and / or tasks associated with software-based testing, each of which can be assigned to a respective test execution environment. For example, tasks associated with hardware-based testing are assigned to one or more hardware-based test execution environments (such as a HIL test environment, etc.), while tasks associated with software-based testing are assigned to one or more software-based test execution environments (such as a SIL test environment, etc.). Thus, the testing of a plurality of test requirements can be performed in a plurality of test execution environments, and a plurality of test results (each associated with a test requirement) can be generated.

[0065] Referring back to FIG. 3, in operation S310, at least one processor of the test information management system may be configured to collect at least one test result. Specifically, at least one processor may establish communication (via the communication interface of the test information management system) with at least one node associated with at least one test execution environment, obtain test data from the at least one node, and extract information / data associated with the at least one test result from the test data. The information associated with the at least one test result may 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.), test log information, test images (e.g., screenshots, etc.), and the like.

[0066] According to an embodiment in which multiple tests are performed in multiple test execution environments, at least one processor may establish communication with multiple nodes associated with the multiple test execution environments, simultaneously or sequentially, in a manner similar to that described above, and collect multiple test results therefrom. An illustrative use case associated therewith is provided below with reference to FIG. 5.

[0067] According to an embodiment, at least one processor of the test information management system may be configured to communicate continuously (or periodically) with the node associated with the test execution environment so as to collect test results continuously (or periodically) from the node in real time or near real time.

[0068] In view of the above, at least one processor of the test information management system may be configured to collect test results according to test requirements, and thus, without having to wait for the completion of testing for all test requirements, as soon as the test results become available, it may be possible to process the test results and synchronize the test results having respective test requirements.

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

[0070] Specifically, at least one processor may be configured to process the collected test result to obtain at least one identification information parameter associated with at least one test case. In this regard, the "identification information parameter" described herein may refer to a parameter that can be utilized by at least one processor to identify a target test case. The identification information parameter associated with at least one test case may include one or more of a keyword associated with at least one test case, a unique identifier (ID) associated with at least one test case, the name or label of at least one test case, and a custom tag associated with at least one test case.

[0071] At least one processor may be configured to process the at least one obtained 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 may perform natural language processing (NLP) operations to extract one or more keywords of at least one test case from the test result, perform a search operation to determine the ID and / or custom tag of at least one test case from the test result, and may do the same kind of things.

[0072] When at least one identification information parameter is obtained, at least one processor may 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, assuming that at least one processor obtains the ID of "#ABC" from the test result, the at least one processor may search for any test case having the same ID of "#ABC" from among a plurality of test cases stored in a storage (e.g., storage 220) and / or managed by a test management system. It is assumed that the at least one processor may identify at least one test case having other identification information parameters (e.g., name, label, tag, etc.) in a similar manner.

[0073] 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 on the at least one identified test case. For example, at least one processor may obtain the at least one identified test case from the storage of the test information management system. As another example, at least one processor may obtain the at least one identified test case from the test management system (e.g., via one or more API calls).

[0074] In some implementations, it can be understood that at least one processor may be configured to perform operation S320 before operation S310 without departing from the scope of the present disclosure. For example, at least one processor may first receive at least one test case, determine parameters associated with one or more test requirements of the at least one test case, and collect one or more test results associated with the one or more test requirements based on the determined parameters.

[0075] Furthermore, in operation S330, at least one processor of the test information management system can be configured to determine 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.

[0076] Specifically, at least one processor can be configured to process at least one collected test result to obtain at least one test parameter. In this regard, the "test parameter" described herein can refer to a parameter that can be used by at least one processor to identify a target test requirement. The test parameter can include one or more of a keyword associated with at least one test requirement, a description defining the test requirement, and a custom tag associated with at least one test requirement. At least one processor can be configured to obtain one or more test parameters in a manner similar to the manner of obtaining one or more identification information parameters (e.g., performing NLP operations, performing search operations, etc.).

[0077] Upon determining at least one test requirement, method 300 can proceed to operation S340, where at least one processor of the test information management system can be configured to synchronize at least one test result having at least one test requirement. According to an embodiment, at least one processor can synchronize at least one test result having at least one test requirement by generating a mapping of at least one test result and at least one test requirement. According to an embodiment where the mapping was generated in a previous operation, at least one processor can obtain the generated mapping (from, for example, the storage of the test information management system) and update the generated mapping with the latest test result. An illustrative description of the mapping is provided below with reference to FIG. 5.

[0078] 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 can be configured to present the synchronized information to one or more users. For example, at least one processor can generate at least one GUI including mapping information based on the mapping of at least one test result and at least one test requirement, and present at least one GUI to the associated user by sending at least one GUI to at least one UE associated with the user. Alternatively or additionally, at least one processor can provide the mapping to the test management system, and then the test management system can be configured to generate and present at least one GUI to the user. According to an embodiment, at least one GUI can be generated based on user information (e.g., the role of the user, etc.). An illustration of an exemplary GUI including the synchronized information is provided below with reference to FIGS. 7 and 8.

[0079] Hereinafter, an illustration of an exemplary use case of method 300 is provided with reference to FIG. 5. Generally, a test information management system 510 (or at least one processor associated therewith) can be configured to collect a plurality of test results 520, determine and obtain a test case 530 associated with the collected test results, and 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 can be similar to the test information management system described herein with reference to other figures.

[0080] Test result 520 may include test results 1 to 4, each of which may be associated with the test requirements of a test case (e.g., the test case in FIG. 4). At least a part of test results 1 to 4 may be associated with testing performed in different test execution environments and may be collected by the test information management system 510 (or at least one processor associated therewith) from different nodes. 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 therefrom.

[0081] When obtaining at least one of test results 1 to 4, the test information management system 510 (or at least one processor associated therewith) may 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) may perform operation S320, obtain an identification information parameter from the test result, determine at least one test case associated with at least one test result (based on the identification information parameter), and then obtain information of at least one test case. For example, when collecting at least one of test results 1 to 4, the test information management system 510 (or at least one processor associated therewith) may be configured to obtain at least one identification information parameter from the collected test result. In the exemplary use case of FIG. 5, test results 1 and 2 include keywords of a test case (shown as "ABC" in FIG. 5), and test results 3 and 4 include the ID of a test case (shown as "#ABC" in FIG. 5). Based on the identification information parameter, at least one processor may determine that the collected test result is associated with a test case having a name / ID / description associated with the ID of "#ABC" or the keyword of "ABC". Accordingly, at least one processor may be configured to obtain information of the determined test case.

[0082] In some implementation manners, the test information management system 510 (or at least one processor associated therewith) can 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 it can be understood that it can be configured to collect the test results associated with the test case.

[0083] After obtaining the test results and the information of the associated test cases, the test information management system 510 (or at least one processor associated therewith) can be configured to associate the obtained test results with the corresponding test requirements of the test cases. Specifically, the test information management system 510 (or at least one processor associated therewith) performs operation S330, obtains test parameters from the test results, and can determine at least one test requirement associated with at least one test result (based on the test parameters) from among a plurality of test requirements of the test case. For example, in the exemplary use case of FIG. 5, the test case 530 includes a plurality of test requirements 1 to N, each of which has an associated parameter, and the test results 1 and 2 include keywords defining their respective test requirements, while the test results 3 and 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.

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

[0085] When synchronizing test information (e.g., test results and information on corresponding test requirements), the test information management system 510 (or at least one processor associated therewith) may be configured to present the synchronized test information to one or more users. An explanation of an exemplary method associated therewith is presented below with reference to FIG. 6, and an explanation of an exemplary GUI associated therewith is presented below with reference to FIGS. 7 and 8.

[0086] FIG. 6 shows a flowchart of an exemplary method 600 for presenting synchronized test information according to one or more embodiments. One or more operations of method 600 may be performed by at least one processor of the test information management system and / or may be performed by a system / device different from the test information management system (e.g., a test management system, etc.).

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

[0088] Upon obtaining the mapping information, method 600 may proceed to operation S620, where information of one or more users associated with the test case or testing is obtained. For example, a test information management system (or at least one processor associated therewith) may determine one or more users associated with the test case or testing based on the test case information (e.g., identification information parameters such as test case ID, keywords, tags, etc.) included in the mapping information, and then subsequently obtain the information of the one or more users (e.g., from storage 220, a node hosting user information, etc.). The user information may include the user's role, position, job description, past presentation information, and / or the like. In an embodiment where operation S620 is performed by the test management system, it is assumed that the test management system may be configured to obtain user information in a similar manner.

[0089] Upon obtaining the user information, method 600 may proceed to operation S630, where the presentation format associated with the user is determined. For example, a test information management system (or at least one processor associated therewith) may determine a presentation format including information suitable for the user based on the user information (e.g., the user's role / persona / job information).

[0090] According to an embodiment, the presentation format may include a general format or a specific format. In this regard, the term "general format" as described herein may refer to any format of a presentation that includes a description that can be understood by a user without (or with limited) a specific level of technical background. Conversely, the term "specific format" as described herein may refer to any format of a presentation that includes a description that can be understood by a user with a specific level of technical background. For example, a specific format may refer to programming code or any other computer-executable language that can be understood by a user with knowledge of a specific type of programming code or system. In an embodiment where operation S630 is performed by a test management system, it is assumed that the test management system may be configured to determine the presentation format in a similar manner.

[0091] Upon determining the presentation format, method 600 may proceed to operation S640, where synchronized test information is presented. For example, a 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 present the GUI to the user. The generated GUI may present the synchronized test information in a presentation format associated with the user. In an embodiment where operation S640 is performed by a test management system, it is assumed that the test management system may be configured to present the synchronized test information in a similar manner.

[0092] For this purpose, the synchronized test information can be presented to the user efficiently and effectively. Specifically, the GUI presented to the user may include appropriate content that is suitable for the user considering the level of the user's technical background. An exemplary description of a GUI generated according to the general format is provided below with reference to FIG. 7, and an exemplary description of a GUI generated according to the specific format is provided below with reference to FIG. 8.

[0093] FIG. 7 shows an exemplary GUI 700 according to one or more embodiments. The GUI 700 may be generated by at least one processor of a test information management system (or test management system) to present synchronized test information to a first user in a general format and presented to the first user (via a UE associated with the first user).

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

[0095] According to an embodiment, one or more test requirements in the first portion 710 may be presented in the form of one or more interactive elements (e.g., selectable text, etc.), such that each time the first user interacts with an intended 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 portion 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 the example of FIG. 7, the test requirement "the set state is a warning" is presented in italic format to notify the user that the requirement has a different test result (e.g., failure) than other test requirements (e.g., success).

[0096] Furthermore, in the example of FIG. 7, one or more test results are presented with respective icons in the second portion 720 (e.g., a check icon defines a "success" test result, an x icon defines a "failure" test result, etc.). Alternatively or in addition to the icon-based presentation, the test results can be presented in the form of a text-based presentation (e.g., the terms "success", "failure", or the like can be presented), a color-based presentation (e.g., green indicates a "success" test result, red indicates a "failure" test result, etc.). It can be understood that the test results can be presented in these forms.

[0097] Furthermore, the test requirements can be presented with one or more interactive elements (e.g., selectable text, buttons, etc.), such that upon interaction by the first user, at least one processor can present more details associated with the test results. For example, in the example of FIG. 7, the test requirement "the set state is a warning" is presented with selectable text "See More Details". Determining user interaction with the selectable text, at least one processor can step back the GUI 700 and present further information about the associated test results (e.g., the reason for failure, etc.) (e.g., in a pop-up window, etc.).

[0098] In addition, each of the plurality of interactive elements 721 can perform one or more operations for managing test results when interacted with by the first user. For example, in the example of FIG. 7, the "Download" button can provide the test results and information associated therewith (e.g., test logs, etc.) to the UE associated with the first user when interacted with by the first user. Further, the "View Test Log" button can configure at least one processor to present the test log to the first user (e.g., in a pop-up window, etc.) when interacted with by the first user. Further, the "End" button can enable the first user to end the current process (e.g., close the GUI 700, redirect the first user to the previous page of the GUI 700, etc.) when interacted with by the first user. It can be understood that the GUI 700 can include any other suitable interactive elements associated with any other suitable operations without departing from the scope of the present disclosure.

[0099] FIG. 8 shows another exemplary GUI 800 according to one or more embodiments. The GUI 800 is generated by at least one processor of a test information management system (or test management system) to present synchronized test information in a format specific to the second user and can be presented to the second user (via the UE associated with the second user).

[0100] The components of GUI800 can be the same as those of GUI700 (described above with reference to FIG. 7). For example, GUI800 can also include a first portion 810 that can include a description of one or more test requirements of a test case, while the second portion 720 can include synchronized test information (i.e., one or more test results along with one or more test requirements) and a plurality of interactive elements 821. Further, GUI800 can also be generated and presented by at least one processor in a manner similar to the methods described hereinabove with reference to FIG. 7. The content of GUI800 is different from GUI700 in that the test requirements are presented in a specific format in the first portion 810 and the test results are presented along with the test requirements that are associated in a specific format in the second portion 720. Accordingly, redundant descriptions associated with the components in GUI800 can be omitted hereinafter for the sake of brevity.

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

[0102] It is understood that the specific order or hierarchy of the blocks in the process / flow diagrams disclosed herein is an example of an exemplary approach. It is understood that the specific order or hierarchy of the blocks in the process / flow chart can be rearranged based on design preferences. Further, some blocks can be combined or omitted. The appended method claims present the elements of the various blocks in an exemplary order and are not meant to be limited to the specific order or hierarchy presented.

[0103] Some embodiments may relate to systems, methods, and / or computer-readable media at any possible level of integration of technical details. Further, as described above herein, one or more of the above-described components may be implemented as instructions stored in a computer-readable medium and executable by at least one processor (and / or may 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 a processor to perform operations.

[0104] A computer-readable storage medium may be a tangible device that can hold and store instructions for use by an instruction execution device. A computer-readable storage medium may be, for example, but is not limited to, 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. A non-exhaustive list of more specific examples of the computer-readable storage medium includes the following, namely, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM 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 raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. As used herein, a computer-readable storage medium should not be construed to be a transient signal itself, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating 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.

[0105] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to respective computing / processing devices, or can be downloaded from 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 comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface within each computing / processing device receives the computer-readable program instructions from the network and transfers the computer-readable program instructions for storage on a computer-readable storage medium within each respective computing / processing device.

[0106] The computer-readable program code / instructions for performing the operations 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, where the one or more programming languages include object-oriented programming languages such as Smalltalk, C++, or the like, and procedural programming languages such as the "C" programming language or similar programming languages. The computer-readable program instructions can be executed entirely on the user's computer, partially on the user's computer, executed as a stand-alone software package, executed partially on the user's computer and partially on a remote computer, or executed entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network including a local area network (LAN) or wide area network (WAN), or a connection to an external computer can be made (e.g., through the Internet using an Internet service provider). In some embodiments, for example, an electronic circuit including a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA) can execute the computer-readable program instructions by personalizing the electronic circuit using the state information of the computer-readable program instructions to perform an aspect or operation.

[0107] The computer-readable program instructions may be provided to a processor of a general purpose computer, a special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions executed via the processor of the computer or other programmable data processing apparatus create means for implementing the functions / acts specified in the flowchart and / or block or blocks of the block diagram. The computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and / or other devices to function in a particular manner, such that the computer-readable storage medium storing instructions therein comprises a manufactured article including instructions which implement the aspects of the functions / acts specified in the flowchart and / or block or blocks of the block diagram.

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

[0109] 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 diagram may represent a module, segment, or portion of instructions comprising 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 compared to those depicted in the figures. In some alternative implementations, the functions recited in the blocks may occur without regard to the order and relationship shown in the figures. For example, two blocks shown in succession may in fact be executed simultaneously or substantially simultaneously, or the blocks may be executed in the reverse order depending on the relevant functions. It should also be noted that each block of the block diagrams and / or flowchart diagrams, and combinations of blocks of the block diagrams and / or flowchart diagrams, can be implemented by a dedicated hardware-based system that performs the specified functions or acts or executes a combination of dedicated hardware and computer instructions.

[0110] It will be apparent that the systems and / or methods described herein may be implemented in various forms of hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement the systems and / or methods is not a limitation of the implementation. Accordingly, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, and it is understood that software and hardware can be designed based on the description herein to implement the systems and / or methods.

Claims

1. 1. A method for automatically synchronizing test information for testing, the method comprising: The processor, collecting at least one test result of said testing; determining at least one test case associated with the at least one test result; determining at least one test requirement from among a plurality of test requirements of at least one of the test cases, the at least one test requirement being associated with at least one of the test results; Synchronizing at least one of the test results with at least one of the test requirements; method.

2. synchronizing the at least one test result with the at least one test requirement includes generating a mapping of the at least one test result and the determined at least one test requirement. The method of claim 1.

3. and synchronizing the at least one test result with the at least one test requirement includes updating a mapping of the at least one test result and the determined at least one test requirement. The method according to claim 1 or 2.

4. The collection of at least one test result includes: Establishing communication with at least one test execution environment; collecting one or more test data from the at least one test execution environment; extracting information from the one or more test data that is associated with the test results; The method of claim 1 or 2, comprising:

5. The determination of the at least one test case includes: processing at least one of said test results to obtain at least one identification parameter associated with at least one of said test cases; identifying at least one of the test cases based on at least one of the identification information parameters; Including, the at least one identification parameter comprises at least one of a keyword associated with at least one of the test cases, a unique identifier (ID) associated with at least one of the test cases, and a tag associated with at least one of the test cases. The method according to claim 1 or 2.

6. Determining the at least one test requirement comprises: processing at least one of said test results to obtain at least one test parameter associated with at least one of said test requirements; determining at least one test requirement from among a plurality of test requirements for at least one of the test cases based on the at least one test parameter; Including, the at least one test parameter comprises at least one of a keyword associated with the at least one test requirement, a description defining at least a portion of the at least one test requirement, and a tag associated with the at least one test requirement. The method according to claim 1 or 2.

7. Obtaining information associated with one or more users; determining a presentation format based on the information of one or more of the users; presenting the synchronized test information to one or more of the users based on the mapping and the presentation format; The method of claim 2 further comprising:

8. The synchronized presentation of the 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; Including, The presentation format is a universal format. The method of claim 7.

9. The synchronized presentation of the test information includes: generating a second GUI based on the mapping and the presentation format; presenting the second GUI to a second user; Further comprising: The presentation format is a specific format. The method according to claim 8.

10. The testing includes testing software of a vehicle system, the software comprising a virtual electronic control unit (ECU). The method according to claim 1 or 2.

11. 1. A system for automatically synchronizing test information for testing, the system comprising: A memory storage for storing instructions; At least one processor; wherein the at least one processor executes the instructions to collecting at least one test result of said testing; determining at least one test case associated with at least one of the test results; determining at least one test requirement from among a plurality of test requirements of at least one of the test cases, the at least one test requirement being associated with at least one of the test results; A system configured to synchronize at least one of the test results with at least one of the test requirements.

12. 12. The system of claim 11, wherein at least one of the processors is configured to execute the instructions to generate a mapping of the at least one of the test results and the determined at least one of the test requirements to synchronize the at least one of the test results with the at least one of the test requirements.

13. at least one of the processors is configured to execute the instructions to synchronize at least one of the test results with at least one of the test requirements by updating a mapping of the at least one of the test results and the determined at least one of the test requirements.

13. A system according to claim 11 or 12.

14. At least one of the processors executes the instructions to Establishing communication with at least one test execution environment; collecting one or more test data from at least one of said test execution environments; extracting information from one or more of the test data that is associated with the test results; and collecting at least one of the test results by 13. A system according to claim 11 or 12.

15. At least one of the processors executes the instructions to processing at least one of said test results to obtain at least one identification parameter associated with at least one of said test cases; identifying at least one of the test cases based on at least one of the identification information parameters; and configured to determine at least one of the test cases by the at least one identification parameter comprises at least one of a keyword associated with at least one of the test cases, a unique identifier (ID) associated with at least one of the test cases, and a tag associated with at least one of the test cases.

13. A system according to claim 11 or 12.

16. At least one of the processors executes the instructions to processing at least one of said test results to obtain at least one test parameter associated with at least one of said test requirements; determining at least one test requirement from among a plurality of test requirements for the at least one test case based on the at least one test parameter; and configured to determine at least one of the test requirements by the at least one test parameter comprises at least one of a keyword associated with the at least one test requirement, a description defining at least a portion of the at least one test requirement, and a tag associated with the at least one test requirement.

13. A system according to claim 11 or 12.

17. At least one of the processors further executes the instructions to: Obtaining information associated with one or more users; determining a presentation format based on the information of the one or more users; and configured to present the synchronized test information to the one or more users based on the mapping and the presentation format. The system of claim 12.

18. At least one of the processors executes 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; and configured to present the synchronized test information by The presentation format is a universal format.

20. The system of claim 17.

19. At least one of the processors further executes the instructions to: generating a second GUI based on the mapping and the presentation format; presenting the second GUI to a second user; and configured to present the synchronized test information by The presentation format is a specific format.

20. The system of claim 18.

20. The testing includes testing software of a vehicle system; The software comprises a virtual electronic control unit (ECU); 13. A system according to claim 11 or 12.

Images