Data monitoring acceptance method and device, electronic equipment and storage medium

Abstract

The invention discloses a data monitoring acceptance method and device, electronic equipment and a storage medium. The data monitoring acceptance method comprises the steps that a data test item is constructed based on an executable interface document output by an interface test tool, and the data test item at least comprises request information, response information and result assertion; executing the data test item according to a pre-configured trigger; and outputting a data test result. Therefore, the request can be executed directly through the constructed data test item integration trigger, the corresponding information is received, and the test result is judged and output, the whole data acceptance process does not need to be manually triggered, and meanwhile, the data flow information can be automatically monitored through the trigger; and automatically triggering and executing request information in the interface document according to a user-defined mode, obtaining interface response information, and comparing, judging and outputting a test result.

Description

Technical Field

[0001] The present application relates to the technical field of computer software system testing, and in particular to a data monitoring and acceptance method, device, electronic equipment and storage medium. Background Art

[0002] During the entire process of software system development and after going online, the system development needs to be tested, maintained, and operated. In order to track business flow problems in a timely manner, testers are required to test and monitor business processes from time to time or throughout the entire process. Specifically, testers use interface testing tools to configure request information, corresponding response information, and result assertions according to the interface documents provided by developers, and then manually execute requests on the interface testing tools and wait for the interface to return response information. Finally, they manually compare the test results to see if they are correct.

[0003] It can be seen that the above data acceptance process mainly relies on testers to manually trigger the test process, which has high investment costs, is not sustainable, and cannot guarantee timely and effective acquisition of business flow problems. Summary of the invention

[0004] The embodiments of the present application provide a data monitoring and acceptance method, device, electronic device and storage medium to solve the problem that existing data testing relies on manual triggering and execution, lacks sustainability functions, resulting in low data acceptance efficiency and inability to monitor in real time.

[0005] In a first aspect, an embodiment of the present application provides a data monitoring and acceptance method, including:

[0006] Building a data test project based on the executable interface document output by the interface test tool, wherein the data test project at least includes request information, response information and result assertion;

[0007] Execute the data test items according to pre-configured triggers;

[0008] Output data test results.

[0009] In a possible embodiment, before the step of constructing a data test project from the executable interface document output by the interface testing tool, the following steps are included:

[0010] Compile interface request information based on the configuration of the interface document through the interface test tool, wherein the interface document at least includes an interface request address, an interface request type, and an interface request message;

[0011] The executable interface document is generated by an interface testing tool.

[0012] In a possible embodiment, the step of constructing a data test project from the executable interface document output by the interface testing tool includes:

[0013] Configuring the executable interface document into a build file through a build tool;

[0014] Based on the executable interface document, writing execution parameters, comparison parameters and execution result addresses corresponding to the request information in the build file;

[0015] The above-written build file is saved to the specified server address.

[0016] In a possible embodiment, the method further includes:

[0017] The data test project is built using the ANT build tool, and the trigger is configured using the Jenkins tool.

[0018] In a possible embodiment, the step of executing the data test item according to a preconfigured trigger includes:

[0019] When the trigger mechanism is reached, the request information is executed;

[0020] Obtain the response information returned by the interface;

[0021] The data test result is generated according to the result assertion.

[0022] In a possible embodiment, the trigger mechanism in the trigger includes the content of triggering the execution of the data test task or the time of triggering the execution of the data test task or the time interval between triggering the execution of two adjacent data test tasks.

[0023] In a possible embodiment, the output data test result includes:

[0024] Outputting the execution process of the data test item;

[0025] Output the response information returned by the interface;

[0026] Output a comparison result, wherein the comparison result includes a result of comparing the response information with the result assertion, whether the data information is correct, and whether the interface address is correct.

[0027] In a possible embodiment, the method further includes:

[0028] At the same time as or after the data test result is output, the data test result is sent to a specified receiving address in a specified manner.

[0029] In a second aspect, an embodiment of the present application provides a data monitoring and acceptance device, including:

[0030] A project construction module, used to construct a data test project based on the executable interface document output by the interface test tool, wherein the data test project at least includes request information, response information and result assertion;

[0031] The trigger configuration module is used to configure the triggers of the integrated execution data test project;

[0032] An execution module, used for executing the data test item according to a pre-configured trigger node through the trigger;

[0033] Output module, used to output data test results.

[0034] In a third aspect, an embodiment of the present application provides an electronic device, comprising a processor and a memory, wherein the memory stores program code, and when the program code is executed by the processor, the processor executes any one of the methods of the first aspect above.

[0035] In a fourth aspect, the present application provides a computer-readable storage medium, which includes a program code. When the storage medium is run on an electronic device, the program code is used to enable the electronic device to execute any one of the methods of the first aspect above.

[0036] On the one hand, an embodiment of the present application provides a computer program product, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium; when a processor of an electronic device reads the computer instructions from the computer-readable storage medium, the processor executes the computer instructions, so that the electronic device executes any one of the methods of the first aspect above.

[0037] The beneficial effects of this application are as follows:

[0038] The embodiment of the present application provides a data monitoring and acceptance method, device, electronic device and storage medium. Among them, the data monitoring and acceptance method includes: constructing a data test project based on an executable interface document output by an interface testing tool, wherein the data test project includes at least request information, response information and result assertion; executing the data test project according to a pre-configured trigger; and outputting the data test result. In this way, the constructed data test project can be directly integrated with the trigger to execute the request, and the corresponding information can be received, and the test results can be judged and output, without manually triggering the entire data acceptance process. At the same time, the trigger can be used to automatically monitor the data flow information, automatically trigger the request information in the execution interface document, obtain the interface response information, and compare and judge the output test results in a customized manner.

[0039] Other features and advantages of the present application will be described in the following description, and partly become apparent from the description, or understood by practicing the present application. The purpose and other advantages of the present application can be realized and obtained by the structures specifically pointed out in the written description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are only the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0041] Figure 1 This is a schematic diagram of an application scenario in an embodiment of the present application;

[0042] Figure 2 This is a flowchart of the implementation of the data monitoring and acceptance method in one embodiment of the present application;

[0043] Figure 3 This is a flowchart of an implementation method of a data monitoring and acceptance method in another embodiment of the present application;

[0044] Figure 4 This is a schematic diagram of the structure of the data monitoring and acceptance device in the embodiment of the present application;

[0045] Figure 5 The figure is a schematic diagram of the composition structure of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical scheme and advantages of the present application clearer, the technical scheme in the embodiment of the present application will be clearly and completely described below in conjunction with the drawings in the embodiment of the present application. Obviously, the described embodiment is only a part of the embodiment of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application. In the absence of conflict, the embodiments in the present application and the features in the embodiments can be arbitrarily combined with each other. In addition, although the logical order is shown in the flow chart, in some cases, the steps shown or described can be performed in an order different from that here.

[0047] The following is a brief introduction to the design concept of the embodiment of the present application:

[0048] During the system development process and the system acceptance and operation process, developers or testers need to track business flow problems in a timely manner, that is, monitor and accept system data. In the prior art, system data monitoring requires testers or developers to manually track the entire process at a fixed time or manually trigger the execution of interface message requests; during system data acceptance, testers are required to use interface testing tools to manually configure request information and corresponding response information and result assertions according to the interface document containing the request address, request type and request message provided by the developer, and then testers manually execute the interface message request in the configured interface testing tool, wait for the interface to return the response information, and then the testers manually compare the response information with the pre-set result assertion to obtain the test result. Commonly used testing tools include Jmeter and Postman. In the prior art, because configuration, execution and result comparison need to be independently implemented in the same application software, namely the above-mentioned interface testing tool, there is a lack of sustainability function, resulting in low system monitoring efficiency, manual real-time labor costs, and cannot guarantee timely and effective or uninterrupted implementation of data testing and monitoring data interface operations.

[0049] In view of this, the embodiments of the present application provide a data monitoring and acceptance method, device, electronic device and storage medium. The data monitoring and acceptance method includes:

[0050] Based on the executable interface document output by the interface testing tool, a data test project is constructed, wherein the data test project includes at least request information, response information and result assertion; the data test project is executed according to the pre-configured trigger; and the data test result is output. In this way, in addition to the existing interface testing tool, the executable interface document configuration exported by the interface testing tool can be used to construct the data test project, and at the same time, by configuring the trigger, the data test project execution is triggered, and the response information is received, the result assertion is performed, and the test result is output, which replaces the manual trigger execution, thereby realizing irregular full-process tracking of business process problems. During the system testing / operation and maintenance process, personnel developers and testers do not need to track business flow problems regularly or throughout the process. They can access the configured data test project, execute or monitor the task operation according to the specified interface at the time point specified by the trigger, the specified frequency or the specified trigger content, which can save the development process and the development / testing / operation time cost after going online.

[0051] The preferred embodiments of the present application are described below in conjunction with the drawings in the specification. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present application, and are not used to limit the present application. In addition, the embodiments and features in the embodiments of the present application may be combined with each other if there is no conflict.

[0052] like Figure 1, which is a schematic diagram of an application scenario provided by an embodiment of the present application. In the schematic diagram of the application scenario, a terminal device 101 and a server 102 are included. The terminal device 101 and the server 102 communicate with each other through a communication network.

[0053] The terminal device 101 is an electronic device used by the target object, which may be a personal computer, a mobile phone, a tablet computer, a notebook, an e-book reader, a vehicle-mounted terminal, etc. In addition, a client for the same interface document and a client for receiving test results may be installed on the terminal device 101, and the client may be a software (for example, a mailbox, a communication tool, etc.), or a web page, a small program, etc. The target object may use the above-mentioned client for providing interface documents to provide interface documents for building data test projects through the terminal device 101, and may also use the above-mentioned client for receiving test results to view test results or execution logs in real time. The target objects in this application scenario mainly include system developers, system testers, and system operation and maintenance personnel.

[0054] The server 102 may be an independent physical server or an edge device 102 in the field of cloud computing. It may also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud storage, cloud functions, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (English name: Content Delivery Network, abbreviated as CDN), as well as big data and artificial intelligence platforms.

[0055] There is no restriction on the number of the terminal devices 101 and / or servers 102 .

[0056] It should be noted that the data monitoring and acceptance method in the embodiment of the present application is jointly executed by the terminal device 101 and the server 102. The server 102 can be set as a server with the same function, or it can be set as a server with different functions. For example, when the server 102 is set as a server with the same function, the server can build data test items based on the executable interface document output by the interface testing tool, and is configured with a trigger; when the server 102 is set as a server with different functions, the servers with different functions are connected in communication. Specifically, the server that builds the data test project and the server that configures the build trigger are independent of each other and connected in communication. The server that configures the build trigger controls the server that builds the data test project to execute the request information through the communication connection. Then, the server that builds the data test project sends the test results to the terminal device 102, and the terminal device 102 receives the test results and presents the test results to the target object so that the target object can view the test results.

[0057] The following describes the data monitoring and acceptance method provided by the exemplary embodiment of the present application in combination with the above-mentioned application scenarios and with reference to the accompanying drawings. It should be noted that the above-mentioned application scenarios are only shown to facilitate understanding of the spirit and principles of the present application, and the implementation methods of the present application are not subject to any limitations in this regard.

[0058] refer to Figure 2 , is an implementation flow chart of a data monitoring and acceptance method provided in an embodiment of the present application. Here, the server is used as the execution subject for introduction. The specific implementation process of the method is as follows:

[0059] S201, constructing a data test project based on an executable interface document output by an interface test tool, wherein the data test project at least includes request information, response information and result assertion.

[0060] In this embodiment, the interface testing tool generally refers to the Jmeter tool, and its file format is a *.jmx format file. The executable interface document is a *.jmx format file generated after the Jmeter tool enters the system-related business interface script and writes the interface request information according to the request address, request type, and request message configuration in the interface document. The exported *.jmx format file participates in the construction of the data test project as the basis for writing the request information, response information, and result assertion of the data test project. Among them, the request information refers to the interface information of the request execution, such as the interface request address, request type, and request message, etc., the response information refers to the response result that should be returned corresponding to the request information that meets the data acceptance requirements, and the result assertion refers to how to compare the test response result with the response result that meets the data acceptance requirements, and locate the problem in the business process based on the judgment result.

[0061] It should be noted that the interface testing tool and the data testing project construction can be integrated on the same server, or can be set up on different servers respectively, and the communication connection can be used to enable the data testing project component to obtain the executable interface document exported by the interface testing tool.

[0062] In some implementations, before step S201, the method may further include:

[0063] First, the interface request information is written by an interface testing tool based on the configuration of the interface document, wherein the interface document at least includes an interface request address, an interface request type and an interface request message.

[0064] Then, the executable interface document is generated by an interface testing tool.

[0065] The interface document is provided by the developer, including information such as the interface request address, interface request type, and interface request message. For example, the system to be accepted or the system under development contains a small program module, and the test business flow is to accept whether the login of the small program is normal. The interface document provided by the developer at least includes the request address, interface request type, and interface request message for accessing the small program interface. The tester will use the interface test tool to configure and write the interface request information based on the document. For example, the interface script of the system-related business (the above-mentioned small program module) can be written through the Jmeter tool, and the data test project can be configured at the same time, and the request information, response information, result assertion and other related settings are allocated, and saved as a *.jmx format file. The *.jmx format file is an executable interface document that can be exported and used in other tools.

[0066] In some implementations, the method may further include, in step S201:

[0067] Configuring the executable interface document into a build file through a build tool;

[0068] Based on the executable interface document, writing execution parameters, comparison parameters and execution result addresses corresponding to the request information in the build file;

[0069] The above-written build file is saved to the specified server address.

[0070] Writing build files through build tools can make it possible for the execution of data test projects to be independent of interface test tools and exist independently on the build tools, thereby facilitating cross-platform implementation and integrated deployment.

[0071] The specific operation of configuring the executable interface document into the build file through the build tool can be to use a build file to add the executable interface document that needs to be integrated in the format of the build file, and then write the execution parameters, comparison parameters and execution result address of the data test project based on the build file after adding the executable structure document. The execution parameters here include but are not limited to the request address, request type, and request message; the comparison parameters include the preset execution task, the preset request response result, the preset data business process, and the comparison method of the response information actually returned during the execution process; the execution result address includes the address where the response information returned by the execution task arrives. Finally, the completed build file, because it is no longer dependent on the interface testing tool, can be saved in the server address specified by individuals, companies, etc., so that developers or testers or operation and maintenance personnel can access it online.

[0072] S202: Execute the data test item according to the pre-configured trigger.

[0073] Since the data test project is not directly configured on the interface test tool, but is independent of the interface test tool, the execution of the data test project can be integrated with the trigger. It should be noted that the data test project execution can be on the same server as the trigger, or can be independently configured on different servers and linked through a communication network.

[0074] As an implementation manner, the step of executing the data test item according to the pre-configured trigger in step S202 includes:

[0075] When the trigger mechanism is reached, the request information is executed;

[0076] Obtain the response information returned by the interface;

[0077] The test result is generated according to the result assertion.

[0078] Among them, the trigger mechanism refers to the content parameters pre-configured with the trigger. Specifically, the trigger includes the content that triggers the execution of the data testing task, that is, when certain specified content appears in the system development process, the data testing task is triggered to execute; or the time when the data testing task is triggered to execute, such as setting the execution of the data testing task to be triggered on a specified date or a specified time node; or the time interval between two adjacent data testing task executions, for example, executing a task every 10 minutes.

[0079] In some implementations, preferably, when the interface testing tool is Jmeter, the ANT building tool file is used to build the data testing project, and the Jenkins tool is used to configure the trigger. Figure 3 The specific implementation method of this application data monitoring and acceptance method is as follows:

[0080] S301, receiving an interface document, which is specifically provided by a developer, wherein the interface document at least includes an interface request address, a request type, and a request message.

[0081] S302, write interface request information using an interface test tool with reference to the interface document. Specifically, the developer or tester refers to the interface request address, request type, and request message in the interface document, uses the Jmeter tool to enter the system-related business interface script into Jmeter, and configures and writes the interface request information in Jmeter, wherein parameters, assertions, and related settings are all assigned and saved as a *.jmx format file.

[0082] S303, exporting the executable interface document, specifically, the developer or tester exports the *.jmx format file in Jmeter as the executable interface document.

[0083] S304, use the build tool to write a script to configure the execution parameters, comparison parameters and execution result parameters of the executable interface document. In this embodiment, the tester uses a build.xml file of Ant to add the executable interface document that needs to be integrated in the *.jmx format to the xml file, and then continues to write the corresponding execution parameters, comparison parameters, execution result parameters and execution result address parameters using the xml file. After writing, it can be stored in the personal / company server address so that it can be accessed online.

[0084] S305, configure the integrated trigger. In this embodiment, the Jenkins tool is used to configure and integrate the trigger, including configuring the integrated trigger content, trigger time, and trigger interval. It should be noted that S304 and S305 can be implemented in parallel or in series, for example, S305 is executed after S304 is completed, or S304 is executed after S305 is completed.

[0085] S306, determine whether the trigger mechanism is achieved, if yes, proceed to S307; if no, do not perform any operation. Specifically, if the system data is monitored to have a preset trigger content, the trigger mechanism is achieved; or if the specified execution time is reached, the trigger mechanism is achieved; or if a specific time interval or execution frequency is configured, the trigger mechanism is automatically achieved.

[0086] S307, execute the data test project. If the trigger mechanism is reached, the process of executing the data test project includes executing the request information, obtaining the interface response information, and generating the test result. Specifically, the request information of the data test project is integrated using the *.jmx format file and the xml file; the response information returned by the interface is obtained; and the data test result is generated according to the result assertion.

[0087] S203, output data test results. After the execution of the data test project is completed, the test structure is output, and the test results are sent to the specified address. The content of the output data test results includes: outputting the execution process of the data test project, which is usually output in the form of a log, so that developers can find business flow problems in time; outputting the response information returned by the interface, which is used to compare with the preset result of normal system operation. If there is inconsistency, it means that there is a problem with the business flow; outputting the comparison result, which includes the result of comparing the response information with the result assertion, whether the data information is correct, whether the interface address is correct, and whether the response information is returned according to the configured address. In some embodiments, the data test results are in html format, which can be used by developers or testers to check whether the data is correct or whether the interface is correct.

[0088] In some embodiments, the method may further include: simultaneously or after the data test result is output, sending the data test result to a designated receiving address in a designated manner. The preferred sending manner may be a log file in HTML format, and the receiving address may be an email address or a web page address.

[0089] Based on the same inventive concept, the present application embodiment also provides a data monitoring and acceptance device. Figure 4 As shown, it is a schematic diagram of the structure of the data monitoring and acceptance device 400, which may include:

[0090] The project construction module 401 is used to construct a data test project based on the executable interface document output by the interface test tool, and the data test project at least includes request information, response information and result assertion. In some possible implementations, the project construction module 401 is also used to configure the executable interface document into a construction file through a construction tool; based on the executable interface document, write the execution parameters, comparison parameters and execution result address corresponding to the request information in the construction file; and save the above-written construction file to a specified server address.

[0091] The trigger configuration module 402 is used to configure the trigger for the integrated execution of the data test project. In some possible implementations, the trigger mechanism in the trigger includes the content of triggering the execution of the data test task, the time of triggering the execution of the data test task, or the time interval between two adjacent data test tasks.

[0092] The execution module 403 is used to execute the data test item according to the pre-configured trigger node through the trigger. In some possible implementations, the execution module 403 is used to execute the request information when the trigger mechanism is reached; obtain the response information returned by the interface; and generate the data test result according to the result assertion.

[0093] The output module 404 is used to output the data test result. In a possible embodiment, the output module 404 can also be used to set the sending mode and receiving address of the data test result output.

[0094] In a possible embodiment, the device also includes an interface document generation module, which is used to write interface request information based on the interface document configuration through an interface testing tool, and the interface document at least includes an interface request address, an interface request type and an interface request message; the executable interface document is generated through the interface testing tool.

[0095] The data monitoring acceptance device provided in the embodiment of the present application, its project construction module 401 and trigger configuration module 402 are both independent of the interface testing tool. In addition to the existing interface testing tool, the executable interface document configuration derived from the interface testing tool can be used to construct the data test project, and at the same time, by configuring the trigger, the data test project execution is triggered, and the response information is received, the result assertion is performed, and the test result is output. Thus, a sustainable integrated solution that can be implemented across platforms and can support automatic construction and deployment is designed, which replaces manual trigger execution, and can then achieve irregular full-process tracking of business process problems. During the system testing / operation and maintenance process, personnel developers and testers do not need to track business flow problems regularly or throughout the process. Access the configured data test project, execute or monitor the task operation according to the specified interface with the time point specified by the trigger or the specified frequency or the specified trigger content, which can save the development process and the development / testing / operation time cost after going online.

[0096] In some possible implementations, the data monitoring and acceptance device according to the present application may include at least a processor and a memory. The memory stores program code, and when the program code is executed by the processor, the processor executes the steps of the data monitoring and acceptance method according to various exemplary implementations of the present application described in this specification. For example, the processor may execute the following steps: Figure 2 Follow the steps shown in .

[0097] Based on the same inventive concept, an electronic device is also provided in the embodiment of the present application, and the electronic device can realize the functions of the aforementioned data monitoring and acceptance method and device, referring to Figure 5 A schematic diagram of the structure of an electronic device in an embodiment, at the hardware level, the electronic device includes a processor 501, and optionally also includes an internal bus 500, a network interface 503, and a memory 502. Among them, the memory 502 may include a memory, such as a high-speed random access memory (Random-Access Memory, RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage, etc. Of course, the electronic device may also include hardware required for other services.

[0098] The processor 501, the network interface 503 and the memory 502 can be connected to each other through the internal bus 500, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0099] The memory 502 is used to store programs. Specifically, the program may include program codes, and the program codes include computer operation instructions. The memory may include internal memory and non-volatile memory, and provide instructions and data to the processor.

[0100] In one possible implementation, the processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, and can also obtain the corresponding computer program from other devices to form a data monitoring and acceptance device at the logical level. The processor 501 executes the program stored in the memory 501 to implement the data monitoring and acceptance method provided in any embodiment of the present application through the executed program.

[0101] As described above, the present invention Figure 2The method performed by the data monitoring and acceptance device provided in the illustrated embodiment can be applied to the processor 501, or implemented by the processor 501. The processor 501 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor 501 or an instruction in the form of software. The above processor 501 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The disclosed methods, steps and logic block diagrams in the embodiments of the present invention can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor, etc.

[0102] The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0103] Based on the same inventive concept, an embodiment of the present application also provides a storage medium, which computer-readable storage medium stores one or more programs, and the one or more programs include instructions. When the instructions are executed by an electronic device including multiple applications, the electronic device can execute the data monitoring and acceptance method provided in any embodiment of the present application.

[0104] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0105] For the convenience of description, the above device is described as various units or modules according to their functions. Of course, when implementing the present invention, the functions of each unit or module can be implemented in the same or multiple software and / or hardware.

[0106] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0107] The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0108] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0109] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A data monitoring and acceptance method, characterized in that: include: Building a data test project based on the executable interface document output by the interface test tool, wherein the data test project at least includes request information, response information and result assertion; Execute the data test items according to pre-configured triggers; Output data test results.

2. The method according to claim 1, characterized in that: Before the step of constructing a data test project from the executable interface document output by the interface test tool, the method includes: Compile interface request information based on the configuration of the interface document through the interface test tool, wherein the interface document at least includes an interface request address, an interface request type, and an interface request message; The executable interface document is generated by the interface testing tool.

3. The method according to claim 1, characterized in that: The step of constructing a data test project from the executable interface document output by the interface test tool includes: Configuring the executable interface document into a build file through a build tool; Based on the executable interface document, writing execution parameters, comparison parameters and execution result addresses corresponding to the request information in the build file; The above-written build file is saved to the specified server address.

4. The method according to claim 3, characterized in that: The method further comprises: The data test project is built using the ANT build tool, and the trigger is configured using the Jenkins tool.

5. The method according to claim 1, characterized in that: The step of executing the data test item according to the pre-configured trigger comprises: When the trigger mechanism is reached, the request information is executed; Obtain the response information returned by the interface; The data test result is generated according to the result assertion.

6. The method according to claim 5, characterized in that The trigger mechanism in the trigger includes the content that triggers the execution of a data test task, the time that triggers the execution of a data test task, or the time interval between triggering the execution of two adjacent data test tasks.

7. The method according to claim 1, characterized in that: The output data test results include: Outputting the execution process of the data test item; Output the response information returned by the interface; Output a comparison result, wherein the comparison result includes a result of comparing the response information with the result assertion, whether the data information is correct, and whether the interface address is correct.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: At the same time as or after the data test result is output, the data test result is sent to a specified receiving address in a specified manner.

9. A data monitoring and acceptance device, characterized in that: include: A project construction module, used to construct a data test project based on the executable interface document output by the interface test tool, wherein the data test project at least includes request information, response information and result assertion; The trigger configuration module is used to configure the triggers of the integrated execution data test project; An execution module, used for executing the data test item according to a pre-configured trigger node through the trigger; Output module, used to output data test results.

10. An electronic device, characterized in that: The device comprises a processor and a memory, wherein the memory stores program codes, and when the program codes are executed by the processor, the processor executes any one of the methods in claims 1 to 8.

11. A computer-readable storage medium, characterized in that: The storage medium comprises a program code, and when the storage medium is run on an electronic device, the program code is used to enable the electronic device to execute any one of the methods of claims 1 to 8.

Images