WO2023197128A1

WO2023197128A1 - Test method and control apparatus

Info

Publication number: WO2023197128A1
Application number: PCT/CN2022/086219
Authority: WO
Inventors: 陈升辉; 周慧强
Original assignee: 华为技术有限公司
Priority date: 2022-04-12
Filing date: 2022-04-12
Publication date: 2023-10-19
Also published as: CN117222983A

Abstract

The present application relates to the technical field of test, and provides a test method and a control apparatus. The method may comprise: obtaining function callback information of a functional module, the function callback information comprising a calling address of at least one external interface function of the functional module, a test for the functional module depending on another functional module calling the at least one external interface function, and the at least one external interface function being used for testing the functional module; receiving a test command line, the test command line comprising function calling address information, and the function calling address information being used for indicating the calling address of the at least one external interface function for testing the functional module; and in response to the test command line, calling at least part of the at least one external interface function to test the functional module. The technical solution of the present can be applied to an intelligent vehicle or an electric vehicle, and is beneficial to improving the testability of the control apparatus applied to the intelligent vehicle or the electric vehicle.

Description

A test method and control device

Technical field

The present application relates to the field of testing technology, and more specifically, to a testing method and a control device.

Background technique

As vehicles become more and more intelligent, microcontroller unit (MCU) is a commonly used chip for intelligent vehicle equipment. Since MCU has high functional safety attributes, MCU needs to support secondary development capabilities of source code on it. . However, the main debugging method of MCU is to directly burn the source code through the debugger, and observe changes in its external output such as controller area network (CAN), logs, voltage, etc. by running points, operating memory, or writing temporary code test stubs. , to determine whether the test results are in line with expectations.

When testing an MCU function module, other functional modules usually need to call the module's external interface function before the module can perform the corresponding function. In this case, if other functional modules have not been developed, this functional module cannot be tested. At this time, the tester needs to write the corresponding temporary code and burn it into the MCU to ensure that the external interface function of the module can be called. However, if you need to modify the input parameters of the external interface function during the test, you need to modify the temporary code and re-burn the temporary code into the MCU. In addition, after the development of other functional modules is completed, testers can only jointly debug all functional modules, making it difficult to conduct end-to-end testing of functional modules in the control device that rely on calls from other functional modules. The vehicle-mounted unit MCU is usually developed in parallel with multiple interrelated functional modules. Therefore, in the scenario of vehicle-mounted unit MCU testing, the above problems will be more obvious.

It can be seen that the functional modules in the on-board unit MCU have poor measurability and poor flexibility, which has become an urgent problem to be solved in the development of intelligent driving technology.

Contents of the invention

This application provides a testing method and control device. Testers can directly call the external interface function of the functional module without writing corresponding test stubs, and solve the problem that the external interface function of the functional module cannot complete the functional test due to the lack of a caller. This problem solves the problem of difficulty in conducting end-to-end testing of functional modules in the control device that rely on calls from other functional modules; at the same time, it helps improve the testability of the control device.

In a first aspect, a testing method is provided. The method includes: obtaining function callback information of a functional module. The function callback information includes a calling address of at least one external interface function of the functional module. The testing of the functional module relies on calls from other functional modules. At least one external interface function, wherein at least one external interface function is used to test the functional module; obtain a test command line, the test command line includes function call address information, the function call address information is used to indicate at least testing of the above functional module The calling address of an external interface function; in response to the above test command line, call at least part of at least one external interface function to test the above functional module.

For example, the functional module may be a module integrated in a control device, and the control device may be an MCU.

The technical solutions in the embodiments of this application can test MCUs in vehicles. In this application, transportation may include one or more different types of transportation vehicles that operate or move on land (e.g., highways, roads, railways, etc.), water (e.g., waterways, rivers, oceans, etc.) or in space Or movable objects. For example, vehicles may include cars, bicycles, motorcycles, trains, subways, airplanes, ships, aircraft, robots, or other types of transportation vehicles or movable objects.

For example, the above function callback information may be actively issued during the initialization process of the function module, or may be passively issued by the function module through a request operation after the function module is initialized. In addition, the above function callback information can also include additional information, such as the number of input parameters of the external interface function, the data type of the input parameters, the value range information of the input parameters, and the default parameters, etc., for auxiliary function modules A call to at least one external interface function.

It should be understood that when testing the specified function of the functional module, at least one external interface function specified in the functional module needs to be called in order for the functional module to perform the corresponding function. Therefore, in response to the above test command line, by calling at least part of the at least one external interface function, the above functional module can be tested.

For example, the above test command line also includes parameter values that specify the external interface function. For example, the external interface function needs to input corresponding parameters so that the function module can complete the execution of the corresponding function.

Based on the above technical solution, testers can directly call the external interface function of the functional module without writing corresponding test stubs, solving the problem that the external interface function of the functional module cannot complete the functional test due to the lack of a caller, thus solving the problem. It is difficult to conduct end-to-end testing of functional modules in the control device that rely on calls from other functional modules; at the same time, it helps to improve the testability of the control device.

Combined with the first aspect, in some implementations of the first aspect, it is confirmed that the proxy function is enabled, wherein when the proxy function is enabled, at least one external interface function is called according to the test command line.

For example, when the development of each functional module in the control device is completed, the execution of the specified function of functional module A depends on the external interface function of functional module B calling functional module A. At this time, the function of functional module A needs to be tested. When the agent function is turned off, function module B needs to be enabled to perform the corresponding function first to drive function module A to perform the corresponding function before the test of function module A can be completed. This process can be called joint debugging. When the proxy function is turned on, there is no need to start the corresponding function of function module B, and a separate end-to-end test can be directly performed on function module A.

Based on the above technical solution, it is possible to switch between joint debugging of functional modules and end-to-end testing of a certain functional module individually, making the method of testing the control device more flexible.

In connection with the first aspect, in some implementations of the first aspect, the function calling address information includes the calling address of the first external interface function; the calling address of the first external interface function matches the calling address of at least one external interface function successfully. Finally, calling at least part of at least one external interface function to test the function module.

For example, the first external interface function may be one or more external interface functions that need to be called to test the above functional module, that is, the first external interface function may be an external interface function or a set of external interface functions, where Includes multiple external interface functions.

For example, when the matching fails, the test command line can be discarded, or stored in a specified location, and then cleared periodically. In addition, when the matching fails, the matching failure information can also be returned and the matching failure information can be sent to the external access device.

For example, the above-mentioned external access device can be a controller area network open environment (controller area network open environment, CANoe), system on chip (system on chip, SOC), etc.

For example, when the test command line includes parameter values, after the calling address of the first external interface function successfully matches the calling address of at least one external interface function, the parameter value also needs to be input into the at least one external interface function.

Based on the above technical solution, it is possible to implement independent end-to-end testing of functional modules, making functional modules with interdependent functions functionally independent of each other; at the same time, it helps to improve the testability of the control device.

In conjunction with the first aspect, in some implementations of the first aspect, the function call address information includes an identification of the functional module; according to the identification of the functional module, at least one external interface function of the functional module is called to perform the function on the functional module. test.

For example, when the function call address information includes the identifier of the specified functional module, after receiving the test command, all or part of the external interface functions in at least one external interface function of the functional module can be called directly according to the identifier of the functional module.

Based on the above technical solution, the call to at least one external interface function of the functional module is not limited to the call based on the calling address of the first external interface function included in the function calling address information. It can also call at least one external interface function of the functional module through the identification of the functional module. An external interface function is called, thereby improving the flexibility of testing the control device; helping to improve the testability of the control device.

Combined with the first aspect, in some implementations of the first aspect, the function callback information also includes value range information of the input parameters of the first external interface function, and the test command line includes the parameter values of the first external interface function. When calling Before at least part of at least one external interface function tests the functional module, it is also necessary to determine that the above parameter value matches the above value range information.

For example, the value range information may be a parameter value interval. When the above-mentioned parameter value is within the parameter value interval, it means that the above-mentioned parameter value and the above-mentioned value range information are successfully matched, and the above-mentioned at least one external Interface functions are called. When the above-mentioned parameter value is outside the parameter value range, it means that the above-mentioned parameter value fails to match the above-mentioned value range information, and the above-mentioned at least one external interface function cannot be called.

Based on the above technical solution, the accuracy of calling at least one external interface function of the functional module can be improved, and functional module test abnormalities caused by incorrect calling of external interface functions can be reduced.

Combined with the first aspect, in some implementations of the first aspect, a test command line sent by the external access device is obtained.

For example, the above test command line can also be obtained from inside the control device. For example, the control device locally stores the test code, and the code includes the test command line. Therefore, the locally stored test command line can also be obtained to enable the response. In the test command line, call at least part of at least one external interface function to test the function module.

Based on the above technical solution, the test command line can be obtained through multiple channels, making the method of testing the control device more flexible.

Combined with the first aspect, in some implementations of the first aspect, the test results of the functional modules are sent to the external access device.

For example, the test results of the external interface function of the above functional module can be a series of parameter values, or a string presented by printing, for example, the name of the target external interface function, the parameter name and its value output by the function.

In a second aspect, a control device is provided. The control device includes: a first acquisition unit for acquiring function callback information of a functional module. The function callback information includes the calling address of at least one external interface function of the functional module. The test of the module relies on other functional modules to call at least one external interface function, where at least one external interface function is used to test the functional module; the second acquisition unit is used to obtain a test command line, which includes function call address information , the function call address information is used to indicate the calling address of at least one external interface function for testing the above-mentioned functional module; the test unit is used to respond to the above-mentioned test command line, call at least part of the at least one external interface function to perform the above-mentioned functional module test.

For example, the above function callback information may also include additional information, such as the number of input parameters of the external interface function, the data type of the input parameters, the value range information of the input parameters, and the default parameters, etc., for auxiliary functions. A call to at least one external interface function of the module.

Combined with the second aspect, in some implementations of the second aspect, the above test unit is also used to confirm that the proxy function is enabled, wherein when the proxy function is enabled, at least one external interface function is called according to the test command line.

For example, when the development of each functional module in the control device is completed, the execution of the specified function of functional module A depends on the external interface function of functional module B calling functional module A. At this time, the function of functional module A needs to be tested. When the agent function is turned off, function module B needs to be enabled to perform the corresponding function first to drive function module A to perform the corresponding function before the test of function module A can be completed. This process can be called joint debugging. When the proxy function is turned on, there is no need to start the corresponding function of functional module B. The above test unit can directly conduct a separate end-to-end test on functional module A.

Combined with the second aspect, in some implementations of the second aspect, the function calling address information includes the calling address of the first external interface function; the calling address of the first external interface function matches the calling address of at least one external interface function successfully. Finally, the above-mentioned test unit is specifically used to call the first external interface function to test the functional module.

For example, the first external interface function may be an external interface function that needs to be called to test the above functional module. The first external interface function may be an external interface function or a function set including multiple external interface functions.

For example, when the match fails, the test unit can discard the test command line, or store it in a specified location, and then clear it regularly. In addition, when matching fails, the test unit can also return matching failure information and send the matching failure information to the external access device.

For example, when the test command line includes parameter values, after the calling address of the first external interface function and the calling address of at least one external interface function are successfully matched, the above-mentioned test unit also needs to input the parameter value to the at least one external interface. in function.

Combined with the second aspect, in some implementations of the second aspect, the function call address information includes the identification of the functional module; the above-mentioned test unit is specifically used to call the above-mentioned at least one external interface function to perform the function module according to the identification of the functional module. test.

For example, when the function call address information includes the identifier of the specified functional module, after obtaining the test command, the above-mentioned test unit can directly call all or part of the external interfaces in at least one external interface function of the functional module based on the functional module identifier. function.

Combined with the second aspect, in some implementations of the second aspect, the function callback information also includes value range information of the input parameters of the first external interface function, and the test command line includes the parameter values of the first external interface function. The above test The unit is specifically configured to determine that the parameter value matches the value range information before calling at least part of the at least one external interface function to test the functional module.

For example, the value range information may be a parameter value interval. When the above-mentioned parameter value is within the parameter value interval, it means that the above-mentioned parameter value and the above-mentioned value range information are successfully matched, and the above-mentioned test unit can perform the above-mentioned At least one external interface function is called. When the above-mentioned parameter value is outside the parameter value range, it means that the above-mentioned parameter value fails to match the above-mentioned value range information, and the above-mentioned test unit cannot call the above-mentioned at least one external interface function.

In conjunction with the second aspect, in some implementations of the second aspect, the above-mentioned second obtaining unit is specifically configured to obtain the test command line sent by the external access device.

For example, the above-mentioned test command line can also be directly obtained internally from the control device by the second acquisition unit. For example, the control device locally stores the test code, and the code includes the test command line. Therefore, the second acquisition unit can also obtain the locally stored test code. The test command line enables the above test unit to respond to the test command line and call at least part of at least one external interface function to test the functional module.

With reference to the second aspect, in some implementations of the second aspect, the above-mentioned control device further includes a sending unit configured to send test results of the functional module to an external access device.

In a third aspect, a control device is provided, including a memory for storing computer instructions; and a processor for executing the computer instructions stored in the memory, so that the device executes any one of the method designs of the first aspect. Methods in possible implementations.

A fourth aspect provides a micro control unit, including the control device of the second aspect.

In a fifth aspect, a computer storage medium is provided. Computer instructions are stored in the computer storage medium. When the instructions are executed on a computer, they cause the computer to execute the method in any possible implementation of the method design of the first aspect. .

In a sixth aspect, a chip is provided, including a processor configured to execute the method in any possible implementation of the method design of the first aspect.

By way of example, the chip may be a baseband chip.

A seventh aspect provides a computer program product. When the computer program code or instructions are executed on a computer, the computer executes the method in any possible implementation of the method design of the first aspect.

Description of the drawings

Figure 1 is a schematic diagram of an existing MCU function module testing logic provided by an embodiment of the present application.

Figure 2 is a schematic diagram of the architecture of a control device provided by an embodiment of the present application.

FIG. 3 is a schematic diagram of another control device architecture provided by an embodiment of the present application.

Figure 4 is a schematic diagram of another control device architecture provided by an embodiment of the present application.

Figure 5 is a schematic flow chart of a testing method provided by an embodiment of the present application.

Figure 6 is a schematic flowchart of the proxy module calling the external interface function of the function module provided by the embodiment of the present application.

Figure 7 is a schematic diagram of the later maintenance of the agent module provided by the embodiment of the present application.

FIG. 8 is a schematic block diagram of a control device 800 provided by an embodiment of the present application.

Detailed ways

In order to facilitate understanding of the embodiments of the present application, the terms and concepts involved in the embodiments of the present application are first explained.

A microcontroller unit, also known as a single-chip microcomputer or single-chip microcomputer, appropriately reduces the frequency and specifications of the central processing unit (CPU), and combines memory, counters, and universal serial bus (USB) Peripheral interfaces such as analog-to-digital converters, universal asynchronous receivers and transmitters, programmable logic controllers, and direct memory access controllers are all integrated on a single chip to form a chip-level computer that can perform different combinations of controls for different applications. The characteristic of MCU is that it generally does not support complex systems running multiple tasks. When testing a specific functional module among the multiple interrelated functional modules of a traditional MCU, it is usually necessary to call the external interface functions of other functional modules, or its own external interface functions are called by other functional modules, in order to realize the function of the functional module. test.

Secondary development refers to customizing and modifying existing software, extending functions, and realizing the functions required by developers. This process usually does not change the core of the original system. It should be understood that the executor of secondary development can be one party or multiple parties. Taking the above-mentioned MCU functional module development as an example, an MCU including basic functions can be provided to one customer for secondary development and expansion of MCU functions, or it can be provided to multiple customers for secondary development and expansion on top of it. MCU functions, and the functional modules secondary developed by multiple customers are usually related to each other. It can be seen that in this case, the problem of the above-mentioned MCU being unable to implement end-to-end testing of this functional module due to the fact that the interrelated business modules have not yet been developed will be particularly obvious.

Hard coding refers to a method of replacing a variable variable with a fixed value. In hard coding, if you want to modify a certain function, you must modify the source code, which lacks flexibility. Therefore, after compiling with hard coding, it is very difficult to change the fixed variable value later. The existing method of testing MCU is that the tester writes the test code through hard coding according to the requirements of the test document and burns it into the MCU to run, so that the MCU function module receives the test command included in the test code when the code is running. Call all external interface functions that need to be called by the test function module. Since the test command needs to be implemented in a hard-coded manner, the input parameters of the external interface function in the test command are all fixed values. If the above-mentioned external interface function input parameters need to be changed, the tester needs to rewrite the test code and change the above-mentioned interface function input parameters. , and then burn the modified test code into the MCU for secondary testing.

A stub function refers to a function that replaces the function of the original function, so that the functional module under test can be isolated from the functional modules it depends on during the testing process. For example, in the existing MCU testing method, if this functional module has been developed, but in the process of testing this functional module, it is necessary to call the external interface function of other functional modules to obtain the output results of the external interface function, and other functions If the module has not developed its external interface function, the tester can write a test stub and add a simple implementation of the external interface function to the test stub. When this function module executes the function, the external interface function in the test stub is called to obtain the corresponding The output results are used to assist this functional module in completing the test.

In order to facilitate understanding of the embodiments of the present application, the prior art method of testing MCU functional modules is first described in detail with reference to FIG. 1 .

Function module A is a basic function module, function module B is an advanced function developed based on the functions of function module A, and function module C is an advanced function developed based on the functions of function module B.

In one embodiment, taking the test function module B as an example, since the function module B is the upper-level functional module of the function module C, when the function module B needs to perform a function, one or more external interfaces of the function module B The function needs to be called by function module C before function module B can perform the corresponding function. It can be seen that the execution of the corresponding functions of function module B relies on function module C calling one or more designated external interface functions of function module B.

Similarly, since functional module A is the upper-level functional module of functional module B, the execution of the corresponding functions of functional module A depends on functional module B calling one or more designated external interface functions of functional module A, so that the functional module A performs the corresponding function.

The prerequisite for calling the external interface function of the function module may be: the calling address of the external interface function and the corresponding external interface function input parameters are known.

It should be understood that the prerequisites to be considered when calling the external interface function of the function module may also include determining the following information: the number of input parameters of the external interface function, parameter type, parameter value range, etc. In addition, additional information such as parameter defaults may also be included, which is not limited in this application.

It should be understood that the tester should write the test code through hard coding according to the external interface function calling method for the corresponding function of the function module given in the product test manual, and burn the test code into the MCU. During the operation of the MCU, , call the external interface function of the specified function module, so that the function module can perform the corresponding function and realize the test of the function module.

The above is the existing method of testing MCU business functions. It can be seen that there is a serial function implementation between function module A, function module B and function module C. This is also a common function deployment method in MCU.

In one embodiment, for the above-mentioned existing method of testing MCU business functions, if the tester needs to test the corresponding function of function module B, the tester must start with function module C, so that function module C performs the corresponding function to drive Execution of the corresponding functions of function module B. And only in the process of function module B executing the function, the execution of the corresponding function of function module A will be driven. Therefore, during the above testing process, it is impossible to conduct end-to-end testing independently for functional modules in the MCU that rely on calls from other functional modules.

In addition, developers usually adopt a parallel development method for MCU function development. Taking the above embodiment as an example, function module A, function module B and function module C are usually handed over to different customers for development, and their development progress Usually cannot be unified.

It should be understood that since the functional modules in the MCU that are functionally dependent on each other are implemented in series, taking the above embodiment as an example, the MCU can only implement the functional module A, the functional module B, and the functional module C after they are all developed. Testing of Function Module A or Function Module B, that is, for the above scenario, at this stage, it is not possible to conduct independent end-to-end testing of Function Module A or Function Module B. If you need to test function module A, you need to first execute the corresponding function of function module B to call the external interface function of function module A so that function module A can perform the corresponding function. Furthermore, to execute the corresponding function of function module B, function module C also needs to call the external interface function of function module B. Otherwise, the test of function module A still cannot be implemented.

To sum up, existing MCUs have poor testability and testing flexibility. It is difficult to conduct end-to-end testing of functional modules that rely on calls from other functional modules in the MCU. At the same time, there is a lack of callers in the external interfaces of functional modules. The corresponding function is difficult to test. This problem will be more obvious when multiple customers develop parallel functional modules of the same MCU.

In view of this, embodiments of the present application provide a testing method that calls the external interface function of the functional module through the proxy module, making each functional module with functional dependencies independent of each other, and solving the problem that the external interface function of the functional module cannot be executed due to the lack of the caller. The corresponding function solves the problem of being unable to complete the test. At the same time, it enables independent end-to-end testing of functional modules in the MCU that rely on calls from other functional modules; it also helps to improve the testability of the MCU.

In addition, the channel module parses the test command input by the tester from the external access device, parses it into a test command line that can be recognized by the agent module, and distributes it to the above-mentioned agent module. The above-mentioned agent module performs functions on the functional module based on the test command line. test. Therefore, testers can repeatedly change the MCU external interface function calling sequence, frequency and input parameters by arranging test commands, thereby achieving path coverage testing of MCU functions, avoiding testers from repeatedly modifying the test code and repeatedly burning the test code. The process of recording to MCU.

Figure 2 shows a schematic diagram of the architecture of a control device provided by an embodiment of the present application. The control device includes function modules, agent modules, channel modules and external access equipment.

The control device architecture includes multiple functional modules, and each functional module has an agent module corresponding to it.

The function module is used to implement specific business functions of the control device, send function callback information to the agent module, and provide its own external interface functions for testing.

In one embodiment, the above function callback information includes the calling address of the external interface function, and may also include at least one of the following: the number of input parameters of the external interface function, the data type of the input parameters, and the value range of the input parameters. Information, used to assist in calling external interface functions.

In one embodiment, the functional module may be a functional module that has been developed, or a functional module whose specific functions have not yet been developed. Even if its specific functions have not yet been developed, it can still provide its own external interface functions. The tester can The transmission status of the data stream after calling the external interface function can also complete the preliminary test of the corresponding function.

The proxy module is used to obtain the function callback information of the function module, and in response to the test command line, call at least some of the external interface functions of at least one external interface function to test the function module.

In one embodiment, the test command line includes function calling address information, and the function calling information may include the calling address of the first external interface function. It should be understood that the first external interface function may be one or more external interface functions that need to be called in the functional module. The agent module can call one or more external interface functions of the functional module according to the calling address of the first external interface function to complete the test of the functional module. It should be understood that when specifying that an external interface function needs to pass in parameters, the test command line also needs to include the corresponding parameter values, and the proxy module needs to input the parameter values into the external interface function.

In addition, the agent module can also be used to send the test results output from the function module corresponding to the called external interface function to the channel module, and send the test results to the external access device through the channel module. It should be understood that the agent module can also directly send the above test results to the external access device, depending on the specific control device architecture. For example, if the control device does not have a channel module, the agent module can directly communicate with the external access device. This application The embodiment does not limit this.

In one embodiment, the agent module can only call one external interface function in the functional module according to the above test command line, or it can call multiple external interface functions in the functional module. That is, the above test command line can be used to call one external interface function. , can also be used to call multiple external interface functions, which is not limited in this application.

The channel module is a module that establishes communication with external access devices and is used to receive test commands input by testers through external access devices. The external interface functions and parameter values included in the test commands can be changed based on the tester's wishes. , thus avoiding the process of repeatedly burning test code.

In addition, the channel module can also be used to parse the test command into a test command line that can be recognized by the agent module, and distribute the test command line to each agent module.

It should be understood that the test command can be input to the channel module in the form of a string, but the data it carries, such as the parameter value of the external interface function input parameter, actually has a specific data type, such as integer, floating Point type, Boolean type, etc. Therefore, the channel module can parse the test command in the form of a string into a set of test command lines including the external interface function address and specific data type parameters. This test command line can be recognized by the agent module and is used by the agent module to call the external interface of the function module. function.

It should be understood that the function of the channel module can be a separately established module as shown in Figure 2, dedicated to real-time communication between the control device and external access equipment, and test command parsing. It may also be a sub-module integrated in the agent module, which is not limited in this application. For convenience of description, the embodiments of this application are described in the form of independent deployment of the agent module and the channel module.

The external access device is used to establish contact with the control device and is a device for testers to input test commands to the control device. The external access device can be CANoe, SOC, etc.

In one embodiment, the external access device can also directly send the above-mentioned test command line to the control device. In this scenario, the above-mentioned channel module does not need to parse the test command line. The test command line can be directly sent to the agent module for function Calling of the external interface function of the module.

In one embodiment, different from the above-mentioned control device architecture, one agent module can also correspond to multiple functional modules. For example, Figure 3 shows a schematic diagram of another control device architecture provided by an embodiment of the present application, or Figure 4 shows Another schematic diagram of the control device architecture provided by the embodiment of the present application, or multiple channel modules are added to the above-mentioned control device architecture. The embodiment of the present application does not limit the specific deployment method of each module. For convenience of description, the embodiment of the present application is mainly described based on the control device architecture in FIG. 2 .

In one embodiment, in a vehicle-mounted unit control device testing scenario, a bench used for vehicle testing can input test commands to the control device in the above embodiment through the above-mentioned external access device.

It should be understood that the above control device may be an MCU or other control device, which is not limited in this application.

It should be understood that in the above control device architecture, in order to avoid that any of the functional modules A, functional module B and functional module C has not yet been developed and affects the testing of each functional module, it is necessary to add an agent module to each functional module. correspond. When the specified external interface module of the functional module needs to be called, the proxy module can directly call the external interface function to prevent the corresponding external interface function of the functional module from being called by other functional modules, causing the problem that the functional module cannot be tested, and it is difficult to Aiming at the problem of end-to-end testing of function modules in control devices that rely on calls from other function modules.

It should be understood that the above-mentioned problem of difficulty in conducting end-to-end testing of functional modules that rely on calls from other functional modules in the control device includes but is not limited to the following two test scenarios:

1. This functional module has been developed, and the execution of the corresponding functions of this functional module requires other functional modules to call the designated external interface function of this functional module to complete the functional test. However, other functional modules have not yet been developed. Therefore, the designated external interface function of this functional module lacks a caller and the test cannot be completed.

2. This functional module has been developed, and the execution of the corresponding functions of this functional module requires other functional modules to call the designated external interface function of this functional module in order to complete the functional test. Other functional modules have been developed, and the test of this functional module Testing must be completed through joint debugging with other functional modules, and end-to-end testing cannot be performed on this functional module alone.

Figure 5 shows a schematic flow chart of a testing method provided by an embodiment of the present application.

In one embodiment, the execution subject of the test method is the above-mentioned control device, and specific functions can be implemented by the agent module and the channel module included in the control device.

S510. Obtain the function callback information of the functional module. The function callback information includes the calling address of at least one external interface function of the functional module. The test of the functional module relies on other functional modules to call at least one external interface function. The at least one external interface function Used to test this functional module.

It should be understood that the test of this functional module depends on other functional modules calling at least one external interface function of this functional module, so that the functional module can execute the corresponding function to complete the functional test.

In one embodiment, the proxy module obtains the function callback information of the functional module. During system initialization, the functional module actively sends the function callback information to the proxy module, so that the proxy module obtains the function callback information. Alternatively, the agent module can actively request to obtain the function callback information of the functional module during system operation, which is not limited in this application.

In one embodiment, the proxy module can correspond to one functional module or multiple functional modules, so the proxy module can receive multiple pieces of function callback information from one or more functional modules. The embodiments of the present application do not limit this.

In addition, the function callback information may also include additional information, such as the number of input parameters of the external interface function, the data type of the input parameters, the value range information of the input parameters, and the default parameters, etc. This application does not limit this. .

S520. Obtain a test command line. The test command line includes function calling address information, where the function calling address information is used to indicate the calling address of at least one external interface function of the test function module.

In one embodiment, the obtained test command line may be generated by the channel module parsing the test command sent from the external access device, may be obtained directly from the external access device, or may be obtained from inside the control device. For example, the channel module first obtains the test command from the external access device, and parses the test command into a set of test command lines including the external interface function address and specific data type parameters, and the test command line can be obtained and directly recognized by the agent module . For another example, the control device stores test code locally, and the code includes a test command line. Therefore, the agent module can also obtain the locally stored test command line. For another example, the external access device directly sends the test command line, so that the agent module can directly obtain the test command line from the external access device.

In one embodiment, the test command line includes function call address information, or function call address information and parameter values. Further, the function calling address information includes the calling address of the designated external interface function, or the identification of the designated function module.

Since the function calling address information includes the calling address of the first external interface function, and the first external interface function is one or more external interface functions that need to be called when testing the functional module, the function module can be called based on the calling address. When the external interface function needs to input parameters, the test command line must also include the corresponding parameter values. The proxy module needs to input the parameter values into the external interface function so that the functions corresponding to the external interface function can be executed. , and then complete the test of the functional module.

When the function call address information includes the identifier of the specified functional module, after obtaining the test command, the agent module can directly call all or part of the external interface functions of at least one external interface function of the functional module based on the functional module identifier, This enables the functions corresponding to the external interface functions to be executed, thereby completing the test of the functional module.

S530: In response to the above test command line, call at least part of the above at least one external interface function to test the function module.

In one embodiment, since the proxy module can be a code module in terms of technical implementation, the proxy module can also be a function, and also has a unique calling address, so the proxy module needs to issue its calling address before receiving the test command line. To the channel module, when the channel module parses the externally input test command into a test command line that can be recognized by the agent module, it can send the test command line to the agent module based on the address information.

In one embodiment, before the above S510, the agent module also needs to confirm whether the agent function is turned on. When the agent function is turned on, the agent module can receive the test command line from the channel module and call the external interface function specified by the function module, that is, to achieve Each functional module in the control device can be tested individually end-to-end.

When the agent function is turned off, the agent module cannot receive the test command line from the channel module and cannot call the external interface function specified by the function module. That is, at this time, only the joint debugging test of the function module in the control device can be performed.

In one embodiment, the information about turning on or off the agent function can also be sent to the channel module together with the calling address of the agent module before the agent module receives the test command line. When the information indicates that it is in the on state, the channel module distributes the information. When testing the command line, you need to send the test command line to the agent module; when the information is indicated as closed, the channel module does not need to send the test command line to the agent module when distributing the test command line.

It should be understood that testers can control the function of the designated agent module to be turned on or off according to test requirements.

In one embodiment, before the channel module sends the test command line to the agent module, the channel module receives the test command sent by the external access device and parses the test command. It should be understood that the process of parsing the test command is the process of converting the test command into a test command line that can be recognized by the agent module. For example, the test command input by the external access device is presented in the form of a string, and the string carried Data usually has special data types, such as integers, floating point, etc. Therefore, after the control device receives the test command, it needs to parse the test command and generate a test command line that can be recognized by the agent module, so that the agent module The specified external interface function of the function module can be called through the test command line. It should be understood that the external access device can also directly send the above test command line to the control device, which is not limited in the embodiments of the present application.

It should be understood that the above-mentioned agent module and channel module can be integrated into one module, or they can be two independent modules, which is not limited in this application.

It should also be understood that through the above testing method, testers can directly call the external interface function of the functional module without writing corresponding test stubs, solving the problem that the external interface function of the functional module cannot complete the functional test due to the lack of a caller. This solves the problem of difficulty in conducting independent end-to-end testing of functional modules in the control device that rely on calls from other functional modules; at the same time, it helps to improve the testability of the control device.

It should be understood that the channel module enables data communication between the control device and the external access device, that is, the test command can be directly sent to the control device through the external access device, without burning the test code to the control device, so that the control device can obtain Test command.

In one embodiment, the test commands are usually recorded in the test instructions, and the tester sends test commands that meet the requirements of the test case to the channel module through the external access device according to the test case. Test commands can be of the following form:

External interface function A calling address = 0x01; parameter a = (int, 50);

External interface function B calling address = 0x11; parameter a = (int, 100); parameter b = (boolean, false);

External interface function C calling address = 0x21;

In one embodiment, the function module includes a function module that specifies the calling address and parameter value of the external interface function.

In one embodiment, the test command line generated after parsing by the channel module includes the calling address and parameter values of the first external interface function.

It should be understood that when an external interface function does not require input parameters, the above test command line for calling the external interface function may not include the parameter value, or the parameter value may be empty, for example, "null" or this attribute does not exist accordingly. The data.

It should also be understood that the test command line may also include other additional information, for example, whether the parameter value of the first external interface function in the test command line is consistent with the value range information of the first external interface function input parameter included in the function callback information. Therefore, the additional information can also be used by the proxy module to determine whether the test command line can call the external interface function of the specified function module, which is not limited in this application.

In one embodiment, the channel module can parse the test command sent from the external access device in the following manner:

Parse the relevant feature information about the external interface function in the test command, such as the calling address, parameter value and additional information of the external interface function. The additional information includes the number of input parameters of the above-mentioned external interface function and the data type of each parameter, etc. After parsing the generated information, the information is packaged to generate a test command line. The test command line can be of the following form:

External interface function A calling address = 0x01; additional information: number of parameters = 2, parameter type = [int, boolean];

Parameter value = [50, true];

External interface function B calling address = 0x11; additional information: number of parameters = 2, parameter type = [int, boolean];

Parameter value = [100, false];

External interface function C calling address = 0x21; additional information: number of parameters = 0, parameter type = [null];

Parameter value = [null];

In one embodiment, when there are multiple agent modules in the control device, that is, one channel module corresponds to multiple agent modules, the channel module needs to distribute the test command line generated by the above analysis to all corresponding agent modules.

In one embodiment, when there are multiple proxy modules in the control device, the above test command may also include the address information of the designated proxy module. After the channel module parses the test command, it can determine whether to receive the parsed and generated test command line. proxy module, thus avoiding the waste of resources caused by sending the parsed test command line to all proxy modules.

It should be understood that compared with existing testing methods, testers can arrange test commands to arrange the calling sequence, frequency and parameters of the external interface function of the function module, thereby achieving path coverage testing of the function module function and avoiding the need for testing. The personnel repeatedly modified the test code and repeatedly burned the test code into the control device.

After the channel module sends a test command line to the agent module, the agent module needs to determine whether it is necessary to call the specified external interface function of the function module based on various information included in the test command line.

Figure 6 shows a schematic flowchart of the proxy module calling the external interface function of the functional module provided by the embodiment of the present application.

S610: The agent module matches the test command line and the function callback information to determine whether the test command line can be used to call the specified external interface function. If the matching is successful, go to S620; if the matching fails, go to S630.

In one embodiment, the proxy module can generate an external interface function library based on the calling address of at least one external interface function included in the function callback information. The library stores the calling conditions of the at least one external interface function, and the calling conditions are at least It must have the calling address of the external interface function. In addition, there may also be additional information such as the number of function input parameters, parameter data types, input parameter value ranges, etc. The embodiments of this application do not limit the content of the additional information.

S620: The agent module calls the specified external interface function, and inputs the parameter values included in the test command line into the external interface function to complete the calling of the external interface function.

In one embodiment, when the function callback information includes the value range information of the first external interface function input parameter, and the test command line includes the parameter value, the agent module needs to determine whether the parameter value matches the value range information. When successful, each parameter value included in the test command line is input into the external interface function, the call of the external interface function is completed, the function module executes the corresponding function, and the test result is output.

It should be understood that when the external interface function does not require input parameters, the proxy module does not need to input parameter values into the external interface function, and the successfully matched test command line in S610 may not include parameter values.

S630: The agent module terminates this call to the external interface function of the function module.

In one embodiment, when the matching fails, the agent module can discard the test command line, or store it in a designated location, and then clear it regularly. This is not limited in the embodiments of this application. In addition, the agent module can also return matching failure information and send the matching failure information to the channel module, which transmits it to the external access device through the channel module to prompt the tester to self-check the test command.

S640: The agent module receives the test results from the function module and forwards the test results to the channel module.

In one embodiment, the above matching failure information or test results can be sent to the channel module, and then the channel module sends it to the external access device. When the proxy module also has the function of communicating with the external access device, for example, The function of the channel module is integrated in the proxy module, and can also be directly sent to the external access device through the proxy module. The embodiments of this application are not limited to this, but ultimately the above matching failure information or test results are sent to the external access device. equipment.

In one embodiment, the above test results can also be directly sent to the channel module through the functional module, which is not limited in this application.

In one embodiment, the test results of the external interface function of the above functional module can be a series of parameter values, or a string presented by printing, for example, the name of the target external interface function, the parameters output by the function and their values. There are no restrictions on this application.

It should be understood that testers can directly call the external interface functions of the functional module without writing corresponding test stubs, solving the problem of the external interface function of the functional module being unable to complete the functional module test due to the lack of a caller, thereby solving the difficulty of testing the functional module. Aiming at the problem of end-to-end testing of functional modules in the control device that rely on calls from other functional modules; at the same time, it helps to improve the testability of the control device.

Figure 7 shows a schematic diagram of the later maintenance of the agent module provided by the embodiment of the present application.

In one embodiment, the function of function module A in Figure 7 needs to be tested. The execution of this function requires function module B to call the external interface function of function module A. The same as the above description, since functional module B has not completed development, it is necessary to call the designated external interface function of functional module A according to the test command line through proxy module A, so that functional module A can perform the corresponding functions. However, when the development of functional module B is completed, since functional module B can call the designated external interface function of functional module A, and the control device only has these two functional modules, the development of these two functional modules has been completed. At this time, you can Turn off the proxy function of proxy module A, or delete proxy module A directly.

It should be understood that the control device architecture proposed in the embodiment of the present application is more flexible. According to the development status of each functional module in the control device, designated agent modules can be independently added, deleted, turned on or off.

It should be understood that when a certain functional module of the control device has been developed, the functional module needs to be tested. However, the execution of the corresponding function of the functional module requires other functional modules to call the designated external interface function of this functional module before it can be completed. Functional testing, while other functional modules have not yet been developed, and it is impossible to test this functional module through existing testing methods. However, according to the testing method provided by the embodiment of the present application, it can be known that the function module can be called through the above-mentioned proxy module, and there is no need to wait for the development of other functional modules to be completed before testing the functional module.

It should be understood that after all functional modules of the control device are developed, the existing testing method is to jointly debug the interdependent functional modules, and cannot individually target a certain functional module that relies on other functional modules in the function deployment of the control device. Conduct end-to-end testing individually.

In one embodiment, both functional module A and functional module B have been developed. The function of functional module A is to obtain rainfall, and the function of functional module B is to determine the wiper swing frequency. At this time, the function of function module A needs to be tested. The existing test method is to run the function of function module B to determine the wiper passive frequency. In this process, function module B calls the designated external interface function of function module A to make the function Module A turns on the function of obtaining rainfall, and then returns the rainfall value. However, according to the testing method provided in this application, it is only necessary to enable the proxy function of the proxy module corresponding to functional module A, and the proxy module can directly call the designated external interface function of functional module A to test functional module A separately without the need for Conduct joint debugging with function module B. The test process is simplified, and end-to-end testing can be carried out individually for the function modules that the control device depends on calling other function modules.

In one embodiment, for a test scenario where multiple interdependent functional modules are jointly debugged, each functional module usually needs to output the status of the code execution by printing a log during the process of executing the specified function code, so as to facilitate subsequent When a function module fails, locate the fault. When a module among multiple interdependent functional modules fails and the specific fault of the functional module needs to be located, all functional modules need to be jointly debugged. In this process, the number of print logs generated by each module is huge, and the test The workload of personnel fault location is relatively large. However, based on the testing method proposed in this application, testers can open the proxy module corresponding to the functional module, directly call the designated external interface function of the functional module through the proxy module, run the corresponding functional code, and generate a print log. It should be understood that the number of print logs generated by testing a single module is much smaller than the number of print logs generated during joint debugging. Therefore, the control device proposed in this application is more convenient for testers to conduct maintenance tests on each functional module individually in the later stage. .

Embodiments of the present application also provide a control device for implementing any of the above methods. For example, a control device including a unit (or means) for implementing any of the above methods is provided.

Figure 8 shows a schematic block diagram of a control device 800 provided by an embodiment of the present application. As shown in Figure 8, the control device 800 includes:

The first obtaining unit 810 is used to obtain the function callback information of the functional module. The function callback information includes the calling address of at least one external interface function of the functional module. The test of the functional module relies on other functional modules to call at least one external interface function. At least one external interface function is used to test the functional module.

The second acquisition unit 820 is configured to receive a test command line, where the test command line includes function call address information, where the function call address information is used to indicate the call address of at least one external interface function of the test function module;

It should be understood that the function of the first acquisition unit 810 can be implemented by the agent module in the above embodiment, and the function of the second acquisition unit 820 can be implemented by the channel module in the above embodiment.

The testing unit 830 is configured to respond to the test command line by calling at least part of at least one external interface function to test the functional module.

Optionally, the test unit 830 is specifically configured to confirm that the proxy function is enabled. When the proxy function is enabled, at least one external interface function is called according to the test command line.

Optionally, the test unit 830 is specifically configured to match the calling address of the first external interface function included in the function calling address information with the calling address of the at least one external interface function. After the matching is successful, call the first external interface function. Test functional modules.

Optionally, when the function callback information also includes the value range information of the input parameter of the first external interface function, and the test command line includes the parameter value of the first external interface function, the test unit 830 is also specifically configured to determine the parameter. The value matches the value range information.

It should be understood that the above functions of the test unit 830 can be implemented by the agent module in the above embodiment.

Optionally, the second obtaining unit 820 is also specifically configured to obtain the test command line sent by the external access device. It should be understood that the external access device can also directly send the test command line to the control device.

The sending unit 840 is used to send the test results of the functional module to the external access device.

It should be understood that the function of the sending unit 840 can be implemented by the channel module in the above embodiment.

The embodiment of the present application also provides an MCU, and further provides a vehicle-mounted unit MCU. The MCU includes the control device 800 mentioned above.

The terms "component", "module", "system", etc. used in this specification are used to refer to computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to, a process, a processor, an object, an executable file, a thread of execution, a program and/or a computer running on a processor. Through the illustrations, both applications running on the computing device and the computing device may be components. One or more components can reside in a process and/or thread of execution and a component can be localized on one computer and/or distributed between 2 or more computers. Additionally, these components can execute from various computer-readable media having various data structures stored thereon. A component may, for example, be based on a signal having one or more data packets (eg, data from two components interacting with another component, a local system, a distributed system, and/or a network, such as the Internet, which interacts with other systems via signals) Communicate through local and/or remote processes.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application. should be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A testing method, characterized by including:

Obtain the function callback information of the functional module. The function callback information includes the calling address of at least one external interface function of the functional module. The test of the functional module relies on other functional modules to call the at least one external interface function. The at least one An external interface function is used to test the functional module;

Obtain a test command line, where the test command line includes function call address information, where the function call address information is used to indicate the call address of the at least one external interface function for testing the functional module;

In response to the test command line, at least part of the at least one external interface function is called to test the functional module.
The method of claim 1, further comprising:

Confirm that the proxy function is enabled, wherein when the proxy function is enabled, the at least one external interface function is called according to the test command line.
The method according to claim 1 or 2, characterized in that the function calling address information includes the calling address of the first external interface function, and the at least one external interface function is called in response to the test command line. Test at least part of the functional modules, including:

After the calling address of the first external interface function and the calling address of the at least one external interface function are successfully matched, the first external interface function is called to test the functional module.
The method according to claim 1 or 2, characterized in that the function call address information includes the identification of the functional module, and in response to the test command line, calling at least one of the at least one external interface function Part of the testing of the functional modules also includes:

According to the identification of the functional module, at least part of the at least one external interface function is called to test the functional module.
The method according to any one of claims 1 to 4, characterized in that the function callback information also includes value range information of the first external interface function input parameter, and the test command line includes the first external Parameter values of the interface function. Before calling at least part of the at least one external interface function to test the functional module, the method further includes:

It is determined that the parameter value matches the value range information.
The method according to any one of claims 1 to 5, characterized in that said obtaining a test command line includes:

Obtain the test command line sent by the external access device.
The method of claim 6, further comprising:

Send the test results of the functional module to the external access device.
A control device, characterized by including:

The first acquisition unit is used to obtain the function callback information of the functional module. The function callback information includes the calling address of at least one external interface function of the functional module. The testing of the functional module relies on other functional modules to call the at least one External interface function, the at least one external interface function is used to test the functional module;

The second acquisition unit is used to acquire a test command line, where the test command line includes function call address information, wherein the function call address information is used to indicate testing of at least one of the at least one external interface function of the functional module. Part of the calling address;

A testing unit, configured to respond to the test command line and call the at least one external interface function to test the functional module.
The control device according to claim 8, characterized in that the test unit is also used for:

Confirm that the proxy function is enabled, wherein when the proxy function is enabled, the at least one external interface function is called according to the test command line.
The control device according to claim 8 or 9, characterized in that the function call address information includes the call address of the first external interface function, and the test unit is specifically used for:

After the calling address of the first external interface function and the calling address of the at least one external interface function are successfully matched, the first external interface function is called to test the functional module.
The control device according to claim 8 or 9, characterized in that the function call address information includes the identification of the functional module, and the test unit is specifically used for:

According to the identification of the functional module, at least part of the at least one external interface function is called to test the functional module.
The control device according to any one of claims 8 to 11, wherein the function callback information also includes value range information of the first external interface function input parameter, and the test command line includes the first Parameter values of external interface functions, the test unit is specifically used for:

Before calling at least part of the at least one external interface function to test the functional module, it is determined that the parameter value matches the value range information.
The control device according to any one of claims 8 to 12, characterized in that the second acquisition unit is specifically used for:

Obtain the test command line sent by the external access device.
The control device according to claim 13, characterized in that the device further includes:

A sending unit, configured to send test results of the functional module to the external access device.
A control device, characterized by including:

Memory, used to store computer instructions;

A processor, configured to execute computer instructions stored in the memory, so that the device performs the method according to any one of claims 1 to 7.
A micro control unit, characterized by comprising the control device according to any one of claims 8 to 15.
A computer storage medium, characterized in that computer instructions are stored in the computer storage medium, and when the instructions are executed on a computer, they cause the computer to perform the method according to any one of claims 1 to 7.
A chip, characterized in that it includes a processor, the processor being used to execute the method according to any one of claims 1 to 7.
A computer program product, characterized in that, when the computer program code or instructions are executed on a computer, the computer causes the computer to perform the method according to any one of claims 1 to 7.