CN117909237A - Test data preparation method, device and storage medium - Google Patents

Abstract

The application provides a test data preparation method, a device and a storage medium, relates to the technical field of communication, and can improve test data preparation efficiency. The method comprises the following steps: acquiring identification information of a target application and an interface method to be tested; the interface method to be tested is a method on a target application interface; monitoring a target application based on the identification information of the target application; when the interface method to be tested is called, determining and executing a key method corresponding to the interface method to be tested; the key method is used for assisting the interface method to be tested in completing the interface test. The method is applied to the process of test data preparation.

Description

Test data preparation method, device and storage medium

Technical Field

The present application relates to the field of communication technology, and in particular to a test data preparation method, device and storage medium.

Background technique

During the interface testing process, when the target interface is called, the test data preparation needs to be completed first. Only when the test data preparation is complete and accurate can the target interface test accuracy be improved.

In the related art, during the test data preparation process, the server will call all methods in the target interface. However, there are many methods in the target interface, and the server will increase the load if it executes all methods in sequence. In addition, the logical relationship between the methods in the target interface is complex. When a method is abnormal, the server may not be able to execute the method associated with the method, which reduces the efficiency of test data preparation. Therefore, how to improve the efficiency of test data preparation is a technical problem that needs to be solved.

Summary of the invention

The present application provides a test data preparation method, device and storage medium, which can improve the test data preparation efficiency.

In order to achieve the above objectives, this application adopts the following technical solutions:

In a first aspect, the present application provides a test data preparation method, which includes: a test data preparation device obtains identification information of a target application and an interface method to be tested; the interface method to be tested is a method on the target application interface; the test data preparation is based on the identification information of the target application, and monitors whether the interface method to be tested in the target application is called; when the interface method to be tested is called, the test data preparation determines and executes a key method corresponding to the interface method to be tested; the key method is used to assist the interface method to be tested to complete the interface test.

In a possible implementation, basic information of a key method is obtained; the basic information includes: a class path, a method name, and a method input parameter; and based on the basic information, the key method is executed.

In one possible implementation, the class object is obtained by reflecting the value of the class path; based on the class object, the instance object is determined; based on the value of the method name and the class object, the method object is determined; and the target algorithm of the method object is executed using the value of the method input parameter and the instance object as input parameters.

In a possible implementation, a security check is performed on the method object.

In a possible implementation, the target algorithm includes an invoke method.

In a possible implementation, the class path includes a package name and a class name.

In the second aspect, the present application provides a test data preparation device, which includes: an acquisition unit and a processing unit; the acquisition unit is used to acquire the identification information of the target application and the interface method to be tested; the interface method to be tested is a method on the target application interface; the processing unit is used to monitor whether the interface method to be tested in the target application is called based on the identification information of the target application; the processing unit is also used to determine and execute the key method corresponding to the interface method to be tested when the interface method to be tested is called; the key method is used to assist the interface method to be tested to complete the interface test.

In a possible implementation, the acquisition unit is further used to acquire basic information of the key method; the basic information includes: class path, method name and method input parameters; the processing unit is used to execute the key method based on the basic information.

In one possible implementation, the processing unit is also used to: obtain a class object by reflecting the value of the class path; determine the instance object based on the class object; determine the method object based on the value of the method name and the class object; and execute the target algorithm of the method object using the value of the method input parameter and the instance object as input parameters.

In a possible implementation, the processing unit is further configured to perform a security check on the method object.

In a possible implementation, the target algorithm includes an invoke method.

In a possible implementation, the class path includes a package name and a class name.

In a third aspect, the present application provides a test data preparation device, comprising: a processor and a communication interface; the communication interface and the processor are coupled, and the processor is used to run a computer program or instructions to implement the test data preparation method described in the first aspect and any possible implementation method of the first aspect.

In a fourth aspect, the present application provides a computer-readable storage medium, which stores instructions. When the instructions are executed on a terminal, the terminal executes the test data preparation method described in the first aspect and any possible implementation of the first aspect.

In a fifth aspect, the present application provides a computer program product comprising instructions, which, when executed on a test data preparation device, enables the test data preparation device to execute the test data preparation method as described in the first aspect and any possible implementation of the first aspect.

In a sixth aspect, the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface and the processor are coupled, and the processor is used to run a computer program or instructions to implement the test data preparation method as described in the first aspect and any possible implementation method of the first aspect.

Specifically, the chip provided in the present application also includes a memory for storing computer programs or instructions.

In the test data preparation method provided in the embodiment of the present application, the test data preparation device obtains the identification information of the target application and the interface method to be tested on the target application interface. In this way, the test data preparation device can monitor whether the interface method to be tested in the target application is called according to the identification information of the target application. When the interface to be tested in the target application is about to be called, the test data preparation device determines the key method corresponding to the interface method to be tested. Since the key method can assist the interface method to be tested to complete the interface test, the key method of the test data preparation device can accurately complete the preparation of the test data. Compared with the prior art, the server needs to execute all methods in the target interface to realize the preparation of the test data. In the present application, when the interface method to be tested is called, it only needs to execute the key method to realize the preparation of the test data. Therefore, the present application can improve the efficiency of test data preparation.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of the structure of a test data preparation system provided in an embodiment of the present application;

FIG2 is a schematic diagram of the structure of a test data preparation device provided in an embodiment of the present application;

FIG3 is a flow chart of a test data preparation method provided in an embodiment of the present application;

FIG4 is a schematic diagram of a test data preparation page provided in an embodiment of the present application;

FIG5 is a schematic diagram of a test data preparation interface provided in an embodiment of the present application;

FIG6 is a flow chart of another test data preparation method provided in an embodiment of the present application;

FIG7 is a schematic diagram of a test data preparation page provided in an embodiment of the present application;

FIG8 is a flow chart of another test data preparation method provided in an embodiment of the present application;

FIG9 is a flow chart of another test data preparation method provided in an embodiment of the present application;

FIG. 10 is a schematic diagram of the structure of another test data preparation device provided in an embodiment of the present application.

Detailed ways

The test data preparation method, device and storage medium provided in the embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

The term "and/or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

The terms "first" and "second" and the like in the specification and drawings of this application are used to distinguish different objects, or to distinguish different processing of the same object, rather than to describe a specific order of objects.

In addition, the terms "including" and "having" and any variations thereof mentioned in the description of the present application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products or devices.

It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

During the interface testing process, when the target interface is called, the test data preparation needs to be completed first. Only when the test data preparation is complete and accurate can the target interface test accuracy be improved.

In the related art, during the test data preparation process, the server will call all methods in the target interface. However, there are many methods in the target interface, and the server will increase the load if it executes all methods in sequence. In addition, the logical relationship between the methods in the target interface is complex. When a method is abnormal, the server may not be able to execute the method associated with the method, which reduces the efficiency of test data preparation. Therefore, how to improve the efficiency of test data preparation is a technical problem that needs to be solved.

The example in Figure 1 is just a simple example. In actual business systems, the interactions between services involved in the number-making process are much more complex and the possibility of being affected is much greater. In the number-making process, some irrelevant interactions or codes often cause number-making interruptions and failures. If these irrelevant interactions and codes can be skipped and the key code or method can be executed directly (such as directly executing method B-2), the success rate of number-making will be greatly improved.

The above scheme brings at least the following beneficial effects: In the embodiment of the present application, the test data preparation device obtains the identification information of the target application and the interface method to be tested on the target application interface. In this way, the test data preparation device can monitor the target application according to the identification information of the target application. When the interface to be tested in the target application is about to be called, the test data preparation device determines the key method corresponding to the interface method to be tested. Since the key method can assist the interface method to be tested to complete the interface test, the key method of the test data preparation device can accurately complete the preparation of the test data. Compared with the prior art, the server needs to execute all methods in the target interface to realize the preparation of the test data. In the present application, when the interface method to be tested is called, it only needs to execute the key method to realize the preparation of the test data. Therefore, the present application can improve the efficiency of test data preparation.

Hereinafter, a test data preparation system 10 provided in an embodiment of the present application will be described in detail in conjunction with FIG. 1 . As shown in FIG. 1 , the test data preparation system 10 includes: a test data preparation device 11 and a terminal device 12 .

The test data preparation device 11 is configured to obtain the identification information of the target application and the interface method to be tested; the interface method to be tested is the method on the target application interface; based on the identification information of the target application, monitor whether the interface method to be tested in the target application is called; when the interface method to be tested is called, determine and execute the key method corresponding to the interface method to be tested; the key method is used to assist the interface method to be tested to complete the interface test.

The terminal device 12 is configured to send identification information of the target application and the interface method to be tested to the test data preparation device 11 .

It should be noted that the test data preparation device 11 and the terminal device 12 are devices with wireless communication functions, which can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted. It can also be deployed on the water surface (such as ships, etc.). It can also be deployed in the air (for example, on airplanes, balloons, and satellites, etc.). The user terminal is also called a mobile station (mobilestation, MS), a terminal (mobile terminal, MT), and a terminal, etc., which is a device that provides voice and/or data connectivity to users. For example, a terminal includes a handheld device with a wireless connection function, a vehicle-mounted device, etc. At present, the terminal can be: a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device (such as a smart watch, a smart bracelet, a pedometer, etc.), an in-vehicle device (such as a car, a bicycle, an electric car, an airplane, a ship, a train, a high-speed train, etc.), a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a smart home device (such as a refrigerator, a TV, an air conditioner, an electric meter, etc.), an intelligent robot, a workshop device, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, or a wireless terminal in a smart home, a flying device (such as an intelligent robot, a hot air balloon, a drone, an airplane), etc. In a possible application scenario of the present application, the test data preparation device 11 and the terminal device 12 are terminal devices that often work on the ground, such as an in-vehicle device. In this application, for the sake of convenience, chips deployed in the above-mentioned devices, such as system-on-a-chip (SOC), baseband chips, etc., or other chips with communication functions may also be referred to as user terminals.

Optionally, the test data preparation device 11 and the terminal device 12 may be embedded communication devices or user handheld communication devices, including mobile phones, tablet computers, etc.

As an example, in an embodiment of the present application, the test data preparation device 11 and the terminal device 12 can also be wearable devices. Wearable devices can also be called wearable smart devices, which are a general term for wearable devices that use wearable technology to intelligently design and develop wearable devices for daily wear, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and independent of smartphones to achieve complete or partial functions, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

The embodiment of the present application provides a test data preparation device for executing the test data preparation system provided by the embodiment of the present application. FIG2 is a schematic diagram of the structure of a test data preparation device provided by the embodiment of the present application. As shown in FIG2, the test data preparation device 200 includes at least one processor 201, a communication line 202, and at least one communication interface 204, and may also include a memory 203. Among them, the processor 201, the memory 203 and the communication interface 204 can be connected through the communication line 202.

The processor 201 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, such as one or more digital signal processors (DSP), or one or more field programmable gate arrays (FPGA).

The communication link 202 may include a pathway for transmitting information between the above-mentioned components.

The communication interface 204 is used to communicate with other devices or communication networks, and can use any transceiver-like device, such as Ethernet, radio access network (RAN), WLAN, etc.

The memory 203 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compressed optical disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to include or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to these.

In one possible design, the memory 203 can exist independently of the processor 201, that is, the memory 203 can be a memory outside the processor 201. In this case, the memory 203 can be connected to the processor 201 through the communication line 202, and is used to store execution instructions or application code, and the execution is controlled by the processor 201 to implement the test data preparation method provided in the following embodiment of the present application. In another possible design, the memory 203 can also be integrated with the processor 201, that is, the memory 203 can be the internal memory of the processor 201, for example, the memory 203 is a high-speed cache, which can be used to temporarily store some data and instruction information, etc.

In one example, the processor 201 may include one or more CPUs, for example, CPU0 and CPU1.

As an optional implementation, the test data preparation device 200 includes multiple processors.

As an optional implementation, the test data preparation device 200 further includes an output device and an input device. Exemplarily, the output device is a display screen, a speaker, and the like, and the input device is a keyboard, a mouse, a microphone, or a joystick, and the like.

It should be noted that the test data preparation device 200 may be a desktop computer, a portable computer, a network server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system or a device having a similar structure as shown in FIG2. In addition, the composition structure shown in FIG2 does not constitute a limitation on the various devices in FIG1 and FIG2. In addition to the components shown in FIG2, the various devices in FIG1 and FIG2 may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

In the embodiment of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices.

In addition, the actions, terms, etc. involved in the various embodiments of the present application can refer to each other without limitation. The message identification information or parameter identification information in the message exchanged between the various devices in the embodiments of the present application is only an example, and other identification information can also be used in the specific implementation without limitation.

The following describes the test data preparation method provided by the embodiment of the present application in conjunction with the test data preparation system shown in Figure 1. Among them, the actions, terms, etc. involved in the various embodiments of the present application can refer to each other without limitation. The message identification information exchanged between the various devices in the embodiment of the present application or the parameter identification information in the message is only an example, and other identification information can also be used in the specific implementation without limitation. The actions involved in the various embodiments of the present application are only an example, and other identification information can also be used in the specific implementation, such as: "included in" in the embodiment of the present application can also be replaced by "carried on" or "carried in", etc.

In order to solve the problems existing in the above-mentioned prior art, the embodiment of the present application proposes a test data preparation method for implementing test data preparation. As shown in FIG3 , the method includes:

S301. A test data preparation device obtains identification information of a target application and an interface method to be tested.

The interface method to be tested is a method on the target application interface.

In a possible implementation, the test data preparation device sends a first request message to a terminal device in the test data preparation device, the first request message is used to request to obtain the identification information of the target application and the interface method to be tested. The test data preparation device receives a first response message from the device that brings the terminal, the first response message including the identification information of the target application and the interface method to be tested.

It is understandable that the tester (user) can input the identification information of the target application and the interface method to be tested and other information in the preset interface associated with the test data preparation apparatus displayed on the terminal device.

Optionally, the preset interface may be an interface in the form of a web page, and the terminal device is an electronic device that can display a web page, such as a mobile phone, a computer, or other device.

Optionally, the terminal device may also be an independent device.

Optionally, the display interface of the terminal device includes an operation button, and the operation button includes at least one of the following: edit, delete, and add. The identification information of the target application includes the name of the target application.

Exemplarily, as shown in FIG. 4 , the user may input identification information (userService) of the target application, the interface method to be tested (com.xxx.common.controller.Action.query), and other information in the interface shown in FIG. 4 .

S302: The test data preparation device monitors whether the interface method to be tested in the target application is called based on the identification information of the target application.

In a possible implementation, the test data preparation apparatus sends first indication information to the terminal device, and the first indication information is used to trigger an injection monitoring button to achieve the purpose of monitoring the interface method to be tested in the target application.

Exemplarily, as shown in FIG. 4 , the test data preparation apparatus sends first indication information to the terminal device, and the terminal device clicks an injection monitoring button based on the first indication information, thereby triggering the test data preparation apparatus to monitor the target application.

In another possible implementation, the test data preparation device sends second indication information to a server to which the target application belongs, where the second indication information is used to instruct the server to monitor the interface method to be tested in the target application.

It is understandable that after receiving the second indication information, the server monitors the interface method to be tested in the target application and feeds back the monitoring result to the test data preparation device in real time.

Optionally, after the test data preparation device monitors the interface method to be tested in the target application based on the identification information of the target application, the recording server may execute the second indication information and mount the second indication information to the process of the target application.

Exemplarily, the second instruction information is: ./sandbox.sh-p 6599-d'service-monitor/startMonit', where 6599 is the process of the target application (which can be obtained through the ps-ef|grep-i xxx|awk'{print$2}' command, and xxx is the identification information of the target application). sandbox.sh is the mount monitoring startup command of the jvm-sandbox pre-installed on the server where the target application is located; service-monitor/startMonit refers to the package identification information of the logical package that implements the monitoring logic executed after the mount monitoring.

S303: When the interface method to be tested is called, the test data preparation device determines and executes the key method corresponding to the interface method to be tested.

Among them, the key method is used to assist the interface method to be tested to complete the interface test.

In a possible implementation, when it is detected that the interface method to be tested is about to be called, the test data preparation device determines and executes the key method corresponding to the interface method to be tested based on the key method mapping table.

It should be explained that the test data preparation device inserts the monitoring code into the front end of the code of the interface method to be tested in the target application. When the interface method to be tested is called, the method calling device will execute the code of the interface method to be tested in sequence. When the monitoring code is executed, the test data preparation device can monitor the interface method being called, thereby determining that the interface method to be tested is called. The method calling device can be a test data preparation device or other equipment.

Optionally, the key method mapping table includes at least one interface method to be tested and a key method corresponding to each interface method to be tested. Any one of the at least one interface method to be tested is mapped to at least one key method.

Exemplarily, the query interface method mapping includes method B-1 and method B-2.

Exemplarily, as shown in FIG5 , the current network service is a flash sale activity, and the current target interface is the query interface for the flash sale activity. The test scenario is to test that when a user has already purchased something, the query interface should return that the user has participated in the activity and is not allowed to participate in the purchase again. The staff can log in to the activity page, query the participation qualifications, and further obtain the purchase activity. For this scenario, before calling the query interface, it is necessary to construct the user data that has participated in the purchase. Under normal circumstances, the server can first call the purchase interface (with the user's login session information) so that the user data is modified to have been purchased, and then call the query interface (with the same user's login session information), so that the test purpose can be achieved.

However, the snap-up interface may fail to execute. As shown in Figure 5, the snap-up interface includes: code block A, code block B, code block C, code block B includes code block B-1 and code block B-2, and code block B-1 is connected to other interfaces. The query interface includes: code block D, code block E, and code block F. Each code block corresponds to a method, that is, the interface method to be tested of code block A is method A, the interface method to be tested of code block B is method B, method B includes method B-2, and the interface method to be tested of code block C is method C. The snap-up can only be successful (processed by code block B) when the user meets the conditions for participating in the activity. In code block B, method B-2 will be executed to process the snap-up logic when the user meets the conditions for participating. To determine whether the user meets the conditions for participating, it is necessary to request an interface of another service to obtain it. If this other interface is abnormal, the subsequent method B-2 will not be executed, which will cause the snap-up interface processing to fail, and ultimately cause the number creation to fail.

The above scheme brings at least the following beneficial effects: In the embodiment of the present application, the test data preparation device obtains the identification information of the target application and the interface method to be tested on the target application interface. In this way, the test data preparation device can monitor whether the interface method to be tested in the target application is called according to the identification information of the target application. When the interface to be tested in the target application is about to be called, the test data preparation device determines the key method corresponding to the interface method to be tested. Since the key method can assist the interface method to be tested to complete the interface test, the key method of the test data preparation device can accurately complete the preparation of the test data. Compared with the prior art, the server needs to execute all methods in the target interface to realize the preparation of the test data. In the present application, when the interface method to be tested is called, it only needs to execute the key method to realize the preparation of the test data. Therefore, the present application can improve the efficiency of test data preparation.

In a possible implementation, in combination with FIG. 3 , as shown in FIG. 6 , S303 , when the interface method to be tested is called, the process in which the test data preparation device determines and executes the key method corresponding to the interface method to be tested can be specifically implemented by the following S601 - S602 .

S601. When the interface method to be tested is called, the test data preparation device obtains basic information of the key method.

The basic information includes: class path, method name, and method input parameters; the class path includes package name and class name.

In a possible implementation manner, the test data preparation device obtains basic information of each key method in at least one key method.

It needs to be explained that the class path refers to the full path name of the class to which the method to be executed belongs; the method name refers to the method to be executed; and the method input refers to the parameters to be input into the method when executing the key method.

For example, as shown in FIG7 , the identification information of the target application (userService), the interface method to be tested (com.xxx.common.controller.Action.query), and the key methods corresponding to the interface method to be tested include purchase and flush. The class path of the purchase key method is com.xxx.common.action.Operator, where com.xxx.common.action is the package name, Operator is the class name, and the method input parameter is {"type":"01":"userld":"66523598412"}; the class path of the flush key method is com.xxx.common.utils.Data, where com.xxx.common.utils. is the package name, Data is the class name, and the method input parameter is {"userld":"66523598412"}.

It should be noted that, as shown in FIG7 , each key method can be operated. The operations include editing and deleting. In this way, the staff can modify the key method corresponding to the interface method to be tested according to the actual working scenario and personal experience.

Optionally, the test data preparation device may modify the key method information corresponding to the interface method to be tested, and update the key method mapping table based on the modification result, so as to accurately determine the key method corresponding to the interface method to be tested.

S602: The test data preparation device executes the key method based on the basic information.

In a possible implementation, the test data preparation device numbers each key method based on the sequence of each key method in the at least one key method obtained, and executes the key methods in sequence based on the key method numbers and basic information of the key methods.

The above scheme brings at least the following beneficial effects: In the embodiment of the present application, the test data preparation device executes the key method based on the basic information of the key method, which can ensure that the key method is accurately executed when calling the interface method to be tested, avoid the waste of resources caused by executing the key method, and improve the test data preparation efficiency.

In a possible implementation, in combination with FIG. 6 , as shown in FIG. 8 , S602 , the process in which the test data preparation device executes the key method based on the basic information can be specifically implemented through the following S801 - S804 .

S801. The test data preparation device obtains a class object by reflecting the value of the class path.

The first value is used to represent the class object, the instance object is converted from the class object, and the class object is obtained by reflecting the first value.

In a possible implementation, the test data preparation device reads a first value of the class path, performs reflection processing on the first value, and obtains a class object represented by the first value.

Exemplarily, the first value includes: com.xxx.common.action.Operator or com.xxx.common.utils.Data.

S802: The test data preparation device determines an instance object based on the class object.

In a possible implementation, the test data preparation device obtains a constructor object based on the class object, and then obtains an instance object of the class through the constructor object.

S803: The test data preparation device determines the method object based on the value of the method name and the class object.

In a possible implementation, the test data preparation device determines the method object based on the second value of the method name and the class object.

Exemplarily, the second value includes: purchase or flush.

S804. The test data preparation device uses the numerical value and instance object of the method input as input parameters to execute the target algorithm of the method object.

Among them, the target algorithm includes the invoke method.

In a possible implementation, the test data preparation device uses the third value and the instance object of the method input as input parameters to execute the target algorithm of the method object.

Exemplarily, the second value includes: {"type":"01":"userld":"66523598412"} or {"userld":"66523598412"}.

The above scheme brings at least the following beneficial effects: In the embodiment of the present application, the test data preparation device executes the key method based on the basic information of the key method, which can ensure that the key method is accurately executed when calling the interface method to be tested, avoid the waste of resources caused by executing the key method, and improve the test data preparation efficiency.

In a possible implementation, in combination with FIG8, as shown in FIG9, at S804, the test data preparation device uses the numerical value and instance object of the method input as input parameters and executes the target algorithm of the method object before the test data preparation device can also process the method object. The process that the test data preparation device can also process the method object can be specifically implemented by the following S901.

S901. The test data preparation device performs a security check on the method object.

In a possible implementation, the test data preparation device calls the setAccessible(true) function to execute the method object to implement a security check on the method object.

It should be explained that the setAccessible(true) function can prohibit checking access rights, so that the test data preparation device can execute private methods.

The above scheme brings at least the following beneficial effects: In the embodiment of the present application, the test data preparation device calls the setAccessible(true) function to execute the method object, so that even if the key method is a private method in a class, it can be triggered and executed separately. It can ensure that the key method is accurately executed when calling the interface method to be tested, avoid the waste of resources caused by executing the non-key method, and improve the efficiency of test data preparation.

It is understandable that the above-mentioned test data preparation method can be implemented by a test data preparation device. In order to realize the above-mentioned functions, the test data preparation device includes hardware structures and/or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the modules and algorithm steps of each example described in the embodiments disclosed herein, the embodiments disclosed in the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the embodiments disclosed in the present application.

The embodiment disclosed in the present application can divide the functional modules according to the test data preparation device generated by the above method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment disclosed in the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

FIG10 is a schematic diagram of the structure of a test data preparation device provided by an embodiment of the present invention. As shown in FIG10 , the test data preparation device 100 can be used to execute the test data preparation method shown in FIG3 , FIG6 , FIG7 , FIG8 , and FIG9 . The test data preparation device 100 includes: an acquisition unit 1001 and a processing unit 1002 .

Acquisition unit 1001 and processing unit 1002; acquisition unit 1001 is used to acquire identification information of the target application and the interface method to be tested; the interface method to be tested is the method on the target application interface; processing unit 1002 is used to monitor whether the interface method to be tested in the target application is called based on the identification information of the target application; processing unit 1002 is also used to determine and execute the key method corresponding to the interface method to be tested when the interface method to be tested is called; the key method is used to assist the interface method to be tested to complete the interface test.

In a possible implementation, the acquisition unit 1001 is further used to acquire basic information of the key method; the basic information includes: class path, method name and method input parameters; the processing unit 1002 is used to execute the key method based on the basic information.

In one possible implementation, the processing unit 1002 is also used to: obtain a class object by reflecting the value of the class path; determine the instance object based on the class object; determine the method object based on the value of the method name and the class object; and execute the target algorithm of the method object using the value of the method input parameter and the instance object as input parameters.

In a possible implementation, the processing unit 1002 is further configured to perform a security check on the method object.

In a possible implementation, the target algorithm includes an invoke method.

In a possible implementation, the class path includes a package name and a class name.

Through the description of the above implementation methods, technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device and unit described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

The present disclosure also provides a computer-readable storage medium having instructions stored thereon. When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the test data preparation method provided by the above-mentioned embodiment of the present disclosure.

The embodiments of the present disclosure also provide a computer program product including instructions, which, when executed on an electronic device, enables the electronic device to execute the test data preparation method provided by the embodiments of the present disclosure.

Among them, the computer readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer readable storage media (a non-exhaustive list) include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a register, a hard disk, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above, or any other form of computer readable storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an application-specific integrated circuit (ASIC). In the embodiments of the present application, a computer-readable storage medium may be any tangible medium that contains or stores a program, which may be used by or in conjunction with an instruction execution system, apparatus, or device.

The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (10)

1. A test data preparation method, characterized in that the method comprises: Obtain identification information of a target application and an interface method to be tested; the interface method to be tested is a method on the target application interface; Based on the identification information of the target application, monitoring whether the interface method to be tested in the target application is called; When the interface method to be tested is called, a key method corresponding to the interface method to be tested is determined and executed; the key method is used to assist the interface method to be tested to complete the interface test. 2. The method according to claim 1, characterized in that the determining and executing the key method comprises: Obtain basic information of the key method; the basic information includes: class path, method name and method input parameters; Based on the basic information, the key method is executed. 3. The method according to claim 2, characterized in that the executing the key method based on the basic information comprises: Obtaining a class object by reflecting the value of the class path; Based on the class object, determining an instance object; Determining a method object based on the value of the method name and the class object; The method object's target algorithm is executed using the method's input parameter value and the instance object as input parameters. 4. The method according to claim 3, characterized in that before taking the third value of the method input parameter and the instance object as input parameters, the method further comprises: Performs a security check on the method object. 5. The method according to claim 3, characterized in that the target algorithm includes an invoke method. 6. The method according to any one of claims 2 to 5, characterized in that the class path includes a package name and a class name. 7. A test data preparation device, characterized in that the device comprises: an acquisition unit and a processing unit; The acquisition unit is used to acquire identification information of the target application and the interface method to be tested; the interface method to be tested is a method on the target application interface; The processing unit is used to monitor whether the interface method to be tested in the target application is called based on the identification information of the target application; The processing unit is further used to determine and execute a key method corresponding to the interface method to be tested when the interface method to be tested is called; the key method is used to assist the interface method to be tested to complete the interface test. 8. The device according to claim 7, characterized in that the device comprises: The acquisition unit is further used to acquire basic information of the key method; the basic information includes: class path, method name and method input parameters; The processing unit is used to execute the key method based on the basic information. 9. A test data preparation device, characterized in that it comprises: a processor and a communication interface; the communication interface is coupled to the processor, and the processor is used to run a computer program or instruction to implement the test data preparation method as described in any one of claims 1-6. 10. A computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium, wherein when a computer executes the instructions, the computer executes the test data preparation method described in any one of claims 1 to 6.