Test case management method and test case management system

Abstract

The invention provides a test case management method and a test case management system. The present disclosure provides systems, methods, and apparatus for managing one or more test cases for testing a test of software of a vehicle system. According to an embodiment, a method may be implemented by at least one processor, the method may include presenting a first graphical user interface (GUI) to a user, the first graphical user interface having information of one or more test cases available to the user; receiving, from a user, a user input defining a user selection of a test case made from among the one or more available test cases; and implementing at least one action of managing the test case selected by the user.

Description

Technical Field

[0001] Systems and methods matching exemplary embodiments of the present disclosure relate to test case management, and more particularly, to managing one or more test cases for testing software associated with a vehicle system. Background Art

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

[0003] In order to develop advanced or complex functions in a system, testing related to the functionality and performance of multiple software components and / or hardware components across multiple systems or domains may be required. In the context of vehicle systems, cross-domain testing is sometimes required in the development of advanced functions in vehicle systems such as Lane Change Assist, Mobile Smart Key, and similar functions. Cross-domain testing may include testing various electronic control units (ECUs) across various systems and the interaction between associated software and hardware components. For example, various test systems may be used to provide testing at various fidelity levels (e.g., virtual ECUs, simulated ECUs, simulated ECUs, etc.), provide testing in various vehicle variants or platforms, and / or provide testing of software developed by various developers.

[0004] In order to properly implement the testing of software for testing vehicle systems, various test conditions may need to be defined based on multiple test cases. In this regard, a test case may refer to a specific setup condition or test steps utilized in a test to verify the functionality or behavior of the software. In particular, a test case may include a detailed description of the test steps implemented in the test. Therefore, in the case of testing software with complex functions, in particular, in the case where the test includes cross-system or cross-domain requirements, the management of the test cases related to the test (such as the arrangement, preparation, documentation and / or tracking of the status of the test cases) throughout the SDLC may be complex and difficult.

[0005] First, in the related art, the test cases available to the user may be limited or restricted by the test cases embedded in the available test systems. That is, whenever the user utilizes a specific test system to test the software, the user may only be able to utilize the test cases provided by the specific test system. The user is sometimes unable to easily construct, adjust, specify, or perform similar operations on the test cases provided by the test system according to the desired test requirements. The situation becomes more complicated and difficult when the test includes multiple test systems and the test cases constructed for one part of the test system are incompatible or cannot be executed in other parts of the test system. Therefore, in the related art, users tend to only utilize the available test cases or the provided test cases, and avoid modifications in the test cases as much as possible.

[0006] Furthermore, whenever the use of a particular test case cannot be avoided, the user may need to expend a great deal of effort, time, and cost in order to construct the desired test case. Furthermore, since various test systems exist with various test case requirements and are incompatible with one another, whenever the user wants to utilize a particular test case at various fidelity levels and / or for various vehicle variants, the user may need to iterate through the process, which may result in a significant increase in effort, time, and cost to subsequently construct the particular test case. In particular, for users who have no experience in constructing test cases and / or have no technical background at all, the process of constructing a particular test case may be even more burdensome and costly.

[0007] In addition, in the related art, there is no method for a user to efficiently and easily share test cases with another user. Therefore, even if a user wants to use a specific test case that may have been built by another user in the past, there is no method for the user to do so.

[0008] Furthermore, in the related art, the processes of searching for available test cases, creating new test cases, and deploying the newly constructed test cases in the existing test system are implemented in various independent systems, thus making the management of test cases inefficient and ineffective.

[0009] Considering the above, the limitations and restrictions in managing test cases in the related art system sometimes lead to a waste of resources (e.g., manpower, time, cost, etc.), which may result in delays in testing. Therefore, the testing of software in the related art may be time-consuming and inefficient, which may delay the development of the software. Summary of the invention

[0010] According to an embodiment, a method for managing one or more test cases for testing software associated with a vehicle system may be provided. The method may be implemented by at least one processor of a system, and the method may include: presenting a first graphical user interface (GUI) to a user, the first graphical user interface having information about one or more test cases available to the user; receiving user input from the user defining a user selection of a test case to be performed from the one or more available test cases; and performing at least one action for managing the test case selected by the user.

[0011] According to an embodiment, presenting the first GUI may include: acquiring information associated with a user from at least one storage medium; determining one or more available test cases based on the acquired user information; generating the first GUI in a manner including information associated with one or more available test cases; and sending the first GUI to a user device associated with the user. The acquired user information may include at least one of the following information: the user's responsibilities, the project associated with the user, the work group associated with the user, and the location associated with the user.

[0012] According to an embodiment, the first GUI may include one or more interactive elements, each of which is associated with an available test case among one or more available test cases. Furthermore, receiving the user input may include: receiving a user interaction related to at least one interactive element among the one or more interactive elements; and determining the available test case associated with the at least one interactive element with which the user interacted as the test case selected by the user.

[0013] According to an embodiment, the implementation of at least one action may include: presenting a second GUI to a user, the second GUI having information associated with a test case selected by the user; receiving user input from the user to modify at least a portion of the information associated with the test case selected by the user; and generating a new test case based on the user input, the new test case having at least a portion of information different from the test case selected by the user.

[0014] According to an embodiment, the information associated with the test case selected by the user may include at least one test step associated with the test case selected by the user. The second GUI may include at least one input field associated with the at least one test step. The receiving of the user input may include: receiving a user selection of at least one parameter defining the at least one test step. The generating of the new test case may include: generating the new test case based on the at least one test step defined by the user.

[0015] According to an embodiment, receiving a user selection for at least one parameter may include: receiving one or more user inputs in at least one input field from a user, the one or more user inputs may include one or more keywords associated with the at least one parameter. The at least one parameter may include at least one of the following parameters: a parameter defining a software-based ECU, a parameter defining a hardware-based ECU, and a parameter defining the fidelity of the test environment.

[0016] According to an embodiment, at least one input field may include pre-entered parameters, and receiving a user selection for at least one parameter may include: receiving from the user an agreement for the pre-entered parameters or a modification for the pre-entered parameters. Further or alternatively, at least one input field may include a plurality of selectable parameters, and receiving a user selection for at least one parameter may include: receiving from the user at least one user selection for at least one parameter among the plurality of selectable parameters.

[0017] According to an embodiment, a system for managing one or more test cases for testing software associated with a vehicle system may be provided. The system may include: at least one storage device storing instructions; and at least one processor, the at least one processor being configured to execute the instructions to present a first graphical user interface (GUI) to a user, the first graphical user interface having information of one or more test cases available to the user, receiving user input defining a user selection of a test case to be performed from the one or more available test cases, and performing at least one action for managing the test case selected by the user.

[0018] According to an embodiment, at least one processor is configured to execute instructions to present a first GUI by: acquiring information associated with a user from at least one storage medium; determining one or more available test cases based on the acquired user information; generating the first GUI in a manner including information associated with one or more available test cases; and sending the first GUI to a user device associated with the user. The acquired user information may include at least one of the following information: the user's role, the project associated with the user, the work group associated with the user, and the location associated with the user.

[0019] According to an embodiment, the first GUI may include one or more interactive elements, each of the one or more interactive elements being associated with an available test case among one or more available test cases, and at least one processor may be configured to execute instructions to receive user input by: receiving user interaction related to at least one interactive element among the one or more interactive elements; and determining an available test case associated with at least one interactive element with which the user has interacted as a test case selected by the user.

[0020] According to an embodiment, at least one processor may be configured to execute instructions to implement at least one action by: presenting a second GUI to a user, the second GUI having information associated with a test case selected by the user; receiving user input from the user to modify at least a portion of the information associated with the test case selected by the user; and generating a new test case based on the user input, the new test case may include at least a portion of information different from the test case selected by the user. The at least one parameter may include at least one of the following parameters: a parameter defining a software-based ECU, a parameter defining a hardware-based ECU, and a parameter defining the fidelity of the test environment.

[0021] According to an embodiment, the information associated with the test case selected by the user may include at least one test step associated with the test case selected by the user. The second GUI may include at least one input field associated with the at least one test step. The at least one processor may be configured to execute instructions to receive user input by the following process: receiving a user selection of at least one parameter defining at least one test step. The at least one processor may be configured to execute instructions to generate a new test case by the following process: generating a new test case based on at least one test step defined by the user.

[0022] According to an embodiment, at least one processor may be configured to execute instructions to receive a user selection for at least one parameter by: receiving one or more user inputs in at least one input field from a user. The one or more user inputs may include one or more keywords associated with the at least one parameter.

[0023] According to an embodiment, at least one input field may include pre-recorded parameters, and at least one processor may be configured to execute instructions to receive user selection for at least one parameter by the following process: receiving consent for the pre-recorded parameters or modification of the pre-recorded parameters from the user. Alternatively or in addition, at least one input field may include multiple selectable parameters, and at least one processor may be configured to execute instructions to receive user selection for at least one parameter by the following process: receiving at least one user selection for at least one parameter among the multiple selectable parameters from the user.

[0024] The additional aspects will be described in part in the following description and in part will be obvious from the description, or may be achieved by practice of the embodiments presented in the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Hereinafter, features, advantages, and significance of preferred embodiments of the present disclosure will be described with reference to the accompanying drawings, in which like reference numerals represent like elements.

[0026] Figure 1 A block diagram of an example system architecture for managing one or more test cases for testing one or more software associated with a vehicle system is shown in accordance with one or more embodiments.

[0027] Figure 2 A block diagram illustrating exemplary components of a test case management system according to one or more embodiments.

[0028] Figure 3 An exemplary graphical user interface (GUI) presented by a test case management system in accordance with one or more embodiments is illustrated.

[0029] Figure 4 Another exemplary GUI presented by a test case management system illustrates one or more embodiments.

[0030] Figure 5 Yet another exemplary GUI presented by a test case management system illustrating one or more embodiments.

[0031] Figure 6 Yet another exemplary GUI presented by a test case management system illustrating one or more embodiments.

[0032] Figure 7 A flow chart illustrating an example method of managing one or more test cases for testing software associated with a vehicle system in accordance with one or more embodiments. DETAILED DESCRIPTION

[0033] The following detailed description of the preferred embodiments refers to the accompanying drawings. The above disclosure provides examples and illustrations, but is not intended to be exhaustive or to limit the embodiments to the exact forms disclosed. Modifications and variations may be made in light of the above disclosure, or may be learned from the implementation of the embodiments. Moreover, one or more features or constituent elements of an embodiment may be combined with another embodiment (or one or more features of another embodiment), or may be combined therewith. 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 implemented (at least partially) simultaneously, and the order of one or more actions may be switched.

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

[0035] As long as it is not particularly clearly recorded, the elements, behaviors or instructions used in this specification should not be interpreted as important or necessary. In addition, the articles "a" and "an" used in this specification are intended to include more than one matter and can be used interchangeably with "more than one". In the case of only one matter, a term such as "one" or the same term is used. In addition, the terms "has", "have", "having", "include", "including" or similar terms used in this specification are meant to be open-ended terms. Moreover, as long as it is not particularly clearly recorded, phrases such as "based on..." are intended to mean "at least partially based on...". Moreover, expressions such as "at least one of [A] and [B]" or "at least one of [A] or [B]" should be understood to include only A, only B, or both A and B.

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

[0037] Moreover, the features, advantages and characteristics of the present disclosure described may be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize that, in view of the description of this specification, the present disclosure may be implemented without one or more of the specific features or advantages of a specific embodiment. In other examples, additional features and advantages that may not be present in all embodiments of the present disclosure may be recognized in certain specific embodiments.

[0038] In addition, the term "vehicle" or similar terms used in this specification may refer to any powered and / or mechanical machine that can transport or move people and / or goods, such as passenger cars, trucks, motorcycles, buses, bicycles, mobility scooters, and the like.

[0039] The terms "test artifact", "test artifact" and similar terms described in this specification may refer to one or more components that constitute a test. For example, a test artifact may include one or more software-based components (e.g., virtual ECU, simulated ECU, vehicle model, etc.), one or more hardware-based components (e.g., physical ECU, vehicle hardware components, etc.), one or more test components (e.g., test environment components, test cycles, test execution, etc.), one or more test scenarios, one or more test cases, one or more test packages and / or the like.

[0040] An exemplary embodiment matching the present disclosure provides a method, system, and device for managing one or more test cases for testing one or more software of a vehicle system such as one or more vehicle-mounted ECUs. According to the embodiment, through the method, system, device, or the like of the present disclosure, one or more users can effectively and efficiently manage one or more test cases for testing software of a vehicle system.

[0041] In some embodiments, the method, system, device, or the like of the present disclosure may generate and present at least one graphical user interface (GUI) to one or more users, with the result that one or more users may use at least one GUI to browse and retrieve available test cases, manage test cases associated with themselves, share one or more test cases, and create one or more new test cases. According to the embodiment, the user may use at least one GUI to select an available test case, and use the selected test case as a template for creating one or more new test cases.

[0042] At least one GUI may be generated based on user information (e.g., user's responsibilities, etc.): at least one GUI may include information and components matching the user. In this way, according to an exemplary embodiment of the present disclosure, users with different backgrounds can efficiently and effectively manage more than one test case according to their own intentions.

[0043] Finally, according to the exemplary embodiments of the present disclosure, more than one test case can be synchronized in a timely and consistent manner. Therefore, software testing can be implemented and managed more efficiently, the burden on users can be significantly reduced, and the time and cost required to develop software can be significantly reduced.

[0044] It is assumed in this specification that the features, advantages, and importance of the exemplary embodiments described above are only part of the present disclosure and are not intended to be exhaustive or to limit the scope of the present disclosure. The following provides further descriptions of the features, constituent elements, configurations, actions, and implementations of the exemplary embodiments of the present disclosure, as well as the associated technical advantages and importance.

[0045] Figure 1 A block diagram of an exemplary system architecture 100 for managing one or more test cases for testing one or more software associated with a vehicle system in accordance with one or more embodiments is shown. According to embodiments, the software may include one or more software-based (e.g., virtualized, simulated, etc.) vehicle electronic control units (ECUs). Figure 1 As shown, the system architecture 100 may include a test case management system 110 , a plurality of user equipments (UEs) 120 - 1 ˜ 120 -N, a plurality of nodes 130 - 1 ˜ 130 -N, and a network 140 .

[0046] Typically, the test case management system 110 can be connected to a plurality of UEs 120-1 to 120-N and a plurality of nodes 130-1 to 130-N in a communicative manner via a network 140, and can 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 one or more test cases for one or more associated users. Figure 2 To provide an explanation of exemplary components that may be included in the test case management system 110, hereinafter, reference is made to Figure 3 to Figure 7 To provide instructions for the actions and use cases for establishing the association.

[0047] 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 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 smart phone, etc.), a wearable device (e.g., a pair of smart glasses or a smart watch), a SIM-based device, or any other suitable device that may be associated with one or more users participating in the testing of the software.

[0048] The plurality of UEs 120-1 to 120-N may be used by one or more associated users to access the test case management system 110 to utilize the test case management system 110. For example, a user may access the test case management system 110 via an associated UE to manage one or more test cases. For example, a user may utilize the test case management system 110 via an associated UE to retrieve one or more available test cases, to construct one or more test cases, to view one or more associated test cases, to modify one or more test cases, to share one or more test cases, and for similar purposes. Furthermore, a user may utilize the test case management system 110 to obtain (e.g., view, download, etc.) information associated with one or more test cases (e.g., content of the test cases, creators of the test cases, test artifacts associated with the test cases, etc.).

[0049] According to an embodiment, at least a portion of the plurality of UEs 120-1 to 120-N may be configured in various geographical locations. For example, a first portion of the plurality of UEs 120-1 to 120-N may be used by a first user (e.g., a developer of a first ECU, etc.), and the first user may be located in a first location, while a second portion of the plurality of UEs 120-1 to 120-N may be used by a second user (e.g., a developer of a second ECU, etc.), and the second user may be located in a second location different from the first location.

[0050] On the other hand, each of the plurality of nodes 130-1 to 130-N may include any other appropriate components that can receive, host, store, deploy, process, provide, or perform similar actions on information and data associated with one or more devices, equipment, systems, or tests. According to an embodiment, at least a portion of the plurality of nodes 130-1 to 130-N may be configured to host, deploy, store, provide, or perform similar actions on one or more test artifacts or components associated with one or more test cases.

[0051] For example, a portion of the plurality of nodes 130-1 to 130-N may include a device or apparatus that can be used to build, store, execute, simulate, or perform similar actions on one or more computer executable software applications, such as one or more virtualized ECUs, one or more simulated ECUs, and / or any other appropriate software-based components (e.g., vehicle models, data communication module (DCM: Data Communications Module) models, heating, ventilation, and air conditioning (HVAC: HeatingVentilation and Air Conditioning) models, etc.). As another example, a portion of the plurality of nodes 130-1 to 130-N may include one or more fully developed physical ECUs, one or more partially developed physical ECUs, one or more vehicle hardware components (e.g., transmission systems, engines, etc.), or the like, or may be connected to the hardware-based components in a communicative manner. One or more of the software-based components and hardware-based components may be associated with one or more test cases managed by the test case management system 110. For example, the one or more test cases may include information (eg, steps, conditions, etc.) for utilizing or testing the one or more of the software-based components and the hardware-based components.

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

[0053] According to an embodiment, at least a portion of the plurality of nodes 130-1 to 130-N may be configured in a geographical location different from the test case management system 110, different from one or more of the plurality of UEs 120-1 to 120-N, and / or different from another portion of the plurality of nodes 130-1 to 130-N.

[0054] According to an embodiment, at least a portion of the plurality of nodes 130-1 to 130-N may be associated with one or more test environments. For example, the above-mentioned portion of the node may have at least one software-based test environment (e.g., software-in-the-loop (SIL) test environment, virtual ECU (V-ECU) test environment, model-in-the-loop (MIL) test environment, processor-in-the-loop (PIL) test environment, etc.) and / or at least one hardware-based test environment (e.g., hardware-in-the-loop (HIL) test environment) connected to it in a communicative manner (e.g., wired connection, wireless connection, etc.) or deployed therein. In this regard, a portion of the plurality of nodes 130-1 to 130-N may receive one or more test cases (e.g., test cases constructed by a user, test cases associated with a user, etc.) from the test case management system 110, and may be configured to utilize the received test cases to automatically implement tests in the desired software and / or hardware components based on the received test cases.

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

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

[0057] According to an embodiment, the network 140 may include a virtual network, which may include one or more physical network components (e.g., Ethernet, WiFi (Wireless Fidelity) modules, electrical communication network hardware, etc.) installed with one or more virtualized network functions (e.g., controller area network (CAN) bus, etc.).

[0058] Next, refer to Figure 2 , Figure 2 A block diagram of exemplary components of a test case management system 200 is shown in one or more embodiments. The test case management system 200 may be used with Figure 1 The test case management system 110 is similarly.

[0059] like Figure 2 As shown, the test case management system 200 may include at least one communication interface 210, at least one storage 220, and at least one processor 230, but it is understandable that the test case management system 200 may include more components or fewer components than those shown, and / or the components included therein may also be arranged in any manner different from that shown without departing from the scope of the present disclosure.

[0060] The communication interface 210 may include a component such as a transceiver (e.g., a transceiver, a separate receiver and a transmitter, etc.) that enables the test case management system 200 (or one or more components included therein) to communicate with one or more components located outside the test case management system 200 via a wired connection, a wireless connection, or a combination of a wired and wireless connection. For example, the communication interface 210 may connect the test case management system 200 (or one or more components included therein) to multiple UEs (e.g., Figure 1 UE 120-1 to 120-N, etc.) and multiple nodes (e.g., Figure 1 Nodes 130-1 to 130-N, etc.), thereby enabling them to communicate with each other and perform actions on each other. As another example, the communication interface 210 enables the components of the test case management system 200 to communicate with each other. For example, the communication interface 210 can connect the storage 220 to the processor 230, thereby enabling them to communicate with each other and perform actions on each other.

[0061] According to an embodiment, the communication interface 210 may include a hardware-based interface, such as a bus interface, an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, a software interface, or the like. According to an embodiment, the communication interface 210 may include at least one controller area network (CAN) bus, which may be configured to connect the components of the test case management system 200 (e.g., storage 220, processor 230, etc.) to multiple UEs (e.g., UE 120-1 to 120-N) and multiple nodes (e.g., nodes 130-1 to 130-N) in a manner that allows communication. 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.

[0062] According to an embodiment, the communication interface 210 may be configured to receive information from one or more components located outside the test case 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 from multiple UEs in order to manage one or more test cases (e.g., define and build test cases, view test cases, arrange test cases, modify test cases, share test cases, etc.), and the user inputs may be provided to the processor 230 and / or the storage 220.

[0063] Likewise, the communication interface 210 may be configured to enable the processor 230 of the test case management system 200 to provide one or more information to one or more components located outside the test case management system 200. For example, the communication interface 210 may enable the processor 230 to provide or send one or more GUIs to multiple UEs or the like.

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

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

[0066] According to an embodiment, the storage 220 may be configured to store information used by the processor 230 to perform one or more actions to manage one or more test cases for one or more users. For example, the storage 220 may be configured to store one or more test cases constructed or produced by one or more users, store information associated with one or more users, store information of one or more test artifacts, store information of one or more test environments, and perform similar actions.

[0067] At least one processor 230 may be configured to receive (e.g., via the communication interface 210, etc.) one or more signals defining one or more instructions to perform one or more actions. Moreover, the processor 230 may be implemented by hardware, firmware, or a combination of hardware and software. The processor 230 may include a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and / or other types of processing or computing components.

[0068] According to an embodiment, at least one processor 230 may include more than one processor, and the more than one processor may be programmed to implement functions or actions for managing more than one test case. For example, the processor 230 may be configured to execute computer-readable instructions stored in a storage device (e.g., storage device 220, etc.), thereby implementing one or more behaviors or one or more actions described in this specification.

[0069] As an example, at least one processor 230 may generate and present one or more graphical user interfaces (GUIs) to the user when determining the user's access, so that the user can interact with the test case management system 200 that manages one or more test cases (e.g., viewing test cases, retrieving test cases, creating test cases, modifying test cases, sharing test cases, etc.). Figure 3 to Figure 6 2. An illustration of an exemplary GUI that may be generated by processor 230 for interaction with more than one user is provided.

[0070] First, refer to Figure 3 , Figure 3 An exemplary GUI 300 of more than one embodiment is shown. The GUI 300 may be generated by at least one processor (e.g., processor 230) of a test case management system and may be presented to a user by at least one processor to enable the user to retrieve and view information about test cases available to the user and to create or define new test cases.

[0071] According to an embodiment, at least one processor may generate and present GUI 300 when a user initially accesses and / or logs into the test case management system. For example, when determining the user's access (e.g., when receiving an access request from a UE associated with the user, when receiving consent and / or authentication from a security system, when verifying the user's identity, etc.), at least one processor may obtain (from one or more storage media, such as storage 220 and / or an external server, etc.) information associated with the user (which may be referred to as "user information" in this specification), and may generate GUI 300 based on this.

[0072] The user information may include the user's role or profile (e.g., test engineer, business manager, software developer, supplier user, etc.), the user's work group (e.g., the team to which the user belongs, the team of users with whom the user collaborates, etc.), one or more projects associated with the user (e.g., projects in which the user participates, previously built test cases, etc.), places associated with the user (e.g., the user's current place, the last known place associated with the user, the user's planned place, etc.), and / or the like. The user information may be included in one or more user profiles associated with the user, with the result that, when determining the user's access, at least one processor may obtain one or more user profiles from one or more storage media (based on the user's authentication information, e.g., user ID, etc.).

[0073] Therefore, at least one processor may generate GUI 300 based on the acquired user information. For example, at least one processor may determine (based on the acquired user information) which test case is associated with the user, and may select from multiple nodes (e.g., Figure 1 The information of the test cases associated with each other is collected among the nodes 130 - 1 to 130 -N, etc., and the information can be included in the GUI 300 (refer to the first part 310 of the GUI 300, which will be further described below).

[0074] As another example, at least one processor may determine (based on the obtained user information) whether there are any reserved projects (e.g., whether there are any reserved test cases scheduled to be built, etc.), and (if so) determine the progress of the reserved projects, which information may be included in the GUI 300 so that the user can resume work on the reserved projects. Conversely, based on the determination that there are no reserved projects available to the user, the at least one processor may generate the GUI 300 so that the user can quickly start a project to build or make one or more desired test cases (see the second portion 320 of the GUI 300, which will be further described below).

[0075] As another example, at least one processor may determine (based on the obtained user information) which test cases are available to the user, and may select from multiple nodes (e.g., Figure 1 The information of available test cases is collected from the nodes 130 - 1 to 130 -N, etc., and the information can be included in the GUI 300 (refer to the third part 330 of the GUI 300, which will be further described below).

[0076] In some embodiments, at least one processor may continuously (or periodically) obtain the latest user information and update the GUI 300 (if any) in such a way that the GUI 300 may always include updated information of the test cases.

[0077] Reference Figure 3 , GUI 300 may include a first portion 310, a second portion 320, and a third portion 330. The first portion 310 may include a list of test cases associated with the user, and the test cases may be classified into more than one category. Figure 3 In the example of FIG. 1 , the first part 310 includes a list 311, which includes test cases associated with the user, and the test cases are sorted according to the projects involved in the test cases (in Figure 3 X” in the , and teams or workgroups associated with the test cases (in Figure 3 Team Y) and associated functions or features according to the test cases (in Figure 3 It should be understood that the test cases associated with the user may also be classified in any other appropriate manner without departing from the scope of the present disclosure.

[0078] Each of the test cases presented in the first portion 310 may have an interactive element that can be interacted with by a user associated therewith. For example, the description of each test case may be presented in the form of selectable or interactive text that enables the user to select the associated test case when interacted with (e.g., clicked, etc.) by the user.

[0079] The first portion 310 may also include one or more interactive elements for enabling the user to manage the list 311. For example, Figure 3 In the example, the first part 310 may include a button 312, which, when interacted by a user, enables the user to edit the list 311 as follows: name changes associated with each category of test cases in the list 311, reorganization of test cases from one category to another, addition or removal of more than one category, and / or similar actions, etc.

[0080] The second portion 320 may include an input window 321 and a plurality of interactive elements 322, which, when interacted with by the user, enable the user to define and create one or more new test cases. In accordance with an embodiment where there are reserved test cases that are predetermined to be constructed (e.g., the user has partially created the test case and saved the project for further use, etc.), the second portion 320 may include information on the reserved test cases, and the user may continue to perform the above-mentioned reserved test case operations. Furthermore, as described below with reference to Figure 3 As further noted, in some embodiments, the second portion 320 may include information about one or more test cases selected by a user (eg, test cases selected from the first portion 310 and / or the third portion 330 ).

[0081] The input window 321 may be configured to receive one or more user inputs from a user to specify, define, and create one or more test cases. According to an embodiment, a user may simply input a description of a desired test step into the input window 321 to define the desired test case. According to an embodiment, at least one processor may receive one or more inputs defining a desired test case from a user in a first format (e.g., a general format, etc.), and may automatically convert one or more user inputs into a second format (e.g., a specific programming language, a specific format, etc.).

[0082] According to an embodiment, while the user inputs a description into the input window 321, the at least one processor may retrieve a test artifact associated with the description, and may present one or more recommendations to the user in the input window 321. As an example, based on the user's decision to input the terms "ECU A" and "service" into the input window 321, the at least one processor may update the input window 321 and present information about one or more services associated with "ECU A" (using a drop-down list, etc.), with the result that the first user may simply select a desired "service" associated with "ECU A" from the presented recommendations.

[0083] Alternatively or in addition, the user can make or construct a new test case by utilizing one or more templates. For example, the user can select (e.g., drag and drop, double-click, etc.) one or more available test cases presented through the first part 310 and / or the third part 330, and / or can double-click in the input window 321, and at least one processor can generate additional interactive elements (e.g., pop-up windows, text input fields, etc.), so that the user can face the directory configured with the desired template and upload the template from the directory. Therefore, the user can use the template to construct or make a desired new test case. Below, refer to Figure 6An exemplary GUI that enables a user to utilize a test case template is described below.

[0084] It is understandable that the input window 321 may also be configured to accept one or more first user inputs for defining the first part of the desired test case via a description, and accept one or more second user inputs for defining the second part of the desired test case via the use of a template. For example, the user may define the first part of the test step or test condition by manually inputting a description in the input window 321, or may define the second part of the test step or test condition by modifying the test case template.

[0085] Furthermore, each of the plurality of interactive elements 322 may trigger the execution of one or more associated behaviors or actions through interaction by a user. Figure 3 In the example of , the "Cancel" button can trigger at least one processor through interaction by the user to end the ongoing action (for example, closing GUI 300, redirecting the user to a page before GUI 300, logging the user out of the test case management system, etc.). Moreover, the "Save" button can trigger at least one processor through interaction by the user to enable the user to create a project file (or any other suitable file or document) provided to the input window 321, the first part 310 and / or the third part 330, including the current progress, composition or the like. Moreover, the "Create" button can trigger at least one processor through interaction by the user to create a test case file including the description or composition provided by the user in the input window 321 specifying one or more new test cases. According to an embodiment, when creating a test case file, at least one processor can store the created test case file in one or more storage media, thereby making the created test case public to selected users (hereinafter, refer to Figure 4 Further documenting the functionality associated with sharing of test cases).

[0086] The third part 330 may include components and information associated with test cases available to the user. Figure 3 As shown, in some embodiments, the third portion 330 may include a first sub-portion 331 and a second sub-portion 332. The first sub-portion 331 may include a search bar (or any other suitable interactive element) that enables a user to input one or more criteria (e.g., keywords, etc.) that define one or more test cases of interest. Figure 3In the example shown in FIG. 1 , the user inputs the keywords “ECU A” and “verification” into the first subsection 331, and the user is interested in viewing the available test cases associated with the verification test of ECU A. Thus, at least one processor can receive from a plurality of nodes (e.g., Figure 1 The nodes 130 - 1 to 130 -N, etc.) obtain information of test cases associated with ECU A and / or verification tests, and the second sub-unit 332 can be updated and present the acquired information.

[0087] In some embodiments, in addition to one or more user input criteria, at least one processor may also take user information into consideration when retrieving available test cases. Figure 3 In the example, when obtaining information of test cases associated with ECUA and / or verification tests, at least one processor can determine which test case is associated with the user's role or image, which test case is approved for presentation to the user, and which test case is associated with the project and similar issues associated with the user. Then, only the determined test case can be presented to the user.

[0088] The second subsection 332 may include components and information associated with available test cases of interest to the user. Figure 3 As shown, the second subsection 332 includes a plurality of selectable texts associated with the benchmarks (e.g., "ECU A" and "Verification") provided by the user in the first subsection 331. Each of the selectable texts in the second subsection may, for example, be associated with a respective category of the test case, and may include more than one subsection when the user interacts (e.g., selects, clicks, taps, etc.). In some embodiments, one or more of the plurality of subsections may further include more than one subsection. For example, in Figure 3 In the example of , at least one processor finds multiple test cases associated with the verification test including ECU A, and on the other hand, the user first selects the selectable text associated with "Verification Test 1". Therefore, at least one processor can update the second sub-section 332 to display the selectable text associated with the available test cases associated with "Verification Test 1".

[0089] According to an embodiment, one or more of the test cases presented in the second sub-section 332 can realize the interaction performed by the user when specifying or making one or more new test cases. For example, when the user makes one or more new test cases, one or more parts of the test cases presented in the second sub-section 332, such as the entire content of the test case, the steps of the test case, or the like, can be dragged and dropped to the input window 321 of the second part 320. In addition, the user can build or make a new test case in the second part 320 while referring to one or more available test cases presented in the third part 330. For example, when determining one or more user interactions related to selectable text in the second sub-section 332, at least one processor can present (in an additional GUI, an additional part of the GUI 300, etc.) the content of the test case associated with the selectable text that has been interacted with, as a result, the user can read the content of the selected test case from it. It is understandable that one or more of the test cases presented in the first part 310 can also realize the interaction performed by the user in the same way when specifying or making one or more new test cases.

[0090] Furthermore, the user may also add one or more of the test cases presented in the second subsection 332 to the list 311 in the first portion 310, so that the user can easily access the test cases in the future. For example, the user may also drag and drop selectable text associated with a desired test case to the first portion 310, and the at least one processor may update the first portion 310 to include the test case associated with the selectable text.

[0091] In view of the above circumstances, exemplary embodiments of the present disclosure provide a test case management system that generates and presents one or more GUIs that enable one or more users to easily and efficiently browse, search, and create one or more test cases.

[0092] Next, refer to Figure 4 , Figure 4 An exemplary GUI 400 is shown for more than one embodiment. The GUI 400 may be generated by at least one processor (e.g., processor 230) of a test case management system and may be presented to a user by at least one processor to enable the user to view and construct test cases associated with the user. Figure 4 In the example, the user can use Figure 3 After using GUI 300 to create a new test case, GUI 400 is generated and presented to the user.

[0093] GUI 400 may include a first portion 410, a second portion 420, and a third portion 430. First portion 410 may include a list of test cases associated with a user and one or more interactive elements associated with actions for managing the list in the same manner as described above with reference to first portion 310 of GUI 300. Therefore, a lengthy description of the association may be omitted below for the sake of brevity.

[0094] The second part 420 may include a browsing window 421 configured to present information of the test case selected by the user in the first part 410, and may include a plurality of interactive elements 422 for enabling the user to manage the selected test case. Figure 4 In the example of , the user interacts with the selectable text associated with "test case 1" in the first portion 410, and thus, at least one processor may obtain information associated with the selected test case and may update the browsing window 421 to present the content of the selected test case. According to an embodiment in which the user selects a portion of the test case (e.g., one or more test steps, etc.), at least one processor may update the browsing window 421 to present only the selected portion of the test case.

[0095] Furthermore, each of the plurality of interactive elements 422 may trigger the execution of one or more associated behaviors or actions through interaction by a user. Figure 4 In the example of , the “Cancel” button may trigger at least one processor through interaction by the user to end the ongoing action (e.g., closing GUI 400, redirecting the user to a previous page of GUI 400, erasing the content presented in browsing window 421, etc.). Moreover, the “Edit” button may trigger at least one processor through interaction by the user to update the third part 430 to include information and elements that enable the user to edit the selected test case. Moreover, the “Template” button may trigger at least one processor through interaction by the user to update the GUI 400 to include information and elements that enable the user to use the selected test case as a template and define or create one or more new test cases, or may generate an additional GUI that may include information and elements that enable the user to use the selected test case as a template and define or create one or more new test cases (hereinafter, refer to Figure 6 To record an exemplary GUI including the above information and elements).

[0096] The third section 430 may include a plurality of interactive elements that enable a user to modify or edit a test case selected by the user in the first section 410 or the second section 420. Figure 4 In the example of , the third portion 430 includes multiple interactive elements 432 associated with an action of modifying the composition of sharing the selected test case ("Test Case 1"). Specifically, the multiple interactive elements 432 include multiple check boxes, each of which is associated with a user group with which the user may share the selected test case. The user can select one or more of the user groups presented in the third portion 430 by clicking or checking the associated text box, and at least one processor can determine which of the multiple text boxes is interacted by the user, can determine the user group associated with it, and can update the shared composition of the selected test case so that the selected test case can be identified and accessed by the user group selected by the user.

[0097] Furthermore, the plurality of interactive elements 432 may also include a plurality of buttons, each of which may trigger the execution of one or more associated behaviors or actions through interaction by a user. Figure 4 In the example of , the "Save" button can trigger at least one processor through interaction by the user to collect information of the check box selected by the user, determine the user group associated with the check box selected by the user, and update the shared composition of the selected test case based on this. Moreover, the "Edit" button can trigger at least one processor through interaction by the user to generate and present one or more additional GUIs, which include information and elements that enable the user to edit multiple text boxes (for example, adding new text boxes and new user groups associated with them, deleting existing text boxes and user groups associated with them, arranging the order of existing text boxes and user groups associated with them, etc.) and / or edit available user groups (for example, changing the name of the user group, setting one or more user groups as default, etc.). Moreover, the "Default" button can trigger at least one processor through interaction by the user to restore the shared composition of the selected test case to the default composition.

[0098] In view of the above circumstances, exemplary embodiments of the present disclosure provide a test case management system that generates and presents one or more GUIs that enable one or more users to easily and efficiently view, use, and configure one or more associated test cases.

[0099] GUI 300 and GUI 400 are described in this specification as separate GUIs, but it is understood that the user can also use any appropriate method to configure the GUI to include the information and / or elements of interest. For example, the user can configure GUI 300 to include a test case browser (e.g., the second part 420 of GUI 400), can configure GUI 400 to include a test case library (e.g., the third part 330 of GUI 300), and can also perform similar actions.

[0100] For example, refer to Figure 5 , Figure 5 An exemplary GUI 500 is shown for more than one embodiment. The GUI 500 may be generated by at least one processor (e.g., processor 230) of the test case management system based on user-defined configurations. Figure 5 In the example of GUI 500, GUI 500 includes a first portion 510 that is the same as third portion 330 of GUI 300 and a second portion 520 that is the same as second portion 420 of GUI 400. Therefore, a lengthy description associated therewith may be omitted below for the sake of brevity.

[0101] Taking the above into consideration, an exemplary embodiment of the present disclosure provides a test case management system that enables one or more users to freely customize how one or more GUIs should be specifically presented. As a result, the one or more users can utilize the test case management system in the manner they desire, thereby easily and efficiently managing one or more test cases.

[0102] Next, refer to Figure 6 , Figure 6 An exemplary GUI 600 is shown for more than one embodiment. The GUI 600 may be generated by at least one processor of the test case management system (e.g., processor 230) and presented to a user by at least one processor when creating and defining a new test case so that the user can use available test cases (e.g., test cases previously constructed by the user or by another user, etc.) as templates. For example, in Figure 6 In the example of , GUI 600 may be generated and presented to a user via at least one processor based on a determination of a user interaction associated with a “Template” button in second portion 420 of GUI 400 or second portion 520 of GUI 500 and the like.

[0103] like Figure 6 As shown, GUI 600 may include an input window 610 and a plurality of interactive elements 620. The duties and functions of the plurality of interactive elements 620 may be the same as those described above with reference to Figure 3Similarly, the plurality of interactive elements 322 within the GUI 300 described above may be described above, and therefore, the lengthy description associated therewith may be omitted below for the sake of brevity.

[0104] The input window 610 may include the content of the test case selected as the template. On the other hand, the above content may be presented in one or more editable formats so that the user can simply modify one or more desired content in a desired manner. Figure 6 In the example, the title of the selected test case and the test steps included in the selected test case are each presented in a plurality of editable formats.

[0105] Specifically, the editable text 611 can be associated with the title of the new test case to be constructed based on the selected test case template, and the editable text 611 can trigger at least one processor through interaction by the user to receive one or more user inputs for defining or changing the title of the new test case to be constructed. According to an embodiment, at least one processor can generate the editable text 611 based on a default structure (such as a structure set by the user). For example, in Figure 6 In the example of FIG. 6 , at least one processor may generate GUI 600 to include a default title by configuring a default naming structure of a term such as “(copy)” after the original title of the selected test case in first portion 610 .

[0106] Furthermore, the editable text 612 may be associated with the first test step of the selected test case, and the editable text 612 may include a plurality of input fields (in Figure 6 denoted as "{}"), each input field can trigger at least one processor through interaction by a user to receive one or more user inputs defining one or more parameters of the first test step. The one or more parameters may include parameters defining software-based components (e.g., the name of a virtual ECU, the name of a signal frame, etc.), parameters defining hardware-based components (the name of a physical bus, etc.), parameters defining a period (e.g., values ​​of seconds, minutes, etc.), parameters defining the fidelity of the test environment (e.g., hardware resources, simulation resources, emulation resources, etc.), and / or any other appropriate parameters that, when combined with the description of the test step, form one or more test conditions of a test case.

[0107] According to an embodiment, at least a portion of the multiple input fields of the editable text can be pre-recorded by at least one processor, or can be pre-filled. Specifically, the multiple input fields of the editable text 613 can be pre-recorded by at least one processor, or can be pre-filled, for example, based on user information of more than one user. For example, at least one processor can determine which parameter is the most common when defining the same (or identical) test steps based on the usage history of multiple users, and then, it can be automatically recorded in the multiple input fields when the GUI 600 is generated. As another example, at least one processor can determine which parameter is used most when defining and making new test cases based on the user's usage history, and then, it can be automatically recorded in the multiple input fields when the GUI 600 is generated.

[0108] According to an embodiment, at least one processor may present one or more selectable options for parameters in at least a portion of multiple input fields of editable text. Specifically, at least one processor may determine the type of parameter associated with each input field, may collect information about possible parameters from multiple nodes (e.g., nodes 130-1 to 130-N), and may present possible parameters in the associated input field for user selection. For example, when generating GUI 600, at least one processor may determine that the first input field of editable text 614 is associated with a parameter that defines a period, may collect information about available resources and / or available test environments that may be constructed from multiple nodes, may determine possible parameters that define a period, and then may include possible parameters in the first input field in the form of a drop-down list.

[0109] It is understood that the input fields associated with each test step of the selected test case are only recorded and shown in various ways in this specification for illustrative purposes. In fact, all input fields of all test steps may be the same (for example, all input fields are automatically pre-filled, etc.) or of the same type without departing from the scope of the present disclosure.

[0110] With the above in mind, an exemplary embodiment of the present disclosure provides a test case management system that enables one or more users to utilize one or more available test cases, for example, one or more test cases constructed and shared by other users, one or more test cases constructed by one or more users, and / or the like, with the result that the one or more users can use the one or more available test cases as templates in order to create one or more new test cases.

[0111] Reference Figure 3 to Figure 6, the above-mentioned GUIs in this specification are only examples of possible implementations, and it is understood that the scope of the present disclosure should not be limited to this. Specifically, one or more of the above-mentioned GUIs may include more information or components than the information or components shown, or less information or components, and / or may be configured in a manner different from that shown. For example, without departing from the scope of the present disclosure, GUI 300 may also include a fourth portion that enables a user to configure a shared configuration of one or more test cases in the same manner as described above with reference to the third portion 430 of GUI 400, and GUI 500 may also include an additional portion that indicates a list of test cases associated with a user in the same manner as described above with reference to the first portion 310 of GUI 300, and may also perform similar actions.

[0112] In view of the above, at least one processor of the test case management system may be configured to generate an appropriate GUI and present it to the user, and the user may easily and efficiently manage one or more test cases by interacting with the presented GUI.

[0113] Next, refer to Figure 7 To record actions that can be performed by at least one processor (eg, processor 230) of the test case management system. Figure 7 , Figure 7 A flow chart of an exemplary method 700 for managing one or more test cases for testing software associated with a vehicle system in accordance with one or more embodiments is shown. One or more actions of the method 700 may be performed by at least one processor when executing computer executable instructions stored in at least one storage memory (e.g., memory 220). The software being tested may include an onboard electronic control unit (ECU) and / or any other software associated with a vehicle system.

[0114] like Figure 7 As shown, in action S710, at least one processor may be configured to present (may be referred to as "one or more available test cases" in this specification) information associated with one or more test cases available to the user. Specifically, at least one processor may present a first GUI having information about one or more available test cases to the user.

[0115] The first GUI may include (refer to Figure 3 to Figure 6One or more information or components related to one or more of GUIs 300 to 600 described above. For example, the first GUI may include the first portion 310 and / or the third portion 330 of GUI 300, may include the first portion 410 of GUI 400, may include the first portion 510 of GUI 500, and / or the like.

[0116] According to an embodiment, at least one processor may obtain information associated with a user (may be referred to as "user information" in this specification) from one or more storage media (e.g., storage 220, a server located outside the test case management system, etc.), may determine one or more available test cases based on the obtained user information, may generate a first GUI including information associated with one or more available test cases, may send the first GUI to at least one user device associated with the user (e.g., UE 120-1 to 120-N, etc.), thereby presenting the first GUI to the user. The user information may include, for example, the user's responsibilities (e.g., test engineer, software developer, etc.), projects associated with the user (e.g., projects assigned to the user, projects managed by the user, etc.), workgroups associated with the user (e.g., teams of users with whom the user collaborates, etc.), and places associated with the user (e.g., current place, last known place, planned place, etc.).

[0117] Thereafter, in action S720, at least one processor may be configured to receive user input from a user defining a user selection of a test case from one or more available test cases (which may be referred to as a "user-selected test case" in this specification). For example, the first GUI has one or more interactive elements (e.g., selectable text, etc.), each of which is associated with an available test case from one or more available test cases (e.g., referring to the description of the association with the selectable text of the first part 310 and the third part 330 of the GUI 300). In this regard, at least one processor may be configured to receive the user input by: receiving a user interaction associated with at least one of the one or more interactive elements; and determining the available test case associated with the at least one interactive element on which the user interaction was performed as the user-selected test case.

[0118] Furthermore, in action S730, the at least one processor may be configured to perform one or more actions for managing the test case selected by the user. For example, the at least one processor may present a second GUI to the user, the second GUI having information associated with the test case selected by the user. The second GUI may include (respectively referring to Figure 3 to Figure 6 The second GUI may include one or more information or components related to one or more of the GUIs 300 to 600 described above. For example, the second GUI may include the third portion 330 of the GUI 300, the second portion 420 of the GUI 400, the second portion 520 of the GUI 500, the input window 610 of the GUI 600, and / or the like. Through the second GUI, the user may use the selected test case as a template in order to create a new test case.

[0119] For example, at least one processor may receive one or more user inputs from a user to modify at least a portion of the information associated with the test case selected by the user. Thereafter, at least one processor may generate a new test case based on the user input, the new test case having at least a portion of information different from the test case selected by the user.

[0120] As an example, the information associated with the test case selected by the user may include a title, a label, or a description associated with the test case selected by the user, and the at least one processor may receive, via the second GUI, the title, label, and / or description (e.g., reference and reference) of the test case selected by the user. Figure 6 The editable text 611 provided as described above establishes one or more user inputs for modification of the associated description. Thus, at least one processor may generate a new test case with a modified title, label and / or description.

[0121] As another example, the information associated with the test case selected by the user may include one or more test steps associated with the test case selected by the user, and the second GUI may include one or more test steps (for example, reference and reference) associated with the test case selected by the user. Figure 6 The input fields for the editable text 612 to 614 provided as described above are associated with each other) at least one input field is associated with each other.

[0122] In this regard, at least one processor may be configured to receive user input via the second GUI by receiving a user selection related to at least one parameter defining a test step, and at least one processor may be configured to generate a new test case by generating a new test case based on the user defined test step. Figure 6The at least one parameter may include at least one of the following parameters: parameters defining software-based components (e.g., software-based ECU, etc.), parameters defining hardware-based components (e.g., hardware-based ECU, etc.), parameters defining periods (e.g., values ​​of seconds, minutes, etc.), parameters defining the fidelity of the test environment (e.g., hardware resources, simulation resources, emulation resources, etc.) and / or any other appropriate parameters.

[0123] Specifically, at least one processor may receive one or more user inputs in at least one input field from a user (e.g., one or more keywords associated with at least one parameter). Further or alternatively, at least one input field may include parameters pre-recorded by at least one processor. In this case, at least one processor may receive from the user consent for the pre-recorded parameters (e.g., user interaction related to the interactive element with which the association is established, etc.), or modifications to the pre-recorded parameters (e.g., revisions of the pre-recorded parameters, etc.). Further or alternatively, at least one input field may include (e.g., in the form of a drop-down list, etc.) a plurality of selectable parameters. In this case, at least one processor may receive from the user at least one user selection for at least one parameter among the plurality of selectable parameters.

[0124] Therefore, exemplary embodiments of the present disclosure provide a test case management system (and a method using the same) to enable more than one user to effectively and efficiently manage more than one test case, thereby addressing the problems of the related art as described above.

[0125] It should be understood that the specific order or hierarchy of the functional blocks in the process / flowchart disclosed in this specification is an example of an exemplary scheme. It should be understood that the specific order or hierarchy of the functional blocks in the process / flowchart can be reconfigured based on design preferences. Moreover, a portion of the functional blocks can be combined or omitted. The accompanying method claims present the elements of the various functional blocks in an exemplary order and are not intended to be limited to the specific order or hierarchy presented.

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

[0127] A computer-readable storage medium may be a tangible device that can hold and store instructions used by an instruction execution device. A computer-readable storage medium may be, for example, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the above, but is not limited to these. A more specific exemplary non-exhaustive list of computer-readable storage media includes the following, namely, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), static random access memories (SRAM), portable compact disc read-only memories (CD-ROM), digital versatile discs (DVD), memory sticks, floppy disks, punched cards with instructions recorded or mechanically encoded devices such as raised structures in grooves, and any suitable combination of the above. The computer-readable storage medium used in this specification should not be interpreted as a temporary signal itself such as an electric wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (for example, a light pulse through an optical cable), or an electrical signal sent through a wire.

[0128] The computer-readable program instructions recorded in this specification can be downloaded from a computer-readable storage medium to a respective computing / processing device, or downloaded to an external computer or 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 have copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and transmits the computer-readable program instructions to be stored in a computer-readable storage medium in the respective computing / processing device.

[0129] The computer readable program code / instructions for performing the actions may be source code or object code written in assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state setting data, configuration data for integrated circuits, or any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++ or similar languages, and procedural programming languages ​​such as the "C" programming language or similar programming languages. The computer readable program instructions may be executed entirely on the user's computer, may be executed partially on the user's computer, may be executed as a stand-alone software package, may be executed partially on the user's computer and partially on a remote computer, or may be executed entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network including a local area network (LAN) or a wide area network (WAN), or a connection to an external computer may be made (e.g., using an Internet service provider and thereby via the Internet). 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) uses state information of computer-readable program instructions to personalize the electronic circuit, thereby executing the computer-readable program instructions to implement programs or actions.

[0130] 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 device in order to generate a machine, and as a result, the instructions executed by the processor of the computer or other programmable data processing device generate a component that implements the function / behavior specified in the functional block or functional blocks (multiple) of the flowchart and / or block diagram. The computer-readable program instructions may also be stored in a computer-readable storage medium, which may instruct a computer, a programmable data processing device, and / or other equipment to function in a specific manner, and as a result, the computer-readable storage medium having the instructions stored therein has an article of manufacture, which includes instructions for implementing the scheme of the function / behavior specified in the functional block or functional blocks (multiple) of the flowchart and / or block diagram.

[0131] Computer-readable program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other device, and cause the computer, other programmable apparatus, or other device to perform a series of action steps, thereby generating a computer installation process, as a result of which the instructions executed on the computer, other programmable apparatus, or other device implement the functions / behaviors specified in the functional box or functional boxes (multiple) in the flowchart and / or block diagram.

[0132] The flowchart and block diagram in the figure show the architecture, function and action of possible implementation of the system, method and computer-readable medium of various implementations. In this regard, each functional block in the flowchart or block diagram can represent a module, segment or part of an instruction that has more than one execution possible instruction to implement the specified logical function. Compared with those depicted in the accompanying drawings, the method, computer system and computer-readable medium may include additional functional blocks, fewer functional blocks, different functional blocks or functional blocks of different configurations. In a partially replaced implementation, the functions recorded in the functional blocks can be generated independently of the order recorded in the figure. For example, two functional blocks shown in succession can be executed in fact at the same time or substantially at the same time, or the functional blocks can be executed in reverse order according to the associated functions. It should be noted that each functional block of the block diagram and / or flowchart, and the combination of the functional blocks of the block diagram and / or flowchart can be implemented by a dedicated hardware-based system that implements the specified function or behavior, or executes a combination of dedicated hardware and computer instructions.

[0133] It is apparent that the systems and / or methods described in this specification 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 system and / or method is not a limitation of the implementation. Therefore, it is understood that the actions and behaviors of the system and / or method are described in this specification without reference to specific software code, and that software and hardware may be designed to implement the system and / or method based on the description of this specification.

Claims

1. A test case management method is a method for managing one or more test cases for testing software associated with a vehicle system, wherein: The method is implemented by at least one processor, and includes: Presenting a first graphical user interface GUI to a user, the first graphical user interface having information of one or more test cases available to the user; receiving user input from the user defining a user selection of a test case to be performed from among the one or more available test cases; and At least one action of managing the test case selected by the user is performed.

2. The test case management method according to claim 1, wherein: The presenting of the first graphical user interface comprises: Acquire information associated with the user from at least one storage medium; Determining the one or more available test cases based on the acquired user information; generating the first graphical user interface in a manner including information associated with the one or more available test cases; and The first graphical user interface is sent to a user device associated with the user.

3. The test case management method according to claim 1 or 2, wherein: The first graphical user interface has one or more interactive elements, each of the one or more interactive elements is associated with an available test case among the one or more available test cases, and the receiving of the user input includes: receiving a user interaction associated with at least one interactive element among the one or more interactive elements; and The available test case associated with at least one interactive element with which the user interacted is determined as the test case selected by the user.

4. The test case management method according to any one of claims 1 to 3, wherein: The performing of the at least one action comprises: Presenting a second graphical user interface to the user, the second graphical user interface having information associated with the test case selected by the user; receiving user input from the user to modify at least a portion of the information associated with the test case selected by the user; and generating new test cases based on the user input, The new test case has at least a portion of information that is different from the test case selected by the user.

5. The test case management method according to any one of claims 2 to 4, wherein: The acquired user information includes at least one of the following information: the role of the user, the project associated with the user, the work group associated with the user, and the place associated with the user.

6. The test case management method according to claim 4 or 5, wherein: The information associated with the test case selected by the user includes at least one test step associated with the test case selected by the user. The second graphical user interface comprises at least one input field associated with the at least one test step, The receiving of the user input includes: receiving a user selection of at least one parameter defining the at least one test step, The generating of the new test case includes generating the new test case based on at least one test step defined by the user.

7. The test case management method according to claim 6, wherein: The receiving of the user selection for the at least one parameter comprises: receiving one or more user inputs from the user in the at least one input field, The one or more user inputs include one or more keywords associated with the at least one parameter.

8. The test case management method according to claim 6 or 7, wherein: The at least one input field has pre-entered parameters, The receiving of the user selection for the at least one parameter comprises: An agreement to the pre-posted parameters or a modification to the pre-posted parameters is received from the user.

9. The test case management method according to any one of claims 6 to 8, wherein: The at least one input field has a plurality of selectable parameters, and the receiving of the user selection for the at least one parameter comprises: At least one user selection is received from the user for at least one parameter among the plurality of selectable parameters.

10. The test case management method according to any one of claims 6 to 9, wherein: The at least one parameter comprises at least one of the following parameters: a parameter defining a software-based ECU, a parameter defining a hardware-based ECU, and a parameter defining the fidelity of a test environment.

11. A test case management system is a system for managing one or more test cases for testing software associated with a vehicle system, wherein: The system has: A storage memory storing instructions; as well as at least one processor, The at least one processor is configured to execute the instructions so that presenting a first graphical user interface GUI to a user, the first graphical user interface having information of one or more test cases available to the user, receiving user input from the user defining a user selection of a test case to be performed from among the one or more available test cases, At least one action of managing the test case selected by the user is performed.

12. The test case management system according to claim 11, wherein: The at least one processor is configured to execute the instructions to present the first graphical user interface by: Acquire information associated with the user from at least one storage medium; Determining the one or more available test cases based on the acquired user information; generating the first graphical user interface in a manner including information associated with the one or more available test cases; as well as The first graphical user interface is sent to a user device associated with the user.

13. The test case management system according to claim 11 or 12, wherein: The first graphical user interface has one or more interactive elements, each of the one or more interactive elements is associated with an available test case among the one or more available test cases. The at least one processor is configured to execute the instructions to receive the user input by: receiving a user interaction associated with at least one interactive element among the one or more interactive elements; as well as The available test case associated with at least one interactive element with which the user interacted is determined as the test case selected by the user.

14. The test case management system according to any one of claims 11 to 13, wherein: The at least one processor is configured to execute the instructions to implement the at least one action by: Presenting a second graphical user interface to the user, the second graphical user interface having information associated with the test case selected by the user; receiving a user input from the user to modify at least a portion of the information associated with the test case selected by the user; as well as generating new test cases based on the user input, The new test case has at least a portion of information that is different from the test case selected by the user.

15. The test case management system according to any one of claims 12 to 14, wherein: The acquired user information includes at least one of the following information: the role of the user, the project associated with the user, the work group associated with the user, and the place associated with the user.

16. The test case management system according to claim 14 or 15, wherein: The information associated with the test case selected by the user includes at least one test step associated with the test case selected by the user. The second graphical user interface comprises at least one input field associated with the at least one test step, The at least one processor is configured to execute the instructions to receive the user input by: receiving a user selection of at least one parameter defining the at least one test step, The at least one processor is configured to execute the instructions to generate the new test case by: generating the new test case based on at least one test step defined by the user.

17. The test case management system according to claim 16, wherein: The at least one processor is configured to execute the instructions to receive the user selection for the at least one parameter by: receiving one or more user inputs in the at least one input field from the user, The one or more user inputs include one or more keywords associated with the at least one parameter.

18. The test case management system according to claim 16 or 17, wherein: The at least one input field has pre-recorded parameters, and the at least one processor is configured to execute the instructions so that The user selection for the at least one parameter is received by receiving from the user an agreement for the pre-written parameter or a modification for the pre-written parameter.

19. The test case management system according to any one of claims 16 to 18, wherein: The at least one input field has a plurality of selectable parameters, and the at least one processor is configured to execute the instructions, thereby The user selection for the at least one parameter is received by receiving at least one user selection for at least one parameter among the plurality of selectable parameters from the user.

20. The test case management system according to any one of claims 16 to 19, wherein: The at least one parameter comprises at least one of the following parameters: a parameter defining a software-based ECU, a parameter defining a hardware-based ECU, and a parameter defining the fidelity of a test environment.

Images