Test case multiplexing method and related device
Through the communication of the target standard protocol between the test verification software and the target calibration software, the update test files and target script files are used to solve the problem that test cases cannot be reused between different calibration software, and the flexible reuse of test cases is achieved and efficiency improvement.
Patent Information
- Application Number
- CN202411263726.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-10
- Publication Date
- 2024-12-13
AI Technical Summary
In the prior art, test cases cannot be reused between different calibration software, resulting in ECU-Test manufacturers need to customize the development of different calibration software, which consumes time and cost money, and test cases are not flexible.
Through the test verification software and the target calibration software, obtain the tasks in the target test case and determine whether the standard protocol is in compliance with the standard protocol; if it does not comply, use the update test file to call the target script file and execute the target interface to achieve the goal function to achieve multiplexing of test cases.
There is no need to redevelop test cases, shorten development cycles, reduce costs, improve test efficiency, and achieve flexible reuse of test cases.
Smart Images
Figure CN119127705A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of testing, and in particular to a test case reuse method and related devices. Background Art
[0002] ECU-Test is a software for testing and verifying embedded systems. INCA is a calibration software. ECU-Test can be connected to INCA to complete the automated testing process. ECU-Test can send calibration instructions to INCA to complete the calibration work without manually writing calibration-related instructions.
[0003] There are many types of calibration software, such as WICAS. Since the test verification software calls different calibration software in different interface implementations, the test cases adapted to one calibration software cannot be used on another calibration software, and the test cases cannot be reused between different calibration software. For example, in ECU-Test, some test cases adapted to INCA cannot be automatically tested in WICAS.
[0004] In the related technology, ECU-Test manufacturers need to carry out customized development for different calibration software and develop new test cases for testing, but this takes a lot of time and money, and the test cases cannot be used flexibly. Summary of the invention
[0005] In view of this, the purpose of this application is to provide a test case reuse method and related devices, which can reuse test cases without redeveloping test cases that match the target calibration software, shorten the development cycle, reduce costs, and improve test efficiency. The specific scheme is as follows:
[0006] On the one hand, the present application provides a test case reuse method, wherein the test verification software includes multiple test cases, the test cases include multiple tasks, the test verification software communicates with the target calibration software through a target standard protocol, the target calibration software has multiple interfaces, each of the interfaces corresponds to an implementation method of each function in the target calibration software, and the method includes:
[0007] Obtaining a target task in a target test case through the test verification software; the target task is used to achieve a target function;
[0008] Determining whether the target task complies with the target standard protocol;
[0009] If not, calling the target script file based on the updated test file of the target test case; the updated test file includes instruction information for calling the target script file;
[0010] During the execution of the target script file, the target interface of the target calibration software is called, and the implementation method of the target function is executed to realize the target function.
[0011] Specifically, before obtaining the target task in the target test case through the test verification software, the method further includes:
[0012] Obtain the test file of the target test case through a use case conversion tool;
[0013] For each target task recorded in the test file, determining whether the target task complies with the target standard protocol;
[0014] If not, the target task in the test file is deleted, and the instruction information in the test file for calling the target task is modified to instruction information for calling the target script file to obtain the updated test file.
[0015] Specifically, the method further includes:
[0016] If the target task complies with the target standard protocol, the target task is executed through the test verification software to achieve the target function.
[0017] Specifically, judging whether the target task complies with the target standard protocol includes:
[0018] Acquire a task set that meets the target standard protocol;
[0019] It is determined whether the target task is in the task set.
[0020] Specifically, calling the target interface of the target calibration software includes:
[0021] Obtaining a first identifier of a target task that does not conform to the target standard protocol;
[0022] When the second identifier of the target interface is consistent with the first identifier, the target interface of the target calibration software is called.
[0023] On the other hand, the embodiment of the present application further provides a test case multiplexing device, the test verification software includes multiple test cases, the test cases include multiple tasks, the test verification software communicates with the target calibration software through the target standard protocol, the target calibration software has multiple interfaces, each of the interfaces corresponds to the implementation method of each function in the target calibration software, and the device includes:
[0024] A first acquisition unit is used to acquire a target task in a target test case through the test verification software; the target task is used to achieve a target function;
[0025] A first judging unit, used to judge whether the target task complies with the target standard protocol;
[0026] A first calling unit, configured to call a target script file based on an updated test file of the target test case if no; the updated test file includes instruction information for calling the target script file;
[0027] The first execution unit is used to call the target interface of the target calibration software and execute the implementation method of the target function during the execution of the target script file to realize the target function.
[0028] Specifically, the device also includes:
[0029] A second acquisition unit, used to acquire the test file of the target test case through a use case conversion tool;
[0030] A second judging unit, configured to judge, for each target task recorded in the test file, whether the target task complies with the target standard protocol;
[0031] The second calling unit is used to delete the target task in the test file if no, and modify the instruction information in the test file for calling the target task to the instruction information for calling the target script file to obtain the updated test file.
[0032] Specifically, the device also includes:
[0033] The second execution unit is used to execute the target task through the test verification software to achieve the target function if the target task complies with the target standard protocol.
[0034] In another aspect, an embodiment of the present application provides a computer device, the computer device comprising a processor and a memory:
[0035] The memory is used to store program code and transmit the program code to the processor;
[0036] The processor is configured to execute the method described above according to the instructions in the program code.
[0037] On the other hand, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium is used to store a computer program, and the computer program is used to execute the method described in the above aspects.
[0038] The embodiment of the present application provides a test case reuse method and related devices, the test verification software includes multiple test cases, the test case includes multiple tasks, the test verification software communicates with the target calibration software through the target standard protocol, the target calibration software has multiple interfaces, each interface corresponds to the implementation method of each function in the target calibration software, that is, the target calibration software has an implementation method corresponding to certain functions. The target task in the target test case is obtained through the test verification software; the target task is used to implement the target function; it is determined whether the target task complies with the target standard protocol; if not, it means that the target task cannot adapt to the target calibration software, and the target calibration software cannot execute the target task to implement the corresponding target function, then the target script file can be called based on the update test file of the target test case, wherein the update test file includes instruction information for calling the target script file; during the execution of the target script file, the target interface of the target calibration software is called, and the implementation method of the target function is executed to implement the target function. In summary, in this application, by developing a large number of interfaces on the target calibration software, when the target task representing the target function cannot be executed, the test verification software can call the target interface, and through the target interface, the target function implementation method provided by the target calibration software can be used to implement the target function. In this way, for tasks that cannot be executed in the test case, the implementation method provided by the target calibration software can be used to complete them instead, so that the test case can be reused without redeveloping the test case that matches the target calibration software, which can shorten the development cycle, reduce costs, and can reuse a large number of test cases, thereby improving test efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0039] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0040] Figure 1 A flow chart of a test case reuse method provided in an embodiment of the present application is shown;
[0041] Figure 2 A flow chart of another test case reuse method provided in an embodiment of the present application is shown;
[0042] Figure 3 A flow chart of another test case reuse method provided in an embodiment of the present application is shown;
[0043] Figure 4 A structural block diagram of a test case reuse device provided in an embodiment of the present application;
[0044] Figure 5 A structural diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0045] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are described in detail below with reference to the accompanying drawings.
[0046] In the following description, many specific details are set forth to facilitate a full understanding of the present application, but the present application may also be implemented in other ways different from those described herein, and those skilled in the art may make similar generalizations without violating the connotation of the present application. Therefore, the present application is not limited to the specific embodiments disclosed below.
[0047] To facilitate understanding, a test case reuse method and related devices provided in an embodiment of the present application are described in detail below in conjunction with the accompanying drawings.
[0048] refer to Figure 1 As shown, it is a flow chart of a test case reuse method provided in an embodiment of the present application, and the method may include the following steps.
[0049] S101, obtaining a target task in a target test case through test verification software.
[0050] In the embodiment of the present application, the test verification software may be, for example, ECU-Test, and the test verification software includes multiple test cases, each of which may include multiple tasks (Jobs), and a task may be understood as a unit in the test verification software that performs a specific test task, and a task may be, for example, starting monitoring or starting recording. If the task is completed, it may indicate that the corresponding function has been achieved. The test case is a test case adapted to other calibration software such as INCA.
[0051] When calibrating the device under test through the target calibration software, the test verification software can be connected to the target calibration software, that is, the test verification software and the target calibration software communicate through the target standard protocol. The target standard protocol can be, for example, the XIL standard protocol. XIL is a communication protocol used for vehicle testing and calibration.
[0052] Specifically, a large number of interfaces can be developed on the target calibration software, that is, the target calibration software has multiple interfaces. Each interface corresponds to the implementation method of each function in the target calibration software, that is, there is an implementation method corresponding to certain functions in the target calibration software, that is, the target calibration software comes with some implementation methods of functions, for example, the target calibration software can also implement "start monitoring". Each interface can correspond to a function, that is, an implementation method corresponding to a function, for example, interface A corresponds to "start monitoring" and interface B corresponds to "start recording". It can be understood that the test verification software and the target calibration software can be installed on the same computer device.
[0053] Specifically, any one of the multiple test cases can be recorded as a target test case, and the task included in the target test case can be recorded as a target task, that is, the multiple test cases include the target test case, and the target test case includes multiple target tasks. A target task in the target test case can be obtained through the test verification software, and the target task is used to achieve the target function, for example, the target task is to start monitoring, thereby achieving the monitoring function.
[0054] S102, determining whether the target task complies with the target standard protocol.
[0055] Specifically, since the target calibration software and the test verification software use the target standard protocol for communication, the tasks sent by the test verification software to the target calibration software also need to comply with the target standard protocol. Therefore, the test verification software can determine whether the target task complies with the target standard protocol in order to determine whether the target task can be executed in the target calibration software.
[0056] In a possible implementation, determining whether the target task complies with the target standard protocol may specifically include obtaining a task set that complies with the target standard protocol and determining whether the target task is in the task set.
[0057] Specifically, the task set includes a large number of tasks that conform to the target standard protocol. When judging whether the target task conforms to the target standard protocol, the target task can be compared with the tasks in the task set, that is, whether the target task is in the task set. If the target task is in the task set, it means that the target task conforms to the target standard protocol, otherwise, it means that the target task does not conform to the target standard protocol. In this way, by establishing a task set, tasks that conform to the target standard protocol can be grouped together, so that it can be more convenient and quick to determine whether a task conforms to the target standard protocol, thereby improving the test efficiency.
[0058] S103: If not, then based on the updated test file of the target test case, call the target script file.
[0059] Specifically, if the target task does not comply with the target standard protocol, it means that the target calibration software cannot perform the target task, and other methods need to be used to implement the target functions that can be achieved by the target task.
[0060] Specifically, an updated test file corresponding to the target test case can be obtained, and the updated test file is used to represent the test process of the updated target test case. The updated test file can include instruction information for calling the target script file, that is, the specific code for calling the target script file. Among them, the target script file is used to call the target interface of the target calibration software, and the target script file can be, for example, a Python script.
[0061] S104, during the execution of the target script file, calling the target interface of the target calibration software and executing the implementation method of the target function to realize the target function.
[0062] Specifically, the test verification software can call and execute the target script file through the computing module. During the execution process, the target script file will call the target interface and execute the implementation method of the relevant target function corresponding to the target interface, thereby completing the target function. In this way, when the target calibration software cannot execute the target task, the interface and built-in implementation method in the target calibration software can be used to implement the function corresponding to the target task, that is, the execution of the target task can be replaced to achieve the same function as the target task, so that the target test case can be reused.
[0063] refer to Figure 2 As shown, the test verification software can obtain the target task (that is, the task to be executed), and then determine whether the target task complies with the target standard protocol. If so, the target task can be executed in the target calibration software. Otherwise, the target script file can be called based on the updated test file, the target interface can be loaded, and the implementation method of the target function can be executed to achieve the target function.
[0064] In summary, in this application, by developing a large number of interfaces on the target calibration software, when the target task representing the target function cannot be executed, the test verification software can call the target interface, and through the target interface, the target function implementation method of the target calibration software can be used to achieve the target function. In this way, for tasks that cannot be executed in the test case, the implementation method of the target calibration software is used instead to complete them, so that the test case can be reused, and there is no need to redevelop test cases that match the target calibration software, which can shorten the development cycle, reduce costs, and can reuse a large number of test cases, thereby improving test efficiency. For example, the existing mature test cases of INCA can be converted into test cases available for WICAS, without the need to rewrite the test cases for WICAS, saving time and manpower, and achieving the purpose of case sharing.
[0065] In a possible implementation, calling the target interface of the target calibration software may specifically include obtaining a first identifier of a target task that does not conform to the target standard protocol; and calling the target interface of the target calibration software when a second identifier of the target interface is consistent with the first identifier.
[0066] Specifically, when the target script file calls the target interface, it needs to determine which interface is the target interface from multiple interfaces, that is, which interface can implement the target function. The determination can be made based on the identifier of the target task and the identifier of the interface.
[0067] Each task has its own identifier, which is used to uniquely identify a task. The identifier can be, for example, a task name, and the identifier of the target task can be recorded as the first identifier. Each interface can also have its own identifier, and the identifier of the target interface can be recorded as the second identifier. In other words, tasks and implementation methods that implement the same function can be marked with the same identifier.
[0068] Compare the first identifier of the target task with the identifiers of each interface. If the first identifier is consistent with the second identifier of the target interface, it means that the interface corresponding to the second identifier is the target interface that can achieve the same function. Therefore, the target interface can be determined from multiple interfaces based on the identifier, thereby improving the accuracy of the target interface, and determining the correct implementation method in the target calibration software to achieve the target function.
[0069] In a possible implementation, if the target task complies with the target standard protocol, the target task is executed by the test verification software to achieve the target function. In other words, if a target task in the target test case complies with the target standard protocol, the target calibration file can directly execute the target task.
[0070] In short, for the target tasks in the target test cases that conform to the target standard protocol, they can be executed in the target calibration software. For the target tasks that do not conform to the target standard protocol, the target interface and target function implementation method of the target calibration software can be called to replace the execution of the target task and realize the target function. This enables the reuse of the target test cases to a greater extent, without the need to develop test cases adapted to the target calibration software, thereby improving testing efficiency.
[0071] In a possible implementation, before S101 of acquiring the target task in the target test case through the test verification software, S201 to S203 may also be included.
[0072] S201, obtaining the test file of the target test case through a use case conversion tool.
[0073] Specifically, a case conversion tool can be developed. When the target task in the target test case cannot be executed in the target calibration software, the target task can be processed by the tool, and the test file of the target test case can be obtained by the tool. The test file is a file for executing the target task in the target test case, and the test file has all the target tasks included in the target test case.
[0074] S202, for each target task recorded in the test file, determine whether the target task complies with the target standard protocol.
[0075] Specifically, for each target task in the test file, it can be determined whether the target task complies with the target standard protocol. In actual applications, the target tasks in the Mapping structure in the test file can be cyclically retrieved, and for each target task, it can be determined whether it complies with the target standard protocol.
[0076] S203, if not, the target task in the test file is deleted, and the instruction information for calling the target task in the test file is modified to the instruction information for calling the target script file, so as to obtain an updated test file.
[0077] Specifically, if the target task does not conform to the target standard protocol, the target task can be deleted from the test file because it cannot be executed later. At this time, it is necessary to call the target script file to call the target interface to implement the target function corresponding to the target task. In this case, the instruction information for calling the target task in the test file can be modified to the instruction information for calling the target script file to obtain an updated test file. In this way, the instruction information for calling the target script file can be included in the updated test file.
[0078] In actual applications, the test file can be a file in XML format. Figure 3 As shown, the target task information (ie, Mapping-ITEM) in the Mapping structure in the test file can be deleted, and the instruction information for calling the target task in the Teststep structure can be modified to the instruction information for calling the target script file.
[0079] In this way, before the target calibration software implements the target function corresponding to the target task, the test file can be updated in advance based on whether the target task complies with the target standard protocol, so that when the target function is implemented, the target script file can be called based on the updated test file, thereby improving the execution accuracy and efficiency.
[0080] Based on the above test case reuse method, the present application embodiment also provides a test case reuse device, referring to Figure 4As shown, it is a structural block diagram of a test case multiplexing device provided by an embodiment of the present application, the test verification software includes multiple test cases, the test cases include multiple tasks, the test verification software communicates with the target calibration software through the target standard protocol, the target calibration software has multiple interfaces, each of the interfaces corresponds to the implementation method of each function in the target calibration software, and the device includes:
[0081] A first acquisition unit 201 is used to acquire a target task in a target test case through the test verification software; the target task is used to achieve a target function;
[0082] A first judging unit 202, used to judge whether the target task complies with the target standard protocol;
[0083] A first calling unit 203 is used to call a target script file based on an updated test file of the target test case if no; the updated test file includes instruction information for calling the target script file;
[0084] The first execution unit 204 is used to call the target interface of the target calibration software and execute the implementation method of the target function to realize the target function during the execution of the target script file.
[0085] Optionally, the device further comprises:
[0086] A second acquisition unit, used to acquire the test file of the target test case through a use case conversion tool;
[0087] A second judging unit, configured to judge, for each target task recorded in the test file, whether the target task complies with the target standard protocol;
[0088] The second calling unit is used to delete the target task in the test file if no, and modify the instruction information in the test file for calling the target task to the instruction information for calling the target script file to obtain the updated test file.
[0089] Optionally, the device further comprises:
[0090] The second execution unit is used to execute the target task through the test verification software to achieve the target function if the target task complies with the target standard protocol.
[0091] Optionally, the first determining unit is configured to:
[0092] Acquire a task set that meets the target standard protocol;
[0093] It is determined whether the target task is in the task set.
[0094] Optionally, the first execution unit is used for:
[0095] Obtaining a first identifier of a target task that does not conform to the target standard protocol;
[0096] When the second identifier of the target interface is consistent with the first identifier, the target interface of the target calibration software is called.
[0097] In summary, in this application, by developing a large number of interfaces on the target calibration software, when the target task representing the target function cannot be executed, the test verification software can call the target interface, and through the target interface, the target function implementation method provided by the target calibration software can be used to implement the target function. In this way, for tasks that cannot be executed in the test case, the implementation method provided by the target calibration software can be used to complete them instead, so that the test case can be reused without redeveloping the test case that matches the target calibration software, which can shorten the development cycle, reduce costs, and can reuse a large number of test cases, thereby improving test efficiency.
[0098] In another aspect, the present application provides a computer device, referring to Figure 5 , which is a structural diagram of a computer device provided in an embodiment of the present application, wherein the computer device includes a processor 310 and a memory 320:
[0099] The memory 320 is used to store program codes and transmit the program codes to the processor 310;
[0100] The processor 310 is used to execute the method provided in the above embodiment according to the instructions in the program code.
[0101] The computer device may include a terminal device or a server, and the aforementioned apparatus may be configured in the computer device.
[0102] On the other hand, an embodiment of the present application further provides a storage medium, wherein the storage medium is used to store a computer program, and the computer program is used to execute the method provided by the above embodiment.
[0103] A person skilled in the art can understand that all or part of the steps of implementing the above method embodiment can be completed by program instruction hardware, and the above program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above method embodiment; and the above storage medium can be at least one of the following media: read-only memory (English: Read-only Memory, abbreviated: ROM), RAM, magnetic disk or optical disk, etc. Various media that can store program codes.
[0104] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.
[0105] The above is only a preferred implementation of the present application. Although the present application has been disclosed as a preferred embodiment, it is not intended to limit the present application. Any technician familiar with the art can use the above disclosed methods and technical contents to make many possible changes and modifications to the technical solution of the present application without departing from the scope of the technical solution of the present application, or modify it into an equivalent embodiment of equivalent changes. Therefore, any simple modification, equivalent change and modification made to the above embodiments based on the technical essence of the present application without departing from the content of the technical solution of the present application still falls within the scope of protection of the technical solution of the present application.
Claims
1. A test case reuse method, It is characterized in that The test verification software includes a plurality of test cases, each of which includes a plurality of tasks. The test verification software communicates with the target calibration software through a target standard protocol. The target calibration software has a plurality of interfaces, each of which corresponds to an implementation method of each function in the target calibration software. The method includes: Obtaining a target task in a target test case through the test verification software; the target task is used to achieve a target function; Determining whether the target task complies with the target standard protocol; If not, calling the target script file based on the updated test file of the target test case; the updated test file includes instruction information for calling the target script file; During the execution of the target script file, the target interface of the target calibration software is called, and the implementation method of the target function is executed to realize the target function.
2. The method according to claim 1, It is characterized in that Before obtaining the target task in the target test case through the test verification software, the method further includes: Obtain the test file of the target test case through a use case conversion tool; For each target task recorded in the test file, determining whether the target task complies with the target standard protocol; If not, the target task in the test file is deleted, and the instruction information in the test file for calling the target task is modified to instruction information for calling the target script file to obtain the updated test file.
3. The method according to claim 1 or 2, It is characterized in that The method further comprises: If the target task complies with the target standard protocol, the target task is executed through the test verification software to achieve the target function.
4. The method according to claim 1, It is characterized in that Determining whether the target task complies with the target standard protocol includes: Acquire a task set that meets the target standard protocol; Determine whether the target task is in the task set.
5. The method according to claim 1, It is characterized in that Calling the target interface of the target calibration software includes: Obtaining a first identifier of a target task that does not conform to the target standard protocol; When the second identifier of the target interface is consistent with the first identifier, the target interface of the target calibration software is called.
6. A test case reuse device, It is characterized in that The test verification software includes a plurality of test cases, each of which includes a plurality of tasks. The test verification software communicates with the target calibration software through a target standard protocol. The target calibration software has a plurality of interfaces, each of which corresponds to an implementation method of each function in the target calibration software. The device includes: A first acquisition unit is used to acquire a target task in a target test case through the test verification software; the target task is used to achieve a target function; A first judging unit, used to judge whether the target task complies with the target standard protocol; A first calling unit, configured to call a target script file based on an updated test file of the target test case if no; the updated test file includes instruction information for calling the target script file; The first execution unit is used to call the target interface of the target calibration software and execute the implementation method of the target function during the execution of the target script file to realize the target function.
7. The device according to claim 6, It is characterized in that The device also includes: A second acquisition unit, used to acquire the test file of the target test case through a use case conversion tool; A second judging unit, configured to judge, for each target task recorded in the test file, whether the target task complies with the target standard protocol; The second calling unit is used to delete the target task in the test file if no, and modify the instruction information in the test file for calling the target task to the instruction information for calling the target script file to obtain the updated test file.
8. The device according to claim 7 or 6, It is characterized in that The device also includes: The second execution unit is used to execute the target task through the test verification software to achieve the target function if the target task complies with the target standard protocol.
9. A computer device, It is characterized in that The computer device comprises a processor and a memory: The memory is used to store program code and transmit the program code to the processor; The processor is configured to execute the method according to any one of claims 1 to 5 according to the instructions in the program code.
10. A computer-readable storage medium, It is characterized in that The computer-readable storage medium is used to store a computer program, and the computer program is used to execute the method according to any one of claims 1 to 5.