CN114666258A - Interface test method, device, electronic equipment and medium - Google Patents
Interface test method, device, electronic equipment and medium Download PDFInfo
- Publication number
- CN114666258A CN114666258A CN202210287904.1A CN202210287904A CN114666258A CN 114666258 A CN114666258 A CN 114666258A CN 202210287904 A CN202210287904 A CN 202210287904A CN 114666258 A CN114666258 A CN 114666258A
- Authority
- CN
- China
- Prior art keywords
- interface
- target
- tested
- data
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000010998 test method Methods 0.000 title description 7
- 238000012795 verification Methods 0.000 claims abstract description 103
- 230000004044 response Effects 0.000 claims abstract description 91
- 238000012360 testing method Methods 0.000 claims abstract description 90
- 238000000034 method Methods 0.000 claims description 27
- 238000004590 computer program Methods 0.000 claims description 14
- 238000012545 processing Methods 0.000 claims description 8
- 238000004458 analytical method Methods 0.000 claims description 2
- 238000010200 validation analysis Methods 0.000 claims 4
- 238000005516 engineering process Methods 0.000 abstract description 5
- 238000013473 artificial intelligence Methods 0.000 abstract description 4
- 238000004891 communication Methods 0.000 description 13
- 238000010586 diagram Methods 0.000 description 10
- 238000012544 monitoring process Methods 0.000 description 9
- 230000007547 defect Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 4
- 238000013459 approach Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/50—Testing arrangements
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
Abstract
The disclosure provides an interface testing method, which relates to the field of artificial intelligence, in particular to the technical fields of computer technology, automatic driving and the like. The implementation scheme is as follows: sending a user request to a server and determining a target interface corresponding to the user request; acquiring a response message aiming at a user request and information to be tested corresponding to a target interface from a server, wherein the information to be tested comprises first data, and the first data corresponds to a message main body of the response message; acquiring a target verification rule corresponding to a target interface, wherein the target verification rule comprises a first verification rule for verifying first data; and verifying the information to be tested based on the target verification rule.
Description
Technical Field
The present disclosure relates to the field of artificial intelligence, and in particular, to the field of computer technology and automatic driving, and in particular, to an interface testing method and apparatus, an electronic device, a computer-readable storage medium, and a computer program product.
Background
Testing of the interface may be accomplished through contract testing. The contract test is a test for synchronization when two sides of the micro service are developed between the consumer and the provider, when the contract test is carried out, a contract document can be created by the consumer side of the interface, rules of the request and the response are defined, then the provider of the interface service is requested according to the contract document, and whether the actual response is matched with the expected response is checked, so that the test of the interface is realized.
The approaches described in this section are not necessarily approaches that have been previously conceived or pursued. Unless otherwise indicated, it should not be assumed that any of the approaches described in this section qualify as prior art merely by virtue of their inclusion in this section. Similarly, unless otherwise indicated, the problems mentioned in this section should not be considered as having been acknowledged in any prior art.
Disclosure of Invention
The present disclosure provides an interface testing method, apparatus, electronic device, computer-readable storage medium, and computer program product.
According to an aspect of the present disclosure, there is provided an interface testing method, including: sending a user request to a server and determining a target interface corresponding to the user request; acquiring a response message aiming at the user request and information to be tested corresponding to the target interface from the server, wherein the information to be tested comprises first data, and the first data corresponds to a message main body of the response message; acquiring a target verification rule corresponding to the target interface, wherein the target verification rule comprises a first verification rule used for verifying the first data; and verifying the information to be tested based on the target verification rule.
According to another aspect of the present disclosure, there is provided an interface testing method, including: in response to receiving a user request from a client, acquiring a target interface and a response message corresponding to the user request; determining information to be tested corresponding to the target interface based on the user request and the response message, wherein the information to be tested comprises first data, and the first data corresponds to a message body of the response message; and sending the response message and the information to be tested to the client
According to another aspect of the present disclosure, there is provided an interface testing apparatus including: a sending module configured to send a user request to a server and determine a target interface corresponding to the user request; a first obtaining module configured to obtain, from the server, a response packet for the user request and information to be tested corresponding to the target interface, where the information to be tested includes first data, and the first data corresponds to a packet body of the response packet; a second obtaining module configured to obtain a target verification rule corresponding to the target interface, where the target verification rule includes a first verification rule for verifying the first data; and the checking module is configured to check the information to be tested based on the target checking rule.
According to another aspect of the present disclosure, there is provided an interface testing apparatus including: the system comprises an acquisition module, a processing module and a display module, wherein the acquisition module is configured to respond to a user request received from a client and acquire a target interface and a response message corresponding to the user request; a determining module configured to determine to-be-tested information corresponding to the target interface based on the user request and the response message, wherein the to-be-tested information includes first data, and the first data corresponds to a message body of the response message; and the sending module is configured to send the response message and the information to be tested to the client.
According to another aspect of the present disclosure, there is provided an electronic device including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform an interface test method.
According to another aspect of the present disclosure, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to execute an interface testing method.
According to another aspect of the present disclosure, a computer program product is provided, comprising a computer program, wherein the computer program, when executed by a processor, implements an interface testing method.
According to one or more embodiments of the present disclosure, an interface testing method is provided, which is capable of monitoring and testing an interface in real time through data generated by actual operation of a user while satisfying a user's usage requirement, so that the scene coverage of the interface testing is more comprehensive.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the embodiments and, together with the description, serve to explain the exemplary implementations of the embodiments. The illustrated embodiments are for purposes of illustration only and do not limit the scope of the claims. Throughout the drawings, identical reference numbers designate similar, but not necessarily identical, elements.
Fig. 1 illustrates a schematic diagram of an exemplary system in which various methods described herein may be implemented, in accordance with embodiments of the present disclosure;
FIG. 2 shows a flow diagram of an interface testing method according to an embodiment of the present disclosure;
FIG. 3 shows a flow diagram of an interface testing method according to an embodiment of the present disclosure;
FIG. 4 shows a block diagram of an interface test apparatus according to an embodiment of the present disclosure;
FIG. 5 shows a block diagram of an interface test apparatus according to an embodiment of the present disclosure; and
FIG. 6 illustrates a block diagram of an exemplary electronic device that can be used to implement embodiments of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of embodiments of the present disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, it will be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
In the present disclosure, unless otherwise specified, the use of the terms "first", "second", and the like to describe various elements is not intended to limit the positional relationship, the temporal relationship, or the importance relationship of the elements, and such terms are used only to distinguish one element from another. In some examples, a first element and a second element may refer to the same instance of the element, and in some cases, based on the context, they may also refer to different instances.
The terminology used in the description of the various described examples in this disclosure is for the purpose of describing particular examples only and is not intended to be limiting. Unless the context clearly indicates otherwise, if the number of elements is not specifically limited, the elements may be one or more. Furthermore, the term "and/or" as used in this disclosure is intended to encompass any and all possible combinations of the listed items.
In the related technology, contract testing aiming at an interface can be carried out based on a Pact open source framework, a consumer side creates a contract document, a request for a service provider side is defined by simulating an actual user, the service provider side provides data in a corresponding format according to the contract document established by the consumer side and returns the data to the consumer, verification is carried out through the contract document, and if the data provided by the service provider side is not matched with the contract document generated by the consumer, an exception is thrown out and a prompt is given out, so that the interface testing is realized. However, in this method, a consumer side is required to define multiple requests for different responses of the same interface and generate multiple contract documents, and a test case needs to be manually executed to perform contract testing, so that the change of the interface cannot be sensed, and the method cannot be used for monitoring the interface. Meanwhile, the check type supported by the Pact framework is simple, the support on a complex interface is poor, and the cost for modifying contract documents is high.
In order to solve the problems, the contract test aiming at the interface is driven by data generated by actual operation of a user, the use requirement of the user is met, meanwhile, the real-time monitoring and testing of the interface are realized, the defect that a consumer request needs to be simulated in the existing contract test is overcome, and the scene of the interface test is more comprehensive.
In the technical scheme of the present disclosure, the processes of collecting, storing, using, processing, transmitting, providing, disclosing and the like of the personal information of the related users all conform to the regulations of the related laws and regulations, and do not violate the good custom of the public order.
Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.
Fig. 1 illustrates a schematic diagram of an exemplary system 100 in which various methods and apparatus described herein may be implemented in accordance with embodiments of the present disclosure. Referring to fig. 1, the system 100 includes one or more client devices 101, 102, 103, 104, 105, and 106, a server 120, and one or more communication networks 110 coupling the one or more client devices to the server 120. Client devices 101, 102, 103, 104, 105, and 106 may be configured to execute one or more applications.
In embodiments of the present disclosure, the server 120 may run one or more services or software applications that enable the interface test method to be performed.
In some embodiments, the server 120 may also provide other services or software applications that may include non-virtual environments and virtual environments. In some embodiments, these services may be provided as web-based services or cloud services, for example, provided to users of client devices 101, 102, 103, 104, 105, and/or 106 under a software as a service (SaaS) model.
In the configuration shown in fig. 1, server 120 may include one or more components that implement the functions performed by server 120. These components may include software components, hardware components, or a combination thereof, which may be executed by one or more processors. A user operating a client device 101, 102, 103, 104, 105, and/or 106 may, in turn, utilize one or more client applications to interact with the server 120 to take advantage of the services provided by these components. It should be understood that a variety of different system configurations are possible, which may differ from system 100. Accordingly, fig. 1 is one example of a system for implementing the various methods described herein and is not intended to be limiting.
The user may use client devices 101, 102, 103, 104, 105, and/or 106 to perform the interface testing method. The client device may provide an interface that enables a user of the client device to interact with the client device. The client device may also output information to the user via the interface. Although fig. 1 depicts only six client devices, those skilled in the art will appreciate that any number of client devices may be supported by the present disclosure.
The server 120 may include one or more general purpose computers, special purpose server computers (e.g., PC (personal computer) servers, UNIX servers, mid-end servers), blade servers, mainframe computers, server clusters, or any other suitable arrangement and/or combination. The server 120 may include one or more virtual machines running a virtual operating system, or other computing architecture involving virtualization (e.g., one or more flexible pools of logical storage that may be virtualized to maintain virtual storage for the server). In various embodiments, the server 120 may run one or more services or software applications that provide the functionality described below.
The computing units in server 120 may run one or more operating systems including any of the operating systems described above, as well as any commercially available server operating systems. The server 120 may also run any of a variety of additional server applications and/or middle tier applications, including HTTP servers, FTP servers, CGI servers, JAVA servers, database servers, and the like.
In some implementations, the server 120 may include one or more applications to analyze and consolidate data feeds and/or event updates received from users of the client devices 101, 102, 103, 104, 105, and 106. Server 120 may also include one or more applications to display data feeds and/or real-time events via one or more display devices of client devices 101, 102, 103, 104, 105, and 106.
In some embodiments, the server 120 may be a server of a distributed system, or a server incorporating a blockchain. The server 120 may also be a cloud server, or a smart cloud computing server or a smart cloud host with artificial intelligence technology. The cloud Server is a host product in a cloud computing service system, and is used for solving the defects of high management difficulty and weak service expansibility in the traditional physical host and Virtual Private Server (VPS) service.
The system 100 may also include one or more databases 130. In some embodiments, these databases may be used to store data and other information. For example, one or more of the databases 130 may be used to store information such as audio files and video files. The database 130 may reside in various locations. For example, the database used by the server 120 may be local to the server 120, or may be remote from the server 120 and may communicate with the server 120 via a network-based or dedicated connection. The database 130 may be of different types. In certain embodiments, the database used by the server 120 may be, for example, a relational database. One or more of these databases may store, update, and retrieve data to and from the database in response to the command.
In some embodiments, one or more of the databases 130 may also be used by applications to store application data. The databases used by the application may be different types of databases, such as key-value stores, object stores, or conventional stores supported by a file system.
The system 100 of fig. 1 may be configured and operated in various ways to enable application of the various methods and apparatus described in accordance with the present disclosure.
Fig. 2 shows a flow diagram of an interface testing method according to an embodiment of the present disclosure. As shown in fig. 2, the interface testing method 200 includes: step S201, sending a user request to a server and determining a target interface corresponding to the user request; step S202, acquiring a response message aiming at the user request and information to be tested corresponding to the target interface from the server, wherein the information to be tested comprises first data, and the first data corresponds to a message main body of the response message; step S203, acquiring a target verification rule corresponding to the target interface, wherein the target verification rule comprises a first verification rule for verifying the first data; and step S204, checking the information to be tested based on the target checking rule.
Therefore, contract testing aiming at the interface is driven by data generated by actual operation of a user, the use requirement of the user is met, simultaneously, the information to be tested returned by the target interface is verified through the target verification rule corresponding to the target interface, the user experience is not influenced, meanwhile, the real-time monitoring and testing of the interface are realized, the defect that the user request needs to be simulated in the existing contract testing is overcome, and the scene coverage of the interface testing is more comprehensive.
According to some embodiments, step S203 comprises: acquiring an interface document of the target interface; defining the first verification rule based on the interface document; and determining the target verification rule based on the first verification rule.
It can be understood that, before the interface is tested, a target verification rule for verifying the information to be tested needs to be predefined, that is, before the interface is tested for a contract, a contract document needs to be predefined for determining whether the information to be tested meets expectations. For the first data corresponding to the message body of the response message in the to-be-tested information, which parameters the message body of the response message corresponding to the interface, that is, the response body of the interface, may have, and the types and value ranges of the parameters may be determined based on the interface document of the target interface, so that a first check rule for checking the first data is defined, and the check on the message body of the response message is realized based on the first check rule in the subsequent interface test, so as to determine the correctness of the response body returned by the server.
According to some embodiments, the information to be tested further includes second data, the second data corresponds to a message body of a request message corresponding to the user request, and step S203 further includes: defining a second check rule for checking the second data based on the interface document; and determining the target check rule based on the second check rule.
It can be understood that the second data corresponding to the message body of the request message corresponding to the user request is the request body. Similarly, the message body of the request message corresponding to the interface, that is, the request body of the interface, may have the parameters, and the types and value ranges of the parameters may be determined based on the interface document of the target interface, so as to ensure that the request sent by the user is reasonable. Therefore, a second check rule for checking the second data can be predefined, and the message body of the request message can be checked based on the second check rule in the subsequent interface test, so as to determine the correctness of the request body sent by the client.
According to some embodiments, the information to be tested further includes third data, the third data corresponds to a header of the response packet, and step S203 further includes: defining a third verification rule for verifying the third data based on the interface document; and determining the target verification rule based on the third verification rule.
It is understood that the third data corresponding to the header of the response packet is the response header. Similarly, the message header of the response packet corresponding to the interface, that is, which parameters the response header of the interface may have, the type and value range of the parameters, and the like may be determined based on the interface document of the target interface, so that a third check rule for checking third data may be predefined, and the message header of the response packet is checked based on the third check rule in a subsequent interface test to determine the correctness of the response header sent by the server.
According to some embodiments, the information to be tested further includes fourth data, where the fourth data corresponds to a header of a request packet corresponding to the user request, and step S203 further includes: defining a fourth verification rule for verifying the fourth data based on the interface document; and determining the target verification rule based on the fourth verification rule.
It is understood that the fourth data corresponding to the header of the request message corresponding to the user request is the request header. Similarly, it may be determined, based on the interface document of the target interface, which parameters may be included in a header of the request packet corresponding to the interface, that is, the request header of the interface, and the type and value range of the parameters, so as to ensure that the source of the request is legal. Therefore, a fourth check rule for checking fourth data can be predefined, and the check of the message header of the request message is realized in a subsequent interface test based on the fourth check rule, so as to determine the correctness of the request header sent by the client.
It can be seen from the above embodiments that, before testing the interface, a response body, a request body, a response head, and a first verification rule, a second verification rule, a third verification rule, and a fourth verification rule corresponding to the request head for verifying the interface may be defined in advance according to respective interface documents of a plurality of interfaces to be tested, and in response to a user request, the verification rules of the interface corresponding to the user request are matched, thereby implementing a full coverage test on data passing through the interface and monitoring of the plurality of interfaces to be tested.
According to some embodiments, the information to be tested comprises data in a key-value format, the key corresponds to a parameter to be verified, and the target verification rule is configured to verify a relationship between the key and the value based on the key. Because the data to be tested are in a preset format of key-value, the target verification rule can determine whether the relation between the key and the value is in accordance with expectation or whether an illegal parameter to be tested exists or not based on the parameter to be tested represented by the key, and the like, so that the preset verification rule can support contract testing of interfaces with various data structures in key-value types.
According to some embodiments, the target verification rule comprises at least one of the following verification types: regular check, value check and type check. As the target verification rule is defined in advance according to the interface document, various types of verification can be defined according to actual requirements, and different verification requirements can be met.
According to some embodiments, the method further comprises: acquiring a verification result of the information to be tested and generating a verification report; and rendering and displaying the verification report. For example, if a field of the interface is detected in the interface testing process, a verification report may be generated based on abnormal data in the information to be tested, and the verification report may be rendered and displayed, so as to implement an abnormal prompt for the user.
According to another aspect of the present disclosure, an interface testing method is provided. Fig. 3 shows a flow chart of an interface testing method according to an embodiment of the present disclosure. As shown in fig. 3, the interface testing method 300 includes: step S301, responding to a user request received from a client, and acquiring a target interface and a response message corresponding to the user request; step S302, determining information to be tested corresponding to the target interface based on the user request and the response message, wherein the information to be tested comprises first data, and the first data corresponds to a message main body of the response message; and step S303, sending the response message and the information to be tested to the client.
The server side can drive contract test aiming at the interface through data generated by actual operation of a user, and after receiving a request message corresponding to a user request, the server acquires a corresponding target interface and a response message, determines to-be-tested information corresponding to the target interface, and sends the response message and the to-be-tested information back to the client. In one example, the format of the information to be tested may be json. Therefore, the server provides the information to be tested for the interface test for the test of the target interface while meeting the use requirement of the user. Therefore, real-time monitoring and testing of the interface are realized without influencing user experience, the defect that a user request needs to be simulated in the existing contract testing is overcome, and the scene of the interface testing is more comprehensive.
According to some embodiments, step S302 comprises: generating a log file in a key-value format based on the user request and the response message, wherein the key corresponds to a parameter to be checked; and analyzing the log file to determine the information to be tested corresponding to the target interface.
Illustratively, the log file may be obtained by using a modification of an engine x (nginx) service. In one example, the nginx service may be used to record a request message and a response message corresponding to a user request, and copy and modify the request message and the response message to generate a log file in a key-value format, where the key-value format may enable a check rule to determine whether a relationship between a key and a value is expected or whether an illegal parameter to be tested exists based on a parameter to be tested represented by the key in an interface test of a client, so that the preconfigured check rule may support contract tests in which multiple data structures are interfaces of key-value types. In one example, a log file may be parsed with a python script to determine information to be tested corresponding to the target interface.
According to another aspect of the present disclosure, an interface testing apparatus is provided. As shown in fig. 4, the interface test apparatus 400 includes: a sending module 401 configured to send a user request to a server and determine a target interface corresponding to the user request; a first obtaining module 402, configured to obtain, from the server, a response packet for the user request and information to be tested corresponding to the target interface, where the information to be tested includes first data, and the first data corresponds to a packet body of the response packet; a second obtaining module 403, configured to obtain a target verification rule corresponding to the target interface, where the target verification rule includes a first verification rule for verifying the first data; and a verification module 404 configured to verify the information to be tested based on the target verification rule.
The operations of the modules 401 and 404 of the interface testing apparatus 400 are similar to the operations of the steps S201 to S204 described above, and are not described herein again.
Therefore, contract testing for the interface is driven through data generated by actual operation of a user, the checking module 404 checks the information to be tested returned through the target interface through the target checking rule corresponding to the target interface while the use requirement of the user is met, real-time monitoring and testing of the interface are achieved while user experience is not influenced, the defect that user requests need to be simulated in the existing contract testing is overcome, and the scene coverage of the interface testing is more comprehensive.
According to some embodiments, the second obtaining module 403 comprises: an acquisition unit configured to acquire an interface document of the target interface; a first defining unit configured to define the first verification rule based on the interface document; and a first determination unit configured to determine the target verification rule based on the first verification rule.
It should be understood that before the interface testing apparatus 400 tests the interface, a target verification rule for verifying the information to be tested needs to be predefined, that is, before the interface is subjected to the contract test, a contract document needs to be predefined for determining whether the information to be tested meets the expectation. For the first data corresponding to the message body of the response message in the to-be-tested information, the first defining unit may determine, based on the interface document of the target interface, which parameters the message body of the response message corresponding to the interface, that is, the response body of the interface may have, and the type and value range of the parameters, so as to define a first check rule for checking the first data, and in a subsequent interface test, the checking module 404 checks the message body of the response message based on the first check rule, so as to determine the correctness of the response body returned by the server.
According to some embodiments, the information to be tested further includes second data, where the second data corresponds to a message body of a request message corresponding to the user request, and the second obtaining module 403 further includes: a second defining unit configured to define a second check rule for checking the second data based on the interface document; and a second determination unit configured to determine the target verification rule based on the second verification rule.
It can be understood that the second data corresponding to the message body of the request message corresponding to the user request is the request body. Similarly, the second defining unit may determine, based on the interface document of the target interface, which parameters the message body of the request message corresponding to the interface, that is, the request body of the interface may have, and the types and value ranges of the parameters, so as to ensure that the request sent by the user is reasonable. Therefore, a second check rule for checking the second data may be predefined, and the check module 404 checks the message body of the request message based on the second check rule in the subsequent interface test, so as to determine the correctness of the request body sent by the client.
According to some embodiments, the information to be tested further includes third data, where the third data corresponds to a header of the response packet, and the second obtaining module 403 further includes: a third defining unit configured to define a third verification rule for verifying the third data based on the interface document; and a third determination unit configured to determine the target verification rule based on the third verification rule.
It is understood that the third data corresponding to the header of the response packet is the response header. Similarly, the third defining unit may determine, based on the interface document of the target interface, which parameters the message header of the response packet corresponding to the interface, that is, the response header of the interface may have, and the type and value range of the parameters, so that a third check rule for checking the third data may be predefined, and in a subsequent interface test, the check module 404 implements, based on the third check rule, the check on the message header of the response packet, so as to determine the correctness of the response header sent by the server.
According to some embodiments, the information to be tested further includes fourth data, where the fourth data corresponds to a header of a request packet corresponding to the user request, and the second obtaining module 403 further includes: a fourth defining unit configured to define a fourth verification rule for verifying the fourth data based on the interface document; and a fourth determination unit configured to determine the target verification rule based on the fourth verification rule.
It is understood that the fourth data corresponding to the header of the request message corresponding to the user request is the request header. Similarly, the fourth defining unit may determine, based on the interface document of the target interface, which parameters the header of the request packet corresponding to the interface, that is, the request header of the interface may have, and the type and value range of the parameters, so as to ensure that the source of the request is legal. Therefore, a fourth check rule for checking the fourth data may be predefined, and the check module 404 checks the header of the request packet based on the fourth check rule in the subsequent interface test, so as to determine the correctness of the request header sent by the client.
As can be seen from the foregoing embodiments, before testing the interface, the second obtaining module 403 may respectively define, according to the interface documents of the plurality of interfaces to be tested, a response body, a request body, a response head, and a first verification rule, a second verification rule, a third verification rule, and a fourth verification rule corresponding to the request head, which are used for verifying the interface, in advance, and in response to a user request, match the verification rule of the interface corresponding to the user request, thereby implementing a full coverage test on the data passing through the interface and monitoring the plurality of interfaces to be tested.
According to some embodiments, the information to be tested comprises data in a key-value format, the key corresponds to a parameter to be verified, and the target verification rule is configured to verify a relationship between the key and the value based on the key. Because the data to be tested are in a preset format of key-value, the target verification rule can determine whether the relation between the key and the value is in accordance with expectation or whether an illegal parameter to be tested exists or not based on the parameter to be tested represented by the key, and the like, so that the preset verification rule can support contract testing of interfaces with various data structures in key-value types.
According to some embodiments, the target verification rule comprises at least one of the following verification types: regular check, value check and type check. As the target verification rule is defined in advance according to the interface document, various types of verification can be defined according to actual requirements, and different verification requirements are met.
According to another aspect of the present disclosure, an interface testing apparatus is provided. Fig. 5 shows a block diagram of an interface test apparatus according to an embodiment of the present disclosure. As shown in fig. 5, the interface test apparatus 500 includes: an obtaining module 501, configured to, in response to receiving a user request from a client, obtain a target interface and a response packet corresponding to the user request; a determining module 502 configured to determine to-be-tested information corresponding to the target interface based on the user request and the response message, wherein the to-be-tested information includes first data, and the first data corresponds to a message body of the response message; and a sending module 503 configured to send the response packet and the information to be tested to the client.
The contract test for the interface can be driven by data generated by the actual operation of the user. After receiving a request message corresponding to a user request, the obtaining module 501 obtains a corresponding target interface and a response message, determines information to be tested corresponding to the target interface, and sends the response message and the information to be tested back to the client. In one example, the format of the information to be tested may be json. Therefore, the server provides the information to be tested for the interface test for the test of the target interface while meeting the use requirement of the user. Therefore, real-time monitoring and testing of the interface are realized without influencing user experience, the defect that a user request needs to be simulated in the existing contract testing is overcome, and the scene of the interface testing is more comprehensive.
The operations of the modules 501-503 of the interface testing apparatus 500 are similar to the operations of the steps S301-S303 described above, and are not described herein again.
According to some embodiments, the generating module 502 comprises: a generating unit configured to generate a log file in a key-value format based on the user request and the response message, wherein the key corresponds to a parameter to be verified; and the analysis unit is configured to analyze the log file so as to determine the information to be tested corresponding to the target interface.
For example, the generating unit may obtain the log file by using a modification to an engine x (nginx) service. In one example, the nginx service may be used to record a request message and a response message corresponding to a user request, and copy and modify the request message and the response message to generate a log file in a key-value format, where the key-value format may enable a check rule to determine whether a relationship between a key and a value is expected or whether an illegal parameter to be tested exists based on a parameter to be tested represented by the key in an interface test of a client, so that the preconfigured check rule may support contract tests in which multiple data structures are interfaces of key-value types. In one example, the parsing unit may parse the log file using a python script to determine information to be tested corresponding to the target interface.
As shown in fig. 6, the electronic device 600 includes a computing unit 601, which can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM)602 or a computer program loaded from a storage unit 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 600 can also be stored. The calculation unit 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
Various components in the electronic device 600 are connected to the I/O interface 605, including: an input unit 606, an output unit 607, a storage unit 608, and a communication unit 609. The input unit 606 may be any type of device capable of inputting information to the electronic device 600, and the input unit 606 may receive input numeric or character information and generate key signal inputs related to user settings and/or function controls of the electronic device, and may include, but is not limited to, a mouse, a keyboard, a touch screen, a track pad, a track ball, a mouse, a keyboard, a touch pad, a mouse, a keyboard, a touch pad, a trackball, a touch pad, a touch,A joystick, a microphone, and/or a remote control. Output unit 607 may be any type of device capable of presenting information and may include, but is not limited to, a display, speakers, a video/audio output terminal, a vibrator, and/or a printer. The storage unit 608 may include, but is not limited to, a magnetic disk, an optical disk. The communication unit 609 allows the electronic device 600 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunications networks, and may include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication transceiver, and/or a chipset, such as bluetoothTMDevices, 802.11 devices, WiFi devices, WiMax devices, cellular communication devices, and/or the like.
The computing unit 601 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of the computing unit 601 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The calculation unit 601 performs the respective methods and processes described above, such as the interface test method. For example, in some embodiments, the interface test method may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 608. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 600 via the ROM 602 and/or the communication unit 609. When the computer program is loaded into RAM 603 and executed by the computing unit 601, one or more steps of the interface testing method described above may be performed. Alternatively, in other embodiments, the computing unit 601 may be configured to perform the interface test method in any other suitable manner (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.
The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server with a combined blockchain.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be performed in parallel, sequentially or in different orders, and are not limited herein as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved.
Although embodiments or examples of the present disclosure have been described with reference to the accompanying drawings, it is to be understood that the above-described methods, systems and apparatus are merely exemplary embodiments or examples and that the scope of the present invention is not limited by these embodiments or examples, but only by the claims as issued and their equivalents. Various elements in the embodiments or examples may be omitted or may be replaced with equivalents thereof. Further, the steps may be performed in an order different from that described in the present disclosure. Further, various elements in the embodiments or examples may be combined in various ways. It is important that as technology evolves, many of the elements described herein may be replaced with equivalent elements that appear after the present disclosure.
Claims (21)
1. An interface testing method, comprising:
sending a user request to a server and determining a target interface corresponding to the user request;
acquiring a response message aiming at the user request and information to be tested corresponding to the target interface from the server, wherein the information to be tested comprises first data, and the first data corresponds to a message main body of the response message;
acquiring a target verification rule corresponding to the target interface, wherein the target verification rule comprises a first verification rule used for verifying the first data; and
and verifying the information to be tested based on the target verification rule.
2. The method of claim 1, wherein the obtaining a target verification rule corresponding to the target interface comprises:
acquiring an interface document of the target interface;
defining the first verification rule based on the interface document; and
and determining the target check rule based on the first check rule.
3. The method of claim 2, wherein the information to be tested further comprises second data corresponding to a message body of a request message corresponding to the user request, and wherein,
the obtaining of the target verification rule corresponding to the target interface further includes:
defining a second check rule for checking the second data based on the interface document; and
determining the target check rule based on the second check rule.
4. The method of claim 2 or 3, wherein the information to be tested further comprises third data, the third data corresponding to a header of the response message, and wherein,
the obtaining of the target verification rule corresponding to the target interface further includes:
defining a third verification rule for verifying the third data based on the interface document; and
and determining the target check rule based on the third check rule.
5. The method of any of claims 2-4, wherein the information to be tested further comprises fourth data corresponding to a header of a request message corresponding to the user request, and wherein,
the obtaining of the target verification rule corresponding to the target interface further includes:
defining a fourth verification rule for verifying the fourth data based on the interface document; and
and determining the target verification rule based on the fourth verification rule.
6. The method of claims 1-5, wherein the information to be tested comprises data in a key-value format, the key corresponding to a parameter to be verified, and the target verification rule is used to verify a relationship between the key and the value based on the key.
7. The method of any of claims 1-6, wherein the target validation rule comprises at least one of the following validation types:
regular check, value check and type check.
8. An interface testing method, comprising:
in response to receiving a user request from a client, acquiring a target interface and a response message corresponding to the user request;
determining information to be tested corresponding to the target interface based on the user request and the response message, wherein the information to be tested comprises first data, and the first data corresponds to a message body of the response message; and
and sending the response message and the information to be tested to the client.
9. The method of claim 8, wherein said determining information to be tested corresponding to said target interface based on said user request and said response message comprises;
generating a log file in a key-value format based on the user request and the response message, wherein the key corresponds to a parameter to be checked; and
and analyzing the log file to determine the information to be tested corresponding to the target interface.
10. An interface test apparatus comprising:
a sending module configured to send a user request to a server and determine a target interface corresponding to the user request;
a first obtaining module configured to obtain, from the server, a response packet for the user request and information to be tested corresponding to the target interface, where the information to be tested includes first data, and the first data corresponds to a packet body of the response packet;
a second obtaining module configured to obtain a target verification rule corresponding to the target interface, where the target verification rule includes a first verification rule for verifying the first data; and
and the checking module is configured to check the information to be tested based on the target checking rule.
11. The apparatus of claim 10, wherein the second obtaining means comprises:
an acquisition unit configured to acquire an interface document of the target interface;
a first defining unit configured to define the first verification rule based on the interface document; and
a first determination unit configured to determine the target verification rule based on the first verification rule.
12. The apparatus of claim 11, wherein the information to be tested further comprises second data corresponding to a message body of a request message corresponding to the user request, and wherein the second obtaining module further comprises:
a second defining unit configured to define a second check rule for checking the second data based on the interface document; and
a second determination unit configured to determine the target verification rule based on the second verification rule.
13. The apparatus according to claim 11 or 12, wherein the information to be tested further includes third data, the third data corresponding to a header of the response packet, and wherein the second obtaining module further includes:
a third defining unit configured to define a third verification rule for verifying the third data based on the interface document; and
a third determination unit configured to determine the target verification rule based on the third verification rule.
14. The apparatus of any of claims 11-13, wherein the information to be tested further comprises fourth data corresponding to a message header of a request message corresponding to the user request, and wherein the second obtaining module further comprises:
a fourth defining unit configured to define a fourth verification rule for verifying the fourth data based on the interface document; and
a fourth determination unit configured to determine the target verification rule based on the fourth verification rule.
15. The apparatus of any of claims 10-14, wherein the information to be tested comprises data in a key-value format, the key corresponding to a parameter to be verified, and the target verification rule is configured to verify a relationship between the key and the value based on the key.
16. The apparatus of any of claims 10-15, wherein the target validation rule comprises at least one of the following validation types:
regular check, value check and type check.
17. An interface test apparatus comprising:
the system comprises an acquisition module, a processing module and a display module, wherein the acquisition module is configured to respond to a user request received from a client and acquire a target interface and a response message corresponding to the user request;
a determining module configured to determine to-be-tested information corresponding to the target interface based on the user request and the response message, wherein the to-be-tested information includes first data, and the first data corresponds to a message body of the response message; and
and the sending module is configured to send the response message and the information to be tested to the client.
18. The apparatus of claim 17, wherein the means for determining comprises:
a generating unit configured to generate a log file in a key-value format based on the user request and the response packet, wherein the key corresponds to a parameter to be verified; and
the analysis unit is configured to analyze the log file to determine information to be tested corresponding to the target interface.
19. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein
The memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-9.
20. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-9.
21. A computer program product comprising a computer program, wherein the computer program realizes the method of any one of claims 1-9 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210287904.1A CN114666258B (en) | 2022-03-22 | 2022-03-22 | Interface testing method, device, electronic equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210287904.1A CN114666258B (en) | 2022-03-22 | 2022-03-22 | Interface testing method, device, electronic equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114666258A true CN114666258A (en) | 2022-06-24 |
| CN114666258B CN114666258B (en) | 2023-11-07 |
Family
ID=82030910
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210287904.1A Active CN114666258B (en) | 2022-03-22 | 2022-03-22 | Interface testing method, device, electronic equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114666258B (en) |
Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2013074873A1 (en) * | 2011-11-18 | 2013-05-23 | Amazon Technologies, Inc. | Virtual network interface objects |
| US20160232085A1 (en) * | 2015-02-10 | 2016-08-11 | Wipro Limited | Method and device for improving software performance testing |
| CN109298997A (en) * | 2018-08-08 | 2019-02-01 | 平安科技（深圳）有限公司 | Interface test method, system, computer equipment and storage medium |
| CN109783367A (en) * | 2018-12-15 | 2019-05-21 | 中国平安人寿保险股份有限公司 | Interface test method, device, computer installation and storage medium |
| CN110750409A (en) * | 2018-07-23 | 2020-02-04 | 北京奇虎科技有限公司 | Method, device and system for realizing test |
| CN111045756A (en) * | 2019-12-10 | 2020-04-21 | 中国工商银行股份有限公司 | Method, apparatus, computing device, and medium for generating interface service |
| WO2020119434A1 (en) * | 2018-12-15 | 2020-06-18 | 深圳壹账通智能科技有限公司 | Method and apparatus for interface data processing, method and apparatus for automated testing, device, and medium |
| CN111478969A (en) * | 2020-04-09 | 2020-07-31 | 吉林亿联银行股份有限公司 | Interface checking method and device |
| CN112199279A (en) * | 2020-09-30 | 2021-01-08 | 北京一起教育信息咨询有限责任公司 | Full-link inspection method and device |
| US10901880B1 (en) * | 2019-09-18 | 2021-01-26 | Capital One Services, Llc | API monitoring and validation for onboarded applications |
| CN112269706A (en) * | 2020-11-16 | 2021-01-26 | 北京百度网讯科技有限公司 | Interface parameter checking method and device, electronic equipment and computer readable medium |
| CN112671605A (en) * | 2020-12-16 | 2021-04-16 | 建信金融科技有限责任公司 | Test method and device and electronic equipment |
| CN113032244A (en) * | 2021-02-23 | 2021-06-25 | 中国工商银行股份有限公司 | Interface testing method, device, computer system and computer readable storage medium |
| US20210240600A1 (en) * | 2020-01-31 | 2021-08-05 | Salesforce.Com, Inc. | Test suite generation from metadata |
| CN113282476A (en) * | 2021-06-24 | 2021-08-20 | 深圳市商汤科技有限公司 | Interface performance testing method and device and electronic equipment |
| CN113297078A (en) * | 2021-05-24 | 2021-08-24 | 平安壹钱包电子商务有限公司 | MOCK system and data testing method based on MOCK system |
| CN113778725A (en) * | 2020-06-03 | 2021-12-10 | 北京沃东天骏信息技术有限公司 | Data verification method and device |
| CN114003506A (en) * | 2021-11-10 | 2022-02-01 | 广州易方信息科技股份有限公司 | Interface testing and monitoring method based on log recording |
| CN114003497A (en) * | 2021-11-01 | 2022-02-01 | 北京百度网讯科技有限公司 | Method, device and equipment for testing service system and storage medium |
-
2022
- 2022-03-22 CN CN202210287904.1A patent/CN114666258B/en active Active
Patent Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2013074873A1 (en) * | 2011-11-18 | 2013-05-23 | Amazon Technologies, Inc. | Virtual network interface objects |
| US20160232085A1 (en) * | 2015-02-10 | 2016-08-11 | Wipro Limited | Method and device for improving software performance testing |
| CN110750409A (en) * | 2018-07-23 | 2020-02-04 | 北京奇虎科技有限公司 | Method, device and system for realizing test |
| CN109298997A (en) * | 2018-08-08 | 2019-02-01 | 平安科技（深圳）有限公司 | Interface test method, system, computer equipment and storage medium |
| CN109783367A (en) * | 2018-12-15 | 2019-05-21 | 中国平安人寿保险股份有限公司 | Interface test method, device, computer installation and storage medium |
| WO2020119434A1 (en) * | 2018-12-15 | 2020-06-18 | 深圳壹账通智能科技有限公司 | Method and apparatus for interface data processing, method and apparatus for automated testing, device, and medium |
| US10901880B1 (en) * | 2019-09-18 | 2021-01-26 | Capital One Services, Llc | API monitoring and validation for onboarded applications |
| CN111045756A (en) * | 2019-12-10 | 2020-04-21 | 中国工商银行股份有限公司 | Method, apparatus, computing device, and medium for generating interface service |
| US20210240600A1 (en) * | 2020-01-31 | 2021-08-05 | Salesforce.Com, Inc. | Test suite generation from metadata |
| CN111478969A (en) * | 2020-04-09 | 2020-07-31 | 吉林亿联银行股份有限公司 | Interface checking method and device |
| CN113778725A (en) * | 2020-06-03 | 2021-12-10 | 北京沃东天骏信息技术有限公司 | Data verification method and device |
| CN112199279A (en) * | 2020-09-30 | 2021-01-08 | 北京一起教育信息咨询有限责任公司 | Full-link inspection method and device |
| CN112269706A (en) * | 2020-11-16 | 2021-01-26 | 北京百度网讯科技有限公司 | Interface parameter checking method and device, electronic equipment and computer readable medium |
| CN112671605A (en) * | 2020-12-16 | 2021-04-16 | 建信金融科技有限责任公司 | Test method and device and electronic equipment |
| CN113032244A (en) * | 2021-02-23 | 2021-06-25 | 中国工商银行股份有限公司 | Interface testing method, device, computer system and computer readable storage medium |
| CN113297078A (en) * | 2021-05-24 | 2021-08-24 | 平安壹钱包电子商务有限公司 | MOCK system and data testing method based on MOCK system |
| CN113282476A (en) * | 2021-06-24 | 2021-08-20 | 深圳市商汤科技有限公司 | Interface performance testing method and device and electronic equipment |
| CN114003497A (en) * | 2021-11-01 | 2022-02-01 | 北京百度网讯科技有限公司 | Method, device and equipment for testing service system and storage medium |
| CN114003506A (en) * | 2021-11-10 | 2022-02-01 | 广州易方信息科技股份有限公司 | Interface testing and monitoring method based on log recording |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114666258B (en) | 2023-11-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108959068B (en) | Software interface testing method, device and storage medium | |
| US20170329696A1 (en) | Techniques for real time server testing in a production environment | |
| WO2023125851A1 (en) | Remote diagnostics method and apparatus, electronic device and storage medium | |
| KR102488582B1 (en) | Method and apparatus for verifying operation state of application | |
| CN114417780B (en) | State synchronization method and device, electronic equipment and storage medium | |
| CN113495843A (en) | Method and device for testing play-starting performance of video player | |
| WO2022100075A1 (en) | Method and apparatus for performance test, electronic device and computer-readable medium | |
| CN112860566A (en) | Applet detection method, device, electronic equipment and readable medium | |
| CN112732312A (en) | Method and device for updating application program, electronic equipment and medium | |
| CN114666258B (en) | Interface testing method, device, electronic equipment and medium | |
| CN115050396A (en) | Test method and device, electronic device and medium | |
| CN113596011B (en) | Flow identification method and device, computing device and medium | |
| US11954013B2 (en) | Method of testing applet performance, electronic device, and computer-readable medium | |
| CN111538656B (en) | Monitoring method, device and equipment for gradient inspection and storage medium | |
| CN114676062A (en) | Method and device for testing difference data of interface, electronic equipment and medium | |
| CN114003497A (en) | Method, device and equipment for testing service system and storage medium | |
| CN113568797B (en) | Testing method and device of intelligent interaction system, electronic equipment and medium | |
| CN114860836B (en) | Method, device, equipment and medium for mining failure interest points | |
| EP4195052A1 (en) | Systems and methods for validating a cloud-hosted application | |
| CN114398653B (en) | Data processing method, device, electronic equipment and medium | |
| US20230111874A1 (en) | Device emulations in a notebook session | |
| CN116610405A (en) | Method and device for controlling page state and electronic equipment | |
| CN113836021A (en) | Test method, test device, electronic apparatus, and medium | |
| CN114238149A (en) | Batch testing method of accounting system, electronic device and storage medium | |
| CN114511694A (en) | Image recognition method, image recognition device, electronic equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |