System, method, and computer program product for viewing test case results

Abstract

The present disclosure relates to the provision of a system. Systems, methods, and computer program products are provided for viewing test case results. According to an exemplary embodiment, a system may include: a storage store storing computer executable instructions; and at least one processor communicatively coupled to the storage, the at least one processor may be configured to execute the instructions to generate a graphical user interface having at least a first portion and a second portion, where the first portion may include one or more elements of a test environment, and the second portion may include one or more elements of the test environment. The second part can comprise a log area; receiving, from a user, a selection input for selecting one of the one or more elements displayed on the first portion; and in response to reception of the selection input, displaying, in the log area, a test log associated with only one selected element among the one or more elements.

Description

Technical Field

[0001] Systems, methods, and computer program products that correspond to exemplary embodiments of this disclosure relate to vehicle software testing, and more specifically, to viewing test case results in vehicle software testing. Background Technology

[0002] In software development, software needs to be tested to ensure that it functions as expected, meets specified requirements, and reliably performs its functions in various scenarios. Software testing is an important part of the Software Development Life Cycle (SDLC). Before deploying software in a real system, testing is conducted to identify defects, errors, or bugs in the software.

[0003] Testing vehicle-related software can be performed by designing test cases that include multiple test steps and are executed within a test environment. The results of these test case executions can then be generated and viewed by users to evaluate the software.

[0004] In related technologies, the results of test case execution can be displayed as a simple pass / fail status associated with the test case and / or as a holistic log relating to all elements of the test. At this point, it is difficult for users to determine which specific test step within a test case is pass or fail, and reading through the holistic log relating to all elements of the test is a time-consuming process. Therefore, determining the specific cause of a failure is time-consuming and prone to errors. Therefore, a system is needed that allows users to view the results of test case execution and quickly and efficiently identify the specific causes of failures. Summary of the Invention

[0005] Exemplary embodiments of this disclosure test vehicle software. Therefore, exemplary embodiments of this disclosure provide a graphical user interface that allows a user to quickly view test results (i.e., test logs, statuses, charts, and similar data) related to specific elements and specific test steps of a test case at a specific point in time. Thus, the graphical user interface facilitates the analysis and identification of errors within test cases, thereby reducing the time required for such analysis and identification.

[0006] According to an exemplary embodiment, a system is provided. The system may include: a storage device storing computer-executable instructions; and at least one processor communicatively connected to the storage device, the at least one processor being configured to execute the instructions to perform the following actions: generating a graphical user interface having at least a first part and a second part, wherein the first part may include one or more elements of a test environment, and the second part may include a log area; receiving selection input from a user to select one of the elements displayed in the first part; and in response to receiving the selection input, displaying a test log associated only with the selected element in the log area.

[0007] According to an exemplary implementation, the graphical user interface may further include a third part, which may include one or more test steps of a test case and a state associated with each of the one or more test steps.

[0008] According to an exemplary implementation, one or more elements may include one or more electronic control units associated with the type of vehicle.

[0009] According to an exemplary implementation, the second part may also include a chart area, which may include a chart representing communication between more than one element during a certain period.

[0010] According to an exemplary implementation, the graphical user interface may further include a fourth part, which may include a video simulation of a simulated test environment.

[0011] According to an exemplary implementation, the graphical user interface may further include a scrubber associated with the test log in the second part and the video simulation in the fourth part, and at least one processor may also be configured to execute instructions to perform the following actions: receiving from the user a sliding input to slide the scrubber to a certain time instance; and updating the test log displayed in the log area and the video simulation displayed in the fourth part based on the time instance in response to receiving the sliding input.

[0012] According to an exemplary implementation, the fourth part may also include a comment window, and at least one processor may also be configured to execute instructions to perform the following actions: receiving comment input from the user and displaying the comment input in the comment window.

[0013] According to an exemplary implementation, a method is provided. The method may include: generating a graphical user interface having at least a first part and a second part, wherein the first part may include one or more elements of a test environment, and the second part may include a log area; receiving selection input from a user to select one of the elements displayed in the first part; and in response to receiving the selection input, displaying a test log associated only with the selected element from the one or more elements in the log area.

[0014] According to an exemplary implementation, the graphical user interface may further include a third part, which may include one or more test steps of a test case and a state associated with each of the one or more test steps.

[0015] According to an exemplary implementation, one or more elements may include one or more electronic control units associated with the type of vehicle.

[0016] According to an exemplary implementation, the second part may also include a chart area, which may include a chart representing communication between more than one element during a certain period.

[0017] According to an exemplary implementation, the graphical user interface may further include a fourth part, which may include a video simulation of a simulated test environment.

[0018] According to an exemplary implementation, the graphical user interface may further include a scrubbing bar associated with the test log in the second part and the video simulation in the fourth part, and the method may further include: receiving from the user a sliding input to slide the scrubbing bar to a time instance; and updating the test log displayed in the log area and the video simulation displayed in the fourth part based on the time instance in response to receiving the sliding input.

[0019] According to an exemplary implementation, the fourth part may also include a comment window, and the method may further include: receiving comment input from a user; and displaying the comment input in the comment window.

[0020] According to an exemplary embodiment, a non-transitory computer-readable recording medium is provided. The non-transitory computer-readable recording medium can record instructions executable by at least one processor for causing at least one processor to perform a method, the method comprising: generating a graphical user interface having at least a first portion and a second portion, wherein the first portion may include one or more elements of a test environment, and the second portion may include a log area; receiving from a user a selection input for selecting one of the elements displayed in the first portion; and, in response to receiving the selection input, displaying a test log associated only with the selected element from the one or more elements in the log area.

[0021] According to an exemplary implementation, the graphical user interface may further include a third part, which may include one or more test steps of a test case and a state associated with each of the one or more test steps.

[0022] According to an exemplary implementation, one or more elements may include one or more electronic control units associated with the type of vehicle.

[0023] According to an exemplary implementation, the second part may also include a chart area, which may include a chart representing communication between more than one element during a certain period.

[0024] According to an exemplary implementation, the graphical user interface may further include a fourth part, which may include a video simulation of a simulated test environment.

[0025] According to an exemplary implementation, the graphical user interface may further include a scrubbing bar associated with the test log in the second part and the video simulation in the fourth part, and the method may further include: receiving from the user a sliding input to slide the scrubbing bar to a time instance; and updating the test log displayed in the log area and the video simulation displayed in the fourth part based on the time instance in response to receiving the sliding input.

[0026] Additional solutions will be described in part in the following description, and may become apparent from the description or may be implemented by practicing the embodiments presented in this disclosure. Attached Figure Description

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

[0028] Figure 1A block diagram illustrating exemplary components of a vehicle software testing (VST) system with one or more implementations.

[0029] Figure 2 Exemplary components of a graphical user interface (GUI) for testing vehicle software, representing one or more implementations.

[0030] Figure 3 Exemplary constituent elements of a first part of a graphical user interface (GUI) for testing vehicle software, representing one or more embodiments.

[0031] Figure 4 Exemplary constituent elements of a third part of a graphical user interface (GUI) for testing vehicle software, representing one or more implementations.

[0032] Figure 5 A flowchart illustrating an exemplary method for testing vehicle software according to one or more implementations. Detailed Implementation

[0033] The following detailed description of exemplary embodiments is with reference to the accompanying drawings. The same reference numerals in different drawings may identify the same or identical elements.

[0034] The above disclosure provides examples and descriptions, but is not intended to be exhaustive or to limit the implementation to the exact form disclosed. Modifications and variations can be made based on the above disclosure, or can be obtained through implementation. Furthermore, one or more features or constituent elements of one embodiment can be incorporated into another embodiment (or one or more features of another embodiment) or combined with another embodiment (or one or more features of another embodiment). Moreover, it is understood that in the flowcharts and descriptions of the actions provided below, one or more actions may be omitted, one or more actions may be added, one or more actions may be performed simultaneously (at least partially), and the order of one or more actions may be changed.

[0035] It is evident that the systems and / or methods described in this specification can be implemented in various forms, including hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement the system and / or method is not a limitation of the implementation. Therefore, the operation and behavior of the system and / or method are described in this specification without reference to specific software code. It is understood that software and hardware can be designed to implement the system and / or method based on the description in this specification.

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

[0037] Unless otherwise explicitly stated, elements, actions, or instructions used in this specification should not be construed as essential or necessary. Furthermore, when used in this specification, the articles “a” and “an” refer to more than one item and can be used interchangeably with “more than one.” When referring to only one item, the term “one” or similar terms is used. Additionally, when used in this specification, the terms “has,” “have,” “having,” “include,” “including,” or similar terms imply open-ended usage. Moreover, unless otherwise explicitly stated, the phrase “based on” means “at least partially based on.” Furthermore, expressions such as “at least one of [A] and [B],” “[A] and / or [B],” or “at least one of [A] or [B]” should be understood as referring to only A, only B, or including both A and B.

[0038] It is assumed that the features, advantages, and importance of the exemplary embodiments described above in this specification are only part of this disclosure and are not intended to be exhaustive or to limit the scope of this disclosure.

[0039] The following provides further description of the features, components, structure, operation, and implementation scheme of vehicle software testing according to more than one embodiment of the present disclosure.

[0040] Exemplary system architecture

[0041] Figure 1 This is a block diagram illustrating exemplary components of a vehicle software testing (VST) system 100 with more than one implementation. The VST system 100 may include devices, systems, platforms, modules, or the like that can be configured to perform more than one action or operation to test vehicle software.

[0042] like Figure 1As shown, the VST system 100 may include at least one communication interface 110, at least one processor 120, at least one input / output component 130, and at least one memory 140. However, it will be understood that the VST system 100 may include more than [other components] without departing from the scope of this disclosure. Figure 1 The constituent elements shown may include more or fewer constituent elements and / or may be combined with Figure 1 The methods shown are configured differently.

[0043] The communication interface 110 may include at least one transceiver-type component (e.g., transceiver, separate receiver and transmitter, bus, etc.) that enables the components of the VST system 100 to communicate with each other and / or with one or more components located outside the VST system 100 via wired connection, wireless connection, or a combination of wired and wireless connection. For example, the communication interface 110 may include 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, or a similar interface.

[0044] For example, communication interface 110 can connect processor 120 to memory 140, thereby enabling them to communicate and interact with each other when performing more than one action.

[0045] According to one or more embodiments, the communication interface 110 may include one or more application programming interfaces (APIs) that enable the VST system 100 (or one or more components included in the VST system 100) to communicate with one or more software applications.

[0046] Input / output component 130 may include at least one component enabling VST system 100 to receive information and / or provide output information. In some embodiments, it is understood that input / output component 130 may include at least one input component (e.g., a touchscreen display, keyboard, keypad, mouse, button, switch, microphone, etc.) and at least one output component (e.g., a display, speaker, one or more light-emitting diodes (LEDs), etc.), and these components may be separable from each other. Further or alternatively, at least one input component may include a sensor for sensing information (e.g., a Global Positioning System (GPS) component, accelerometer, gyroscope, and / or actuator).

[0047] Storage 140 may include one or more storage media suitable for storing data, information, and / or computer-executable instructions internally. According to an exemplary embodiment, storage 140 may include at least one storage device such as random access memory (RAM), read-only memory (ROM), and / or other types of dynamic or static storage devices (e.g., flash memory, magnetic storage, and / or optical storage) that stores information and / or instructions for use by processor 120. Further or alternatively, storage 140 may include a hard disk (e.g., magnetic disk, optical disk, magneto-optical disk, and / or solid-state drive), a compact optical disk (CD), a digital versatile optical disk (DVD), a floppy disk, a cartridge, magnetic tape, and / or other types of non-transitory computer-readable media, and include a corresponding drive. In this specification, computer-readable media are defined as non-transitory storage devices. Storage devices include storage space within a single physical storage device or storage space spread across multiple physical storage devices.

[0048] According to an exemplary embodiment, storage 140 can be configured to store information such as raw data, metadata, or similar data. Further or alternatively, storage 140 can be configured to store more than one piece of information associated with more than one action performed by processor 120. For example, storage 140 can store information specifying past actions performed by processor 120 to test vehicle software, the results of more than one action performed by processor 120, or similar information. Moreover, storage 140 can store data or information required for testing vehicle software.

[0049] In any implementation, storage 140 may include multiple storage media, and storage 140 may be configured to store copies or replicas of at least a portion of information on multiple storage media to provide redundancy and backup of information or associated data. Furthermore, storage 140 may also store computer-readable or computer-executable instructions that, when executed by more than one processor (e.g., processor 120), cause more than one processor to perform more than one operation / action described in this specification.

[0050] Processor 120 may include at least one processor that can be programmed or configured to perform the functions or actions described herein. For example, processor 120 may be configured to execute computer-executable instructions stored in at least one storage medium or storage device (e.g., storage device 140, etc.) thereby performing one or more operations or actions described herein.

[0051] According to an exemplary embodiment, processor 120 may be configured (e.g., via communication interface 110, input / output component 130, etc.) to receive one or more signals and / or one or more user inputs that define one or more instructions to perform one or more actions. Furthermore, processor 120 may be implemented in hardware, firmware, or a combination of hardware and software. For example, processor 120 may include at least one of 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 other types of processing or computing components.

[0052] According to an exemplary embodiment, the processor 120 may be configured to collect, extract, and / or receive more than one piece of information (in the form of signals or data) and process the received information, thereby testing the vehicle software.

[0053] Figure 1 The number and configuration of the constituent elements shown are provided as an example. In fact, with... Figure 1 Compared to the constituent elements shown, VST system 100 may include additional constituent elements, fewer constituent elements, different constituent elements, or constituent elements configured differently. Further or alternatively, the set of constituent elements of VST system 100 (e.g., more than one constituent element) may perform more than one function as described by other sets of constituent elements of VST system 100.

[0054] The following is for reference Figure 5 This provides an explanation of some exemplary actions that can be performed by the processor 120.

[0055] Examples of vehicle software testing disclosed herein

[0056] According to an exemplary implementation, one or more test cases can be designed and executed within a test environment to test the vehicle software.

[0057] A test case can refer to a specific set of conditions and / or steps designed to verify the functionality or behavior of software (or a system under test). A test case can specify more than one operation and expected result for a specific test scenario. The conditions and / or steps designed to verify the functionality or behavior of the software can be referred to as the test steps included in the test case. According to an exemplary implementation, more than one test step may be included in a test case, which may include: a test case ID (e.g., a set of inherent identifiers or numbers assigned to test cases for tracking and reference purposes), a test purpose (e.g., a description or specification of the goal or purpose of the test case), at least one test condition (e.g., preconditions or initial states required to execute the test case, specific settings or configurations required to trigger test execution, etc.), at least one test action (e.g., an operation or action performed to execute the test case, required input or interaction with the software, etc.), at least one expected result (e.g., the expected result or behavior anticipated by the software when the test case is executed normally, etc.), and any other appropriate information, one or more of these.

[0058] A test environment can refer to a specific set of conditions and / or elements in which test cases are executed (for those conditions and / or elements). In particular, a test environment may include more than one vehicle element associated with a test case. More than one vehicle element can refer to more than one element associated with more than one component of the vehicle, such as an Electronic Control Unit (ECU), a motor, and similar elements. For example, with respect to test cases designed to test software associated with the detection and display of obstacles near the rear of the vehicle, the test environment may include the vehicle's (more than one vehicle element) IVI ECU and ADAS ECU. According to an exemplary implementation, the test environment may also include more than one environmental element associated with a test case. More than one environmental element can refer to more than one element associated with the vehicle's environment. For example, test cases designed to test software associated with detecting and displaying obstacles near the rear of the vehicle may include obstacles near the rear of the vehicle and rain (more than one environmental element). As a result, when the vehicle's IVI ECU and ADAS ECU detect and display obstacles near the rear of the vehicle during rain, the test cases can evaluate the software associated with the vehicle's IVI ECU and ADAS ECU.

[0059] Figure 2 Exemplary components of a graphical user interface (GUI) 200 for testing vehicle software, representing one or more implementations.

[0060] like Figure 2 As shown, the graphical user interface (GUI) 200 may include at least a first part 220 and a second part 240.

[0061] According to an exemplary embodiment, the first part 220 may include more than one element of the test environment. The more than one element may include more than one vehicle element and / or more than one environmental element. The more than one vehicle element may be an element associated with more than one component of a vehicle in the test environment, such as an electronic control unit (ECU), a motor, and similar elements. According to an exemplary embodiment, the more than one vehicle element may be an element associated with more than one component of a specific type (model) of vehicle in the test environment. For example, the more than one element may include more than one electronic control unit (ECU) of a specific type of vehicle (which may differ from the ECUs in different types of vehicles). The more than one environmental element may be an element associated with the environment of the vehicle in the test environment, such as rainfall, moisture content, sunlight, specific weather conditions, and similar elements.

[0062] Figure 3 This describes exemplary components of a first portion 300 of a graphical user interface (GUI) for testing vehicle software, representing one or more embodiments. The first portion 300 can be associated with... Figure 2 The first part 220 corresponds to the first part 300, therefore, unless otherwise explicitly stated, the features associated with the first part 300 and the first part 220 can be applied to each other in the same way.

[0063] like Figure 3 As shown, the first part 300 may include three elements: an in-vehicle infotainment (IVI) electronic control unit (ECU) 320, an advanced driver assistance system (ADAS) electronic control unit (ECU) 340, and a transmission control module (TCM) electronic control unit (ECU) 360. The IVI ECU 320, ADAS ECU 340, and TCM ECU 360 correspond to the IVI ECU, ADAS ECU, and TCM ECU in the vehicle, respectively. It can be understood that... Figure 3 The configuration shown is simplified for illustrative purposes and is by no means intended to limit the scope of this disclosure. For example, in practice, the number of elements can be arbitrary, and the elements can be any elements in the test environment described above.

[0064] Here, for example, it can be understood that users sometimes want to perform tests in a test environment that includes the vehicle's IVI ECU, ADAS ECU, and TCM ECU (i.e., to perform tests to test the vehicle's IVI ECU, ADAS ECU, and TCM ECU). Therefore, the first part can be as follows: Figure 3 The diagram shows IVI ECU320, ADAS ECU340, and TCM ECU360.

[0065] return Figure 2 According to an exemplary embodiment, the second part 240 may include a log area. The log area may display test logs associated with test cases. According to an exemplary embodiment, the log area may display overall test logs associated with all elements of the test environment and / or test logs associated with specific elements of the test environment. For example, the log area may display overall test logs associated with IVI ECU320, ADAS ECU340, and TCM ECU360 in the test environment and / or display test logs associated with one of IVI ECU320, ADAS ECU340, and TCM ECU360 in the test environment. It is understood that test logs can refer to logs representing various information, activities, results, non-compliance, and any other associated data related to the execution of tests, as known in the art.

[0066] According to an exemplary implementation, when test cases are executed in a test environment having one or more elements displayed in the first section, the VST system can display the overall log associated with all one or more elements in the log area. Then, the user can provide selection input to choose one of the elements displayed in the first section. Here, the VST system can then display the test log associated only with the selected element in the log area. For example, the user can select to display... Figure 3 In the first part 300, the ADAS ECU 340, the VST system can then display test logs associated only with the ADAS ECU 340 in the log area of ​​the second part 240. According to an exemplary implementation, the user can provide selection input by clicking on elements in the first part 220.

[0067] Therefore, the GUI enables users to quickly view specific test logs that are associated with specific elements of the test environment, thereby reducing the time required to analyze and identify the causes of errors within test cases.

[0068] According to an exemplary implementation, GUI200 may further include ( Figure 2 (Not shown in the diagram) The third part. The third part may include more than one test step of the test case, and includes the state associated with each of the more than one test steps.

[0069] Figure 4 This describes exemplary components of a third part 400 of a graphical user interface (GUI) for testing vehicle software, representing one or more implementations. (Example...) Figure 4 As shown, the third part 400 may include five test steps: test step 1 410, test step 2 420, test step 3 430, test step 4 440, and test step 5 450, and their respective associated states 412, 422, 432, 442, and 452. It is understood that... Figure 4 The configuration shown is simplified for illustrative purposes and is by no means intended to limit the scope of this disclosure. For example, in practice, the number of test steps and associated states within Part Three (and within the test cases) can be arbitrary, the specific content and form of the test steps can be arbitrary, and the specific form of the states can be arbitrary.

[0070] like Figure 4 As shown, test step 1 410 may include the step of "assuming the start of the REACTOR_SCENARIO (reactor_scenario)" to define the operation of a test environment that has established conditions and / or elements for the execution of test cases. Test step 2 420 may include the step of "powering on the ADAS_ECU" to define the operation of an Advanced Driver Assistance System (ADAS) electronic control unit (ECU) within the test environment. Similarly, test step 3 430 may include the step of "powering on the IVI_ECU" to define the operation of an In-vehicle Infotainment System (IVI) electronic control unit (ECU) within the test environment.

[0071] Test step 4 440 may include the step of specifying the condition scenario where the obstacle is 2.0 meters away from the front right of the vehicle, "the obstacle is 2.0 meters away from the front right of the vehicle". Test step 5 450 may include the step of specifying the expected result of the condition scenario specified in test step 4 440, "then, the IVI displays that the obstacle is at the front right MAX DISTANCE of the vehicle", where the in-vehicle infotainment system displays the obstacle at the maximum distance from the front right of the vehicle.

[0072] Furthermore, state 412 can be associated with test step 1 410, indicating that test step 1 410 was successful (i.e., the start of "REACTOR_SCENARIO" was successful). The same applies to states 422, 432, and 442, which can be associated with test step 2 420, test step 3 430, and test step 4 440. At this point, state 452 can be associated with test step 5 450, indicating that test step 5 450 failed (i.e., as expected in the scenario specified in test step 4 440, the in-vehicle infotainment system failed to display the obstacle at its maximum distance to the right front of the vehicle). Therefore, the user can identify that the cause of the failure may be related to the in-vehicle infotainment system, and then select IVI ECU 320 in Part 1 300 to view the test log associated with IVI ECU 320 and further investigate and identify the cause of the failure.

[0073] Therefore, the GUI enables users to quickly identify where (i.e., which specific test step within a test case) fails, and then quickly analyze and identify the cause of the error (failure) within the test case by viewing the specific test logs in the log area.

[0074] return Figure 2 According to an exemplary embodiment, the second part 240 may further include a chart area. The chart area may include a chart representing communication between more than one element over a period of time. According to an exemplary embodiment, the chart may be a time sequence chart. For example, the chart may represent communication between IVI ECU 320 and ADAS ECU 340 over a period of time (e.g., from the start of a test case until the time when test step 5 450 becomes non-compliant).

[0075] Therefore, GUI200 enables users to quickly analyze and identify the causes of errors within test cases by rapidly viewing the interactions between elements of the test environment during a specific period, and then viewing specific test logs in the log area that are associated with specific elements.

[0076] According to an exemplary implementation, GUI200 may further include ( Figure 2 (Not shown in the image) Part Four. Part Four may include a video simulation of the simulated test environment for executing the test cases. For example, for a test case intended to test the communication between the IVIECU320 and ADASECU340 during reverse parking, Part Four may display a video simulation of the vehicle performing reverse parking.

[0077] Therefore, GUI200 enables users to visualize the real-world scene of the vehicle during testing, which improves the time available for analyzing and identifying the causes of errors within test cases.

[0078] According to an exemplary implementation, a user can add annotations to the video simulation in the fourth part. In particular, the fourth part may also include an annotation window where the user can provide annotation input. Annotation input may include comments, diagrams, symbols, and similar inputs that the user wants to add as annotations to the video simulation. Therefore, the user can provide annotations to the system, where they can be displayed in the annotation window.

[0079] According to an exemplary implementation, GUI200 may further include ( Figure 2 (not shown) scrubber, which may be associated with one or more of the second part 240, the third part, and the fourth part.

[0080] According to an exemplary implementation, the scrubbing bar can be associated with the second portion 240. In particular, the scrubbing bar can be associated with a test log displayed in the log area of ​​the second portion 240, such that when a user moves the scrubbing bar to a specific time instance (i.e., provides input to slide the scrubbing bar), the test log displayed in the log area can be updated to reflect the test log generated up to that specific time instance.

[0081] According to an exemplary embodiment, the scrubber can also be associated with a chart in the chart area of ​​the second part 240. As a result, when a user moves the scrubber to a specific time instance (i.e., provides input to slide the scrubber), the chart in the chart area can be updated to reflect communication between more than one element up to that specific time instance.

[0082] According to an exemplary implementation, the scrubbing bar can be associated with a third part. In particular, the scrubbing bar can be associated with a state displayed in the third part, such that when a user moves the scrubbing bar to a specific time instance (i.e., provides input to slide the scrubbing bar), the state in the third part can be updated to reflect the state in that specific time instance.

[0083] According to an exemplary implementation, the scrubbing bar can be associated with the fourth part. In particular, the scrubbing bar can be associated with a video simulation displayed in the fourth part, such that when a user moves the scrubbing bar to a specific time instance (i.e., provides input to slide the scrubbing bar), the video simulation displayed in the fourth part can be updated to reflect the video simulation in that specific time instance.

[0084] Therefore, GUI200 enables users to quickly view test results at specific points in time (i.e., test logs, test step status, charts, and similar items), thereby facilitating error analysis within test cases and reducing the time required for such analysis.

[0085] Understandable Figure 2 The configurations shown are simplified for illustrative purposes and are by no means intended to limit the scope of this disclosure. For example, in practice, the relative position, relative size, and / or shape associated with each element within the GUI200 can be arbitrary.

[0086] Exemplary actions for testing vehicle software in this disclosure

[0087] The following is for reference Figure 5 This document describes some exemplary actions that can be performed through the VST system disclosed herein.

[0088] Figure 5 The flowchart illustrates an exemplary method 500 for testing vehicle software according to one or more embodiments. One or more actions in method 500 can be performed by at least one processor (e.g., processor 120) of the VST system.

[0089] like Figure 5 As shown, in action S510, at least one processor can be configured to generate a graphical user interface. The graphical user interface may include at least a first part and a second part. Here, the first part may include more than one element of the test environment, and the second part may include a log area.

[0090] According to an exemplary embodiment, one or more elements may include one or more vehicle elements and / or one or more environmental elements. One or more vehicle elements may be elements associated with one or more components of a vehicle in a test environment, such as an electronic control unit (ECU), a motor, and similar elements. According to an exemplary embodiment, one or more vehicle elements may be elements associated with one or more components of a specific type (model) of vehicle in a test environment. For example, one or more elements may include one or more electronic control units (ECUs) of a specific type of vehicle. One or more environmental elements may be elements associated with the vehicle's environment, such as rainfall, moisture content, sunlight, specific weather conditions, and similar elements.

[0091] According to an exemplary implementation, the log area can display test logs associated with test cases. Specifically, the log area can display overall test logs associated with all elements of the test environment and / or test logs associated with specific elements of the test environment. The method then proceeds to action S520.

[0092] In action S520, at least one processor may be configured to receive selection input for selecting one of more than one elements displayed in the first portion. The selection input may be received from a user. According to an exemplary embodiment, the selection input may include a click input. The method then proceeds to action S530.

[0093] In action S530, at least one processor can be configured to display a test log in response to the receipt of a selection input. The test log can be associated with only one selected element from more than one elements and can be displayed in the log area of ​​the second part.

[0094] When action S530 is performed, method 500 may end or terminate. Alternatively, method 500 may return to action S520, whereby at least one processor may be configured to repeatedly (in action S520) receive selection input and (in action S530) display test logs for at least a predetermined amount of time. For example, a user may sometimes want to view test logs associated with different elements in the first part continuously (or periodically). Therefore, at least one processor may then restart (in action S520) receiving selection input and (in action S530) displaying test logs.

[0095] According to an exemplary embodiment, the second part of the graphical user interface may further include a chart area. The chart area may include a chart representing communication between more than one element during a certain period. According to an exemplary embodiment, the chart may be a time-series chart.

[0096] According to an exemplary embodiment, the graphical user interface may further include a third part. The third part may include one or more test steps of a test case and states associated with each of the one or more test steps. According to an exemplary embodiment, when a test case is executed, each state can be updated to the state of the associated test step among the one or more test steps, such as success, failure, and similar states.

[0097] According to an exemplary implementation, the graphical user interface may further include a fourth part. The fourth part may include a video simulation of a simulated test environment.

[0098] According to an exemplary embodiment, the graphical user interface may further include a scrubbing bar, which may be associated with one or more of the second, third, and fourth portions.

[0099] According to an exemplary implementation, the scrubbing bar can be associated with test logs displayed in the log area of ​​the second section. In this regard, at least one processor can be configured to receive swipe input from a user, indicating that the scrubbing bar is being slid to a specific time instance. Subsequently, in response to the receipt of the swipe input, at least one processor can be configured to update the test logs displayed in the log area based on the time instance. For example, the test logs displayed in the log area can be updated to reflect test logs generated up to the specified time instance.

[0100] According to an exemplary implementation, the scrubber bar can be associated with a chart in the chart area of ​​the second part. At this point, at least one processor can be configured to receive a swipe input from a user, indicating that the scrubber bar is being slid to a specific time instance. Subsequently, in response to the receipt of the swipe input, at least one processor can be configured to update the chart displayed in the chart area based on the time instance. For example, the chart displayed in the chart area can be updated to reflect the charts generated up to the time instance (communication between more than one element).

[0101] According to an exemplary implementation, the scrubbing strip can be associated with a state in the third part. In this regard, at least one processor can be configured to receive a sliding input from a user, indicating that the scrubbing strip is slid to a certain time instance. Subsequently, in response to the receipt of the sliding input, at least one processor can be configured to update the state displayed in the third part based on the time instance. For example, the state displayed in the third part can be updated to reflect the respective states of the test steps within the time instance.

[0102] According to an exemplary implementation, the scrubbing bar can be associated with the video simulation in the fourth section. At this point, at least one processor can be configured to receive a sliding input from a user, indicating that the scrubbing bar is being slid to a certain time instance. Subsequently, in response to the receipt of the sliding input, at least one processor can be configured to update the video simulation in the fourth section based on the time instance. For example, the video simulation in the fourth section can be updated to reflect the video simulation in the time instance.

[0103] According to an exemplary implementation, the fourth part may further include an annotation window. At this point, at least one processor may be configured to receive annotation input from a user. The annotation input may include comments, diagrams, symbols, and similar inputs that the user wishes to append as annotations to the video simulation. Subsequently, in response to the receipt of the annotation input, at least one processor may be configured to display the annotation input in the annotation window.

[0104] Various implementation schemes

[0105] The above disclosure provides examples and illustrations, but is not intended to be exhaustive or to limit the implementation to the exact form disclosed. Modifications and variations can be made based on the above disclosure, or can be obtained through implementation.

[0106] Some implementations may involve systems, methods, and / or computer-readable media at a detailed level of any possible integrated technology. Furthermore, one or more of the aforementioned constituent elements 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 (multiple)) having computer-readable program instructions for causing the processor to perform actions.

[0107] A computer-readable storage medium can be a tangible device capable of holding and storing 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 thereof, but is not limited thereto. A non-exhaustive list of more specific examples of computer-readable storage media includes: portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital versatile optical disc (DVD), memory sticks, floppy disks, punch cards, or devices with mechanically encoded and recorded instructions, such as raised structures in a slot, and any suitable combination thereof. The computer-readable storage medium used in this specification should not be construed as a temporary signal itself, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses passing through fiber optic cables), or electrical signals transmitted through wires.

[0108] The computer-readable program instructions described in this specification can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded to external computers or external storage devices via networks such as the Internet, local area networks, wide area networks, and / or wireless networks. The network may include copper cables, optical fibers, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. Network adapter cards or network interfaces within each computing / processing device receive and transmit the computer-readable program instructions from the network for storage on the computer-readable storage media within the respective computing / processing device.

[0109] Computer-readable program code / instructions that perform actions can be any of the following: assembly instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, configuration data for integrated circuits, or source code or object code written in any combination of one or more programming languages. These one or more programming languages ​​include object-oriented programming languages ​​such as Smalltalk, C++, or similar languages, and procedural programming languages ​​such as the "C" programming language or similar languages. Computer-readable program instructions can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer can connect to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or (for example, via the internet using an internet service provider) connect to an external computer. In some implementations, for example, electronic circuits including programmable logic circuits, field-programmable gate arrays (FPGAs) or programmable logic arrays (PLAs) can be personalized to execute computer-readable program instructions by utilizing state information of computer-readable program instructions to perform schemes or actions.

[0110] 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 to generate a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create parts that implement the functions / behaviors specified in the flowcharts and / or block diagrams or in the function blocks(s). The computer-readable program instructions can also be stored in a computer-readable storage medium that can instruct a computer, a programmable data processing apparatus, and / or other devices to function in a particular manner, such that the computer-readable storage medium containing the instructions comprises an article of manufacture including instructions for implementing the functions / behaviors specified in the function blocks of the flowcharts and / or block diagrams or in the function blocks(s).

[0111] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus or other device, and perform a series of action steps on the computer, other programmable apparatus or other device to generate a computer-implemented process, the result of which the instructions executed on the computer, other programmable apparatus or other device implement the functions / behaviors specified in the function blocks of the flowchart and / or block diagram or in the function blocks(multiple).

[0112] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and action of various implementations of systems, methods, and computer-readable media. In this regard, each functional block in a flowchart or block diagram may represent a microservice module, segment, or part of an instruction having one or more executable instructions that implement the specified logical function. Methods, computer systems, and computer-readable media may include additional functional blocks, fewer functional blocks, different functional blocks, or functional blocks configured differently compared to those depicted in the figures. In some alternative implementations, the functions described in the functional blocks may occur regardless of the order in which they are described in the figures. For example, two consecutively shown functional blocks may be executed practically or substantially simultaneously, or functional blocks may sometimes be executed in reverse order according to their related functions. It should also be noted that the functional blocks of the block diagrams and / or flowcharts, and combinations of functional blocks in the block diagrams and / or flowcharts, can be implemented by a system based on dedicated hardware that performs the specified functions or behaviors or executes a combination of dedicated hardware and computer instructions.

[0113] It is evident that the systems and / or methods described in this specification can be implemented in various forms, including hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement the system and / or method is not a limitation on the implementation. Therefore, it is understood that the operation and behavior of the system and / or method are not described in this specification with reference to specific software code, and software and hardware can be designed to implement the system and / or method based on the description in this specification.

[0114] It will be understood that many modifications and variations of this disclosure can be made in light of the foregoing teachings. It will be apparent that, within the scope of the appended sections, this disclosure can be practiced in ways different from those specifically described in this specification.

[0115] Alternatively, the computer program product including the computer program of the above embodiments may be stored in a storage medium or distributed through a communication line.

Claims

1. A system for viewing test case results, comprising: Storage memory, which stores computer-executable instructions; and At least one processor is connected to the storage device in a communicative manner. The at least one processor is configured to execute the instructions to perform the following actions: Generate a graphical user interface that has at least a first part and a second part, wherein, The first part has one or more elements of the test environment, and the second part has a log area; The user receives selection input from the user to select one of the more than one elements displayed in the first part; and In response to receiving the selection input, a test log associated only with the selected element from the more than one elements is displayed in the log area.

2. The system according to claim 1, wherein, The graphical user interface also has a third part. The third part includes one or more test steps for test cases and a state associated with each of the one or more test steps.

3. The system according to claim 1 or 2, wherein, The one or more elements mentioned above have one or more electronic control units that are associated with the type of vehicle.

4. The system according to any one of claims 1 to 3, wherein, The second part also includes a chart area. The chart area contains charts representing one or more communications between the one or more elements during a certain period.

5. The system according to any one of claims 1 to 4, wherein, The graphical user interface also has a fourth part. The fourth part includes video simulation of the simulated testing environment.

6. The system according to claim 5, wherein, The graphical user interface also includes a scrubbing bar that is associated with the test log in the second part and the video simulation in the fourth part. The at least one processor is also configured to execute the instructions to perform the following actions: The user receives a swipe input indicating that the scrubbing strip should be slid to a specific time instance; and In response to receiving the sliding input, the test log displayed in the log area and the video simulation displayed in the fourth part are updated based on the time instance.

7. The system according to claim 5 or 6, wherein, The fourth part also includes a comment window. The at least one processor is also configured to execute the instructions to perform the following actions: Receive annotation input from the user; and The input annotation is displayed in the annotation window.

8. A method for viewing test case results, comprising: Generate a graphical user interface with at least a first part and a second part, wherein the first part has one or more elements of the test environment, and the second part has a log area; The user receives selection input from the user to select one of the more than one elements displayed in the first part; and In response to receiving the selection input, a test log associated only with the selected element from the more than one elements is displayed in the log area.

9. The method according to claim 8, wherein, The graphical user interface also has a third part. The third part includes one or more test steps for test cases and a state associated with each of the one or more test steps.

10. The method according to claim 8 or 9, wherein, The one or more elements mentioned above have one or more electronic control units that are associated with the type of vehicle.

11. The method according to any one of claims 8 to 10, wherein, The second part also includes a chart area. The chart area contains charts representing one or more communications between the one or more elements during a certain period.

12. The method according to any one of claims 8 to 11, wherein, The graphical user interface also has a fourth part. The fourth part includes video simulation of the simulated testing environment.

13. The method according to claim 12, wherein, The graphical user interface also includes a scrubbing bar that is associated with the test log in the second part and the video simulation in the fourth part. The method further includes: The user receives a swipe input indicating that the scrubbing strip should be slid to a specific time instance; and In response to receiving the sliding input, the test log displayed in the log area and the video simulation displayed in the fourth part are updated based on the time instance.

14. The method according to claim 12 or 13, wherein, The fourth part also includes a comment window. The method further includes: Receive annotation input from the user; and The input annotation is displayed in the annotation window.

15. A computer program product comprising a computer program for causing at least one processor to perform a method, wherein, The method includes: Generate a graphical user interface with at least a first part and a second part, wherein the first part has one or more elements of the test environment, and the second part has a log area; The user receives selection input from the user to select one of the more than one elements displayed in the first part; and In response to receiving the selection input, a test log associated only with the selected element from the more than one elements is displayed in the log area.

16. The computer program product according to claim 15, wherein, The graphical user interface also has a third part. The third part includes one or more test steps for test cases and a state associated with each of the one or more test steps.

17. The computer program product according to claim 15 or 16, wherein, The one or more elements mentioned above have one or more electronic control units that are associated with the type of vehicle.

18. The computer program product according to any one of claims 15 to 17, wherein, The second part also includes a chart area. The chart area contains charts representing one or more communications between the one or more elements during a certain period.

19. The computer program product according to any one of claims 15 to 18, wherein, The graphical user interface also has a fourth part. The fourth part includes video simulation of the simulated testing environment.

20. The computer program product according to claim 19, wherein, The graphical user interface also includes a scrubbing bar that is associated with the test log in the second part and the video simulation in the fourth part. The method further includes: The user receives a swipe input indicating that the scrubbing strip should be slid to a specific time instance; and In response to receiving the sliding input, the test log displayed in the log area and the video simulation displayed in the fourth part are updated based on the time instance.

Images