Automatic joint debugging method and device capable of being paused based on service function
By building and combining test scripts in business joint debugging and setting up pause nodes, the problem of manual cooperation in the existing technology is solved, and automated joint debugging is realized, and efficiency and resource utilization are improved.
Patent Information
- Application Number
- CN202410995334.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-23
- Publication Date
- 2024-11-15
AI Technical Summary
During the existing business joint commissioning process, it is difficult for testers to view and modify intermediate data in real time, resulting in manual cooperation with demand, resulting in untimely response and waste of resources, affecting project progress.
By building test scripts corresponding to business function modules, combining them into business scenario scripts, and setting up pause nodes in the scripts to obtain and adjust joint debugging data to continue execution, avoiding manual intervention.
It realizes automated joint commissioning, saves labor costs, improves joint commissioning efficiency, and facilitates viewing and verifying intermediate data without the need for multiple module testers to coordinate.
Smart Images

Figure CN118964187A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of testing technology, and in particular to a pausable automated joint debugging method and device based on business functions. Background Art
[0002] During the software development process, when the function development of a module is completed, it is usually necessary to interact with the functions of multiple business nodes of other modules of the system and transmit data, etc., and the modules need to be jointly debugged.
[0003] In the existing business joint debugging process, when a business process needs to be debugged, the tester triggers the business process through a script, and the script executes the entire business process. If you want to view, verify, modify, and other operations on the intermediate data during the joint debugging process, since the script executes the entire business process without interruption, it is very difficult to operate the intermediate data, and manual joint debugging is required. However, manual joint debugging requires the coordination of testers in each module, resulting in the following problems:
[0004] 1. Manual response is not timely. Usually, joint debugging often involves multiple modules, and it is difficult for testers from multiple modules to cooperate in the joint debugging of a business scenario at the same time.
[0005] 2. It consumes a lot of manpower costs. Testers of multiple modules need to cooperate with the joint debugging of a business scenario at the same time, which consumes a lot of testing resources and affects the project progress. Summary of the invention
[0006] In view of the above problems, embodiments of the present application are proposed to provide a pausable automated joint debugging method and device based on business functions that overcome the above problems or at least partially solve the above problems.
[0007] According to a first aspect of an embodiment of the present application, a suspendable automated joint debugging method based on a business function is provided, which includes:
[0008] Constructing the first test script corresponding to each business function module;
[0009] Combining the plurality of first test scripts according to the execution order of the business function modules to obtain a second test script for the business scenario;
[0010] A pause node is set in the second test script so that when the script is executed to the pause node, the joint debugging data executed by the first test script is obtained and / or the joint debugging data is adjusted to continue executing the second test script according to the adjusted joint debugging data.
[0011] Optionally, the first test script includes a business function module test script and a log recording script;
[0012] The logging script records the joint debugging data of the first test script execution; the joint debugging data includes input information before the business function module call execution, output information after the business function module call execution and / or variable information generated during the business function module call execution.
[0013] Optionally, setting the pause node in the second test script further includes:
[0014] At least one pause node is set in the second test script, and the pause node is set between any two adjacent first test scripts.
[0015] Optionally, setting a pause node in the second test script so as to obtain the joint debugging data executed by the first test script and / or adjust the joint debugging data when executing to the pause node to continue executing the second test script according to the adjusted joint debugging data further includes:
[0016] When the execution reaches the pause node, the execution of the second test script is paused, and the joint debugging data of the execution of the first test script recorded by the log recording script is obtained to verify the joint debugging.
[0017] Optionally, the method further comprises:
[0018] Build a log record reading script and set the log record reading script after the pause node.
[0019] Optionally, setting a pause node in the second test script so as to obtain the joint debugging data executed by the first test script and / or adjust the joint debugging data when executing to the pause node to continue executing the second test script according to the adjusted joint debugging data further includes:
[0020] When the execution reaches the pause node, the execution of the second test script is paused;
[0021] Obtain the joint debugging data of the first test script execution recorded by the log recording script, and modify the joint debugging data;
[0022] Call the log record reading script, read the modified joint debugging data, and continue to execute the second test script according to the modified joint debugging data.
[0023] Optionally, the method further comprises:
[0024] According to different functions in business scenarios, each business function module is obtained by dividing according to preset dimensions.
[0025] According to a second aspect of an embodiment of the present application, a suspendable automated joint debugging device based on a business function is provided, comprising:
[0026] A functional testing unit, adapted to construct a first test script corresponding to each business function module;
[0027] A combining unit, adapted to combine the plurality of first test scripts according to the execution order of the business function modules to obtain a second test script for the business scenario;
[0028] The pause unit is suitable for setting a pause node in the second test script so as to obtain the joint debugging data executed by the first test script and / or adjust the joint debugging data when executing to the pause node to continue executing the second test script according to the adjusted joint debugging data.
[0029] According to a third aspect of an embodiment of the present application, there is provided a computing device, comprising: a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus;
[0030] The memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute operations corresponding to the above-mentioned automatic joint debugging method that can be paused based on business functions.
[0031] According to a fourth aspect of an embodiment of the present application, a computer storage medium is provided, in which at least one executable instruction is stored, and the executable instruction enables a processor to perform operations corresponding to the above-mentioned pausible automated joint debugging method based on business functions.
[0032] According to a fifth aspect of an embodiment of the present application, a computer program product is provided, comprising at least one executable instruction, wherein the executable instruction enables a processor to perform operations corresponding to the above-mentioned pausible automated joint debugging method based on business functions.
[0033] According to the business function-based pausable automated joint debugging method and device provided in the present application, a corresponding first test script is constructed according to the business function module, each first test script can test the corresponding business function module, and the first test scripts are combined in sequence to obtain a second test script for business scenario joint debugging test. In the second test script, a pause node is flexibly set according to the joint debugging requirements. When the execution reaches the pause node, the joint debugging data of the first test script that has been jointly debugged and executed can be obtained, which is convenient for viewing and verifying the intermediate data of the joint debugging, and there is no need for the cooperation of module testers from all parties, saving manpower time and other costs.
[0034] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0035] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present application. Also, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:
[0036] Figure 1 A flowchart of a suspendable automated joint debugging method based on business functions according to an embodiment of the present application is shown;
[0037] Figure 2 A flow chart of a suspendable automated joint debugging method based on business functions according to another embodiment of the present application is shown;
[0038] Figure 3 A schematic diagram of the structure of a suspendable automatic joint debugging device based on business functions according to an embodiment of the present application is shown;
[0039] Figure 4 A schematic diagram of the structure of a computing device according to an embodiment of the present application is shown. DETAILED DESCRIPTION
[0040] The exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present application and to fully convey the scope of the present application to those skilled in the art.
[0041] First, the terms involved in one or more embodiments of the present application are explained.
[0042] Joint debugging test: After each module is implemented, the relevant interfaces are tested. The purpose of this test is to find errors in the overall design. There may be no problem when executing each module separately, but when they are combined and interact with each other, unexpected errors may occur. Therefore, the entire system needs to be debugged as a whole to ensure the overall functionality and correctness of the system.
[0043] Figure 1 A flowchart of a suspendable automated joint debugging method based on business functions according to an embodiment of the present application is shown. Figure 1 As shown, the method comprises the following steps:
[0044] Step S101, constructing a first test script corresponding to each business function module.
[0045] For the joint debugging test, this embodiment improves the way in which the existing automated script executes the entire business scenario process, avoiding the problem that the joint debugging test requires manual intervention when obtaining the intermediate data of the joint debugging. Specifically, for the business scenario of the joint debugging test, the business scenario can be divided into different business function modules according to different business functions, and for each business function module, a first test script corresponding to the business function module is constructed respectively. For example, the business function module includes multiple business function modules such as login, add purchase, payment, logistics, etc., and a first test script 1 corresponding to login, a first test script 2 corresponding to add purchase, a first test script 3 corresponding to payment, and a first test script 4 corresponding to logistics are constructed. Each first test script corresponds to a business function module, and executing a first test script can complete the test of a business function module. For example, executing the first test script 1 completes the test of the login business module, obtains the login information, and obtains the corresponding shopping cart according to the login information. Execute the first test script 2, test the add purchase module, complete the addition of items to the shopping cart, and obtain the information after the purchase, which can be used for the subsequent joint debugging test of the payment module and the logistics module.
[0046] In addition to testing the business function module, the first test script can also record the generated joint debugging data into the log, so that the joint debugging data can be easily viewed through the log.
[0047] Step S102: Combine multiple first test scripts according to the execution order of the business function modules to obtain a second test script for the business scenario.
[0048] In order to complete the joint debugging test of the business scenario, in addition to constructing the first test script, it is also necessary to combine multiple first test scripts in sequence according to the execution order of the business function modules, such as combining the first test script 1, the first test script 2, the first test script 3, and the first test script 4 in the order of the execution of the business function modules, such as login, add to purchase, payment, and logistics, to obtain the second test script of the business scenario. The second test script contains multiple first test scripts combined in sequence, such as the first test script 1, the first test script 2, the first test script 3, and the first test script 4 combined in sequence, so that when performing the joint debugging test, the first test script 1, the first test script 2, the first test script 3, and the first test script 4 are called and executed in sequence.
[0049] Step S103, setting a pause node in the second test script so that when the pause node is executed, the joint debugging data executed by the first test script is obtained and / or the joint debugging data is adjusted to continue executing the second test script according to the adjusted joint debugging data.
[0050] In addition to the first test scripts that contain multiple sequential combinations, the second test script also contains a pause node. The pause node can ensure that the second test script is suspended according to the business test requirements during the joint debugging test, and the joint debugging data generated by the execution of a certain first test script is obtained. For example, the pause node is set between the purchase module and the payment module. When the second test script is executed to the pause node, the execution is suspended. At this time, the first test script 2 has been executed, and the first test script 3 has not been executed. The joint debugging data generated after the first test script 2 can be obtained, such as the product information, quantity information, price information, etc. of the added purchase in the shopping cart. On the one hand, the tester can verify the obtained joint debugging data based on the viewing. On the other hand, the obtained joint debugging data can also be adjusted, such as modifying the joint debugging data, so as to continue to execute the second test script according to the adjusted joint debugging data. The joint debugging test covers abnormal scenarios, etc.
[0051] In this embodiment, the joint debugging test is different from the unit test and the business regression test. The unit test is only a test for the normal execution of the code layer. It tests whether the code can be executed normally. It cannot test whether the business logic of the business scenario is correct, nor does it involve the relationship between business function modules. Business regression testing, integration testing, etc. do not need to be paused. Pausing will affect the fluency of regression testing and integration testing. The joint debugging test involves whether the business logic between each business function module is executed correctly. The joint debugging data generated by the previous business function module is connected to the use of the next business function module. Therefore, viewing, verifying, and adjusting the intermediate data of the joint debugging are also required for the joint debugging test. This embodiment adds a pause node to obtain the joint debugging data, which is convenient for viewing, verification, and adjustment, and does not need to be obtained manually. The joint debugging test is completed automatically, which is more flexible and convenient.
[0052] According to the business function-based pausable automated joint debugging method provided in the present application, a corresponding first test script is constructed according to the business function module, each first test script can test the corresponding business function module, and the first test scripts are combined in sequence to obtain a second test script for the business scenario joint debugging test. In the second test script, a pause node is flexibly set according to the joint debugging requirements. When the execution reaches the pause node, the joint debugging data of the first test script that has been jointly debugged and executed can be obtained, which is convenient for viewing and verifying the intermediate data of the joint debugging, and there is no need for the cooperation of module testers from all parties, saving manpower time and other costs.
[0053] Figure 2 A flowchart of a suspendable automated joint debugging method based on business functions according to an embodiment of the present application is shown. Figure 2 As shown, the method comprises the following steps:
[0054] Step S201, according to different functions in the business scenario, each business function module is obtained by dividing according to preset dimensions.
[0055] Before building the test script for joint debugging, divide the business scenarios to be jointly debugged. According to the different functions contained in the business scenarios, they can be divided according to different dimensions, such as based on a single function point, based on different preset dimensions such as business association closeness, and divide the business scenarios into multiple business function modules. For example, for the shopping business scenario, it can be divided into multiple business function modules such as login, add to cart, payment, logistics, receipt, return, etc. The specific settings are based on the implementation situation and are not limited here.
[0056] Step S202: construct a first test script corresponding to each business function module.
[0057] According to each business function module, a corresponding first test script is constructed for it. The first test script includes a business function module test script, that is, a script that tests the specific functions of the business function module. The business function module can be tested by calling and executing the first test script.
[0058] The first test script also includes a log recording script. The log recording script is used to record the joint debugging data executed by the first test script. The joint debugging data includes input information before the business function module is called and executed, output information after the business function module is called and executed, and variable information generated during the business function module call and execution. Taking the payment module as an example, the input information includes product information, quantity information, price information, etc. in the shopping cart, the output information includes order information, etc., and the variable information includes order number generation information, the correspondence between order number and product, etc. The log recording script can record input information in the log before the first test script tests the business function module, and record output information, generated variable information, etc. after execution. The log can be set in advance, or an interface can be provided to facilitate testers to specify logs, etc., which is not limited here.
[0059] In this embodiment, the first test script corresponds to the business function module one by one, which facilitates suspension based on the business function module and timely discovers whether there are problems in the joint debugging between the business function modules.
[0060] Step S203: Combine the multiple first test scripts according to the execution order of the business function modules to obtain a second test script for the business scenario.
[0061] According to the execution order of each business function module in the business scenario, the first test scripts corresponding to each business function module are sorted and combined in sequence. When combining, the first test scripts can be called and executed in sequence according to the sorting, so as to obtain the second test script of the business scenario.
[0062] Step S204: setting at least one pause node in the second test script, wherein the pause node is set between any two adjacent first test scripts.
[0063] When setting a pause node in this embodiment, the pause node can be set between any two adjacent first test scripts, that is, after executing any first test script, the execution can be paused to verify and adjust the joint debugging data of the first test script that has been tested and executed.
[0064] One or more pause nodes can be set, which are set according to the implementation situation and are not limited here.
[0065] Step S205, constructing a log record reading script, and setting the log record reading script after the pause node.
[0066] This embodiment can also adjust the joint debugging data recorded in the log. In order to facilitate the joint debugging test, a log record reading script is also constructed. It is set after the node is paused. After adjusting the joint debugging data in the log, the log record reading script can be called to read the log so as to continue the joint debugging according to the adjusted joint debugging data.
[0067] Step S206, when the execution reaches the pause node, the execution of the second test script is paused, and the joint debugging data of the execution of the first test script recorded by the log recording script is obtained to verify the joint debugging.
[0068] The joint debugging test executes the second test script. When it reaches the pause node, the execution of the second test script is paused. At this time, the joint debugging data of each executed first test script recorded in the log recording script can be obtained, including the input information, output information, intermediate variable information, etc. of the business function module corresponding to each executed first test script. Obtaining each joint debugging data recorded in the log can facilitate testers to review and verify it, and confirm whether the business logic of the joint debugging execution of the business scenario is normal. Obtaining each joint debugging data based on the log does not require manual cooperation, which is more convenient and quick. In addition, the pause node can be set flexibly, and one or more can be set according to business needs, which is convenient and flexible to obtain joint debugging data for verification.
[0069] Step S207, when executing to the pause node, suspend the execution of the second test script; obtain the joint debugging data of the first test script execution recorded in the log recording script, and modify the joint debugging data; call the log recording reading script, read the modified joint debugging data, and continue to execute the second test script according to the modified joint debugging data.
[0070] For business scenarios, in addition to testing normal scenarios, joint debugging tests also need to consider abnormal scenarios, special scenarios, etc., and the joint debugging data needs to be adjusted so that the joint debugging test can cover abnormal scenarios, special scenarios, etc. Therefore, the second test script is executed in the joint debugging test, and when the execution reaches the pause node, the execution of the second test script is suspended. The joint debugging data of each executed first test script recorded by the log recording script is obtained, and the joint debugging data can be modified according to the specific situation of the joint debugging test so that it can cover abnormal scenarios, special scenarios, etc., such as adjusting the joint debugging data for payment exceptions, purchase failures, and other scenarios. Specifically, the log recording script records the joint debugging data in the log, and the joint debugging data in the log can be modified according to business needs. After modification, the execution log recording reading script is called to read the modified joint debugging data in the log, and the second test script is continued to be executed according to the modified joint debugging data, so that the modified joint debugging data can be used to achieve joint debugging coverage of abnormal scenarios, special scenarios, etc.
[0071] Furthermore, the execution order of step S206 and step S207 is not limited, and the corresponding steps are executed according to the implementation situation.
[0072] According to the suspendable automated joint debugging method based on business functions provided by the present application, the business scenario is divided into multiple business function modules according to preset dimensions, and the corresponding first test scripts are constructed in units of business function modules. Each first test script tests the corresponding business function module, and the log recording script records the joint debugging data required or generated by the execution of the first test script. Combine the first test scripts according to the execution order of the business function modules to obtain the second test script for the joint debugging test of the business scenario. In the second test script, one or more pause nodes can be flexibly set according to the joint debugging requirements. When the execution reaches the pause node, the execution of the second test script is suspended, and the joint debugging data of the first test script that has been executed by joint debugging is obtained, which is convenient for viewing and verifying the intermediate data of the joint debugging. Further, the joint debugging data recorded in the log can also be modified, and the log record reading script is used to read the modified joint debugging data, and the second test script is continued to be executed according to the modified joint debugging data, so as to ensure that the joint debugging test can cover various situations such as normal scenarios, abnormal scenarios, and special scenarios. The entire execution process does not require the cooperation of module testers from all parties, saving manpower time and other costs.
[0073] Figure 3 FIG. 1 shows a schematic diagram of a structure of a suspendable automatic joint debugging device based on business functions provided by an embodiment of the present application. Figure 3 As shown, the device comprises:
[0074] Functional testing unit 310, adapted to construct a first test script corresponding to each business functional module;
[0075] A combining unit 320, adapted to combine the plurality of first test scripts according to the execution order of the business function modules to obtain a second test script for the business scenario;
[0076] The pause unit 330 is adapted to set a pause node in the second test script so as to obtain the joint debugging data of the first test script when executing to the pause node and / or adjust the joint debugging data to continue executing the second test script according to the adjusted joint debugging data.
[0077] Optionally, the first test script includes a business function module test script and a log recording script;
[0078] The logging script records the joint debugging data of the first test script execution; the joint debugging data includes input information before the business function module call execution, output information after the business function module call execution and / or variable information generated during the business function module call execution.
[0079] Optionally, the pause unit 330 is further adapted to:
[0080] At least one pause node is set in the second test script, and the pause node is set between any two adjacent first test scripts.
[0081] Optionally, the pause unit 330 is further adapted to:
[0082] When the execution reaches the pause node, the execution of the second test script is paused, and the joint debugging data of the execution of the first test script recorded by the log recording script is obtained to verify the joint debugging.
[0083] Optionally, the device further includes: a reading unit 340, adapted to construct a log record reading script, and set the log record reading script after the pause node.
[0084] Optionally, the pause unit 330 is further adapted to:
[0085] When the execution reaches the pause node, the execution of the second test script is paused;
[0086] Obtain the joint debugging data of the first test script execution recorded by the log recording script, and modify the joint debugging data;
[0087] Call the log record reading script, read the modified joint debugging data, and continue to execute the second test script according to the modified joint debugging data.
[0088] Optionally, the device further includes: a division unit 350, adapted to obtain various business function modules according to different functions in a business scenario and according to preset dimensions.
[0089] The description of the above units refers to the corresponding description in the method embodiment, which will not be repeated here.
[0090] According to the business function-based pausable automated joint debugging device provided in the present application, a corresponding first test script is constructed according to the business function module, each first test script can test the corresponding business function module, and the first test scripts are combined in sequence to obtain a second test script for the business scenario joint debugging test. In the second test script, a pause node is flexibly set according to the joint debugging requirements. When the execution reaches the pause node, the joint debugging data of the first test script that has been jointly debugged and executed can be obtained, which is convenient for viewing and verifying the intermediate data of the joint debugging, and there is no need for the cooperation of module testers from all parties, saving manpower time and other costs.
[0091] The present application also provides a non-volatile computer storage medium, which stores at least one executable instruction, and the executable instruction can execute the operations corresponding to the suspendable automated joint debugging method based on business functions in any of the above method embodiments.
[0092] The present application also provides a computer program product, which includes at least one executable instruction or computer program, which can enable a processor to execute operations corresponding to the pausable automated joint debugging method based on business functions in any of the above-mentioned method embodiments.
[0093] Figure 4 A schematic diagram of the structure of a computing device according to an embodiment of the present application is shown. The specific embodiment of the present application does not limit the specific implementation of the computing device.
[0094] like Figure 4 As shown, the computing device may include: a processor (processor) 402 , a communications interface (Communications Interface) 404 , a memory (memory) 406 , and a communication bus 408 .
[0095] in:
[0096] The processor 402 , the communication interface 404 , and the memory 406 communicate with each other via a communication bus 408 .
[0097] The communication interface 404 is used to communicate with other devices such as clients or other servers.
[0098] The processor 402 is used to execute the program 410, and specifically can execute the relevant steps in the above-mentioned embodiment of the automatic joint debugging method that can be paused based on business functions.
[0099] Specifically, the program 410 may include program codes, which include computer operation instructions.
[0100] The processor 402 may be a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the present application. The one or more processors included in the computing device may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.
[0101] The memory 406 is used to store the program 410. The memory 406 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.
[0102] The program 410 can be specifically used to enable the processor 402 to execute the suspendable automated joint debugging method based on the business function in any of the above-mentioned method embodiments. The specific implementation of each step in the program 410 can refer to the corresponding descriptions in the corresponding steps and units in the above-mentioned suspendable automated joint debugging embodiment based on the business function, which will not be repeated here. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the above-mentioned devices and modules can refer to the corresponding process description in the above-mentioned method embodiment, which will not be repeated here.
[0103] The algorithm or display provided here is not inherently related to any specific computer, virtual system or other device. Various general systems can also be used together with the teaching based on this. According to the above description, it is obvious to construct the structure required for this type of system. In addition, the application is not directed to any specific programming language either. It should be understood that various programming languages can be utilized to realize the content of the application described here, and the above description of specific languages is to disclose the preferred embodiment of the application.
[0104] In the description provided herein, a large number of specific details are described. However, it is understood that the embodiments of the present application can be practiced without these specific details. In some instances, well-known methods, structures and techniques are not shown in detail so as not to obscure the understanding of this description.
[0105] Similarly, it should be understood that in order to streamline the present application and help understand one or more of the various inventive aspects, in the above description of the exemplary embodiments of the present application, the various features of the present application are sometimes grouped together into a single embodiment, figure, or description thereof. However, the disclosed method should not be interpreted as reflecting the following intention: the claimed application requires more features than the features clearly stated in each claim. More specifically, as reflected in the claims below, the inventive aspects are less than all the features of the single embodiment disclosed above. Therefore, the claims following the specific embodiment are hereby expressly incorporated into the specific embodiment, wherein each claim itself serves as a separate embodiment of the present application.
[0106] Those skilled in the art will appreciate that the modules in the devices in the embodiments may be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments may be combined into one module or unit or component, and in addition they may be divided into a plurality of submodules or subunits or subcomponents. Except that at least some of such features and / or processes or units are mutually exclusive, all features disclosed in this specification (including the accompanying claims, abstracts and drawings) and all processes or units of any method or device disclosed in this manner may be combined in any combination. Unless otherwise expressly stated, each feature disclosed in this specification (including the accompanying claims, abstracts and drawings) may be replaced by an alternative feature providing the same, equivalent or similar purpose.
[0107] In addition, those skilled in the art will appreciate that, although some embodiments herein include certain features included in other embodiments but not other features, the combination of features of different embodiments is meant to be within the scope of the present application and form different embodiments. For example, in the claims below, any one of the claimed embodiments may be used in any combination.
[0108] The various component embodiments of the present application can be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It should be understood by those skilled in the art that a microprocessor or digital signal processor (DSP) can be used in practice to implement some or all functions of some or all components of the present application. The present application can also be implemented as a device or apparatus program (e.g., computer program and computer program product) for executing a part or all of the methods described herein. Such a program implementing the present application can be stored on a computer-readable medium, or can have the form of one or more signals. Such a signal can be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.
[0109] It should be noted that the above embodiments illustrate the present application rather than limit the present application, and that those skilled in the art may design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference symbol between brackets shall not be constructed as a limitation on the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "one" or "an" preceding an element does not exclude the presence of multiple such elements. The present application may be implemented by means of hardware including several different elements and by means of a suitably programmed computer. In a unit claim that lists several devices, several of these devices may be embodied by the same hardware item. The use of the words first, second, and third, etc. does not indicate any order. These words may be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be understood as limitations on the order of execution.
Claims
1. A suspendable automated joint debugging method based on business functions, include: Constructing the first test script corresponding to each business function module; Combining the plurality of first test scripts according to the execution order of the business function modules to obtain a second test script for the business scenario; A pause node is set in the second test script so that when the execution reaches the pause node, the joint debugging data executed by the first test script is obtained and / or the joint debugging data is adjusted to continue executing the second test script according to the adjusted joint debugging data.
2. The method according to claim 1, in, The first test script includes a business function module test script and a log recording script; The logging script records the joint debugging data of the execution of the first test script; the joint debugging data includes input information before the business function module is called and executed, output information after the business function module is called and executed, and / or variable information generated during the business function module call and execution.
3. The method according to claim 1 or 2, in, The step of setting a pause node in the second test script further comprises: At least one pause node is set in the second test script, and the pause node is set between any two adjacent first test scripts.
4. The method according to any one of claims 1 to 3, in, The step of setting a pause node in the second test script so as to obtain the joint debugging data of the first test script when the script is executed to the pause node and / or adjusting the joint debugging data to continue executing the second test script according to the adjusted joint debugging data further includes: When the execution reaches the pause node, the execution of the second test script is paused, and the joint debugging data of the first test script execution recorded by the log recording script is obtained to verify the joint debugging.
5. The method according to any one of claims 1 to 3, in, The method further comprises: A log record reading script is constructed, and the log record reading script is set after the pause node.
6. The method according to claim 5, in, The step of setting a pause node in the second test script so as to obtain the joint debugging data of the first test script when the script is executed to the pause node and / or adjusting the joint debugging data to continue executing the second test script according to the adjusted joint debugging data further includes: When the execution reaches the pause node, the execution of the second test script is paused; the joint debugging data of the execution of the first test script recorded by the log recording script is obtained, and the joint debugging data is modified; Call the log record reading script, read the modified joint debugging data, and continue to execute the second test script according to the modified joint debugging data.
7. The method according to any one of claims 1 to 6, in, The method further comprises: According to different functions in business scenarios, each business function module is obtained by dividing according to preset dimensions.
8. A suspendable automated joint debugging device based on business functions, include: A functional testing unit, adapted to construct a first test script corresponding to each business function module; A combining unit, adapted to combine the plurality of first test scripts according to the execution order of the business function modules to obtain a second test script for the business scenario; The pause unit is suitable for setting a pause node in the second test script so as to obtain the joint debugging data of the first test script execution and / or adjust the joint debugging data to continue executing the second test script according to the adjusted joint debugging data when executing to the pause node.
9. A computing device, include: A processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform operations corresponding to the pausable automated joint debugging method based on business functions as described in any one of claims 1 to 7.
10. A computer storage medium, wherein at least one executable instruction is stored in the storage medium, and the executable instruction enables a processor to execute operations corresponding to the suspendable automated joint debugging method based on business functions as described in any one of claims 1 to 7.
11. A computer program product, comprising at least one executable instruction, wherein the executable instruction enables a processor to execute operations corresponding to the suspendable automated joint debugging method based on business functions as described in any one of claims 1 to 7.
