CN112732548B - Interface testing method and device - Google Patents
Interface testing method and device Download PDFInfo
- Publication number
- CN112732548B CN112732548B CN201910975010.XA CN201910975010A CN112732548B CN 112732548 B CN112732548 B CN 112732548B CN 201910975010 A CN201910975010 A CN 201910975010A CN 112732548 B CN112732548 B CN 112732548B
- Authority
- CN
- China
- Prior art keywords
- request
- parameter
- interface
- parameters
- tested
- 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.)
- Active
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 211
- 230000004044 response Effects 0.000 claims abstract description 196
- 238000000034 method Methods 0.000 claims description 33
- 230000001360 synchronised effect Effects 0.000 claims description 29
- 230000000903 blocking effect Effects 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims 1
- 238000001514 detection method Methods 0.000 description 17
- 230000008569 process Effects 0.000 description 15
- 230000006870 function Effects 0.000 description 12
- 238000004891 communication Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 238000010998 test method Methods 0.000 description 5
- 230000000977 initiatory effect Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 238000000605 extraction Methods 0.000 description 3
- 230000001133 acceleration Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000005484 gravity Effects 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 230000005236 sound signal Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000010897 surface acoustic wave method Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention discloses an interface testing method and device, wherein the interface testing method comprises the following steps: obtaining a test request, wherein the test request comprises an interface to be tested, a request parameter of the interface to be tested and a predicted response parameter corresponding to the request parameter, testing the interface to be tested through the request parameter to obtain a real response parameter corresponding to the request parameter, generating a parameter updating instruction corresponding to the request parameter of the interface to be tested according to the real response parameter and the predicted response parameter, and updating the request parameter based on the parameter updating instruction to obtain the updated request parameter. Therefore, the problem of missing connection of the existing interface can be solved, and the accuracy of the test interface can be improved.
Description
Technical Field
The invention relates to the technical field of computers, in particular to an interface testing method and device.
Background
With the development of technology, the architecture of a service system is more and more complex, and various problems may exist in the process of executing the service, so that the service system is generally tested.
However, when testing a programming interface, the response parameters are usually scanned by manually setting data, so that the accuracy of the existing method for testing the interface is low, and the problem of missed detection exists.
Disclosure of Invention
The embodiment of the invention provides an interface testing method and device, which can solve the problem of missing connection of the existing interface, thereby improving the accuracy of the tested interface.
The embodiment of the invention provides an interface testing method, which comprises the following steps:
acquiring a test request, wherein the test request comprises an interface to be tested, a request parameter of the interface to be tested and a predicted response parameter corresponding to the request parameter;
testing the interface to be tested through the request parameters to obtain real response parameters corresponding to the request parameters;
generating a parameter updating instruction corresponding to the request parameter of the interface to be tested according to the real response parameter and the predicted response parameter;
and updating the request parameters based on the parameter updating instruction to obtain updated request parameters.
Correspondingly, the embodiment of the invention also provides an interface testing device, which comprises:
the test system comprises an acquisition module, a test module and a test module, wherein the acquisition module is used for acquiring a test request, and the test request comprises an interface to be tested, a request parameter of the interface to be tested and a predicted response parameter corresponding to the request parameter;
The test module is used for testing the interface to be tested through the request parameters to obtain real response parameters corresponding to the request parameters;
the generating module is used for generating a parameter updating instruction corresponding to the request parameter of the interface to be tested according to the real response parameter and the predicted response parameter;
and the updating module is used for updating the request parameters based on the parameter updating instruction to obtain updated request parameters.
Optionally, in some embodiments of the present invention, the generating module is specifically configured to:
and comparing the real response parameter with the predicted response parameter, and generating a parameter updating instruction corresponding to the request parameter of the interface to be tested based on the comparison result.
Optionally, in some embodiments of the present invention, the generating module includes:
a first extracting unit configured to extract a range of the real response parameter and a range of the predicted response parameter;
the comparison unit is used for comparing the range of the real response parameter with the range of the predicted response parameter;
and the first generation unit is used for generating a parameter updating instruction corresponding to the request parameter of the interface to be tested when the end point of the range of the real response parameter is different from the end point of the range of the predicted response parameter.
Optionally, in some embodiments of the present invention, the updating module includes:
a second extraction unit configured to extract a range of the request parameter;
the updating unit is used for updating the range of the request parameter based on the parameter updating instruction to obtain an updated range;
and the second generation unit is used for generating updated request parameters based on the request parameters and the updated range.
Optionally, in some embodiments of the present invention, the updating unit is specifically configured to:
and adjusting a value point in a preset interval in the range of the request parameter based on the parameter updating instruction to obtain an updated request parameter range interval.
Optionally, in some embodiments of the present invention, the updating unit is specifically configured to:
and adjusting the end points of the request parameter range based on the parameter updating instruction to obtain an updated request parameter range interval.
Optionally, in some embodiments of the present invention, the update module is specifically configured to:
synchronizing the range of the request parameters according to the updated range to obtain synchronized request parameters;
testing the interface to be tested through the synchronized request parameters to obtain real response parameters corresponding to the synchronized request parameters;
And returning to execute the step of testing the interface to be tested through the synchronized request parameters until the real response parameters corresponding to the synchronized request parameters are consistent with the predicted response parameters, and obtaining updated request parameters.
Optionally, in some embodiments of the present invention, the method further includes a detection module, where the detection module is configured to:
detecting whether the same request parameters exist in the interface to be detected within preset time;
when the same request parameters exist in the interface to be tested, updating a preset blocking instruction, and returning to execute the step of acquiring the test request, wherein the blocking instruction is used for blocking the test request with the same request parameters as the current test request in a preset time period in the future.
Optionally, in some embodiments of the present invention, the method further includes a determining module, where the determining module is configured to:
when a plurality of test requests exist in the interface to be tested, extracting a time stamp corresponding to each test request;
determining a test request to be processed currently based on a preset strategy and a time stamp corresponding to each request parameter;
the test module is specifically used for: and testing the interface to be tested through the request parameters of the test request to be processed currently, and obtaining the real response parameters corresponding to the request parameters to be processed currently.
After a test request is obtained, the test request comprises a to-be-tested interface, a request parameter of the to-be-tested interface and a predicted response parameter corresponding to the request parameter, the to-be-tested interface is tested through the request parameter to obtain a real response parameter corresponding to the request parameter, then a parameter updating instruction corresponding to the request parameter of the to-be-tested interface is generated according to the real response parameter and the predicted response parameter, and finally the request parameter is updated based on the parameter updating instruction to obtain an updated request parameter. Therefore, the problem of missing connection of the existing interface can be solved, and the accuracy of the test interface can be improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1a is a schematic diagram of a scenario of an interface testing method according to an embodiment of the present invention;
FIG. 1b is a flowchart of an interface testing method according to an embodiment of the present invention;
FIG. 2 is a flow chart of an interface test method according to an embodiment of the invention
FIG. 3a is a schematic structural diagram of a first embodiment of an interface testing apparatus according to an embodiment of the present invention;
FIG. 3b is a schematic diagram of a second embodiment of an interface testing apparatus according to an embodiment of the present invention;
FIG. 3c is a schematic structural diagram of a third embodiment of an interface testing apparatus according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to fall within the scope of the invention.
First, terms mentioned in the embodiments of the present invention will be explained:
an interface, in the present embodiment, refers to an application program interface (Application Programming Interface, API) that is a predefined function or refers to a convention in which different components of a software system are joined, in order to provide an application program with the ability of a developer to access a set of routines based on certain software or hardware without having to access the native code or understand the details of the internal operating mechanism.
The embodiment of the invention provides an interface testing method and device.
The interface testing device may be integrated in a network device, such as a terminal or a server, where the terminal may include a mobile phone, a tablet computer, or a personal computer (PC, personal Computer), and the server may include a server that operates independently or a distributed server, or may include a server cluster that includes multiple servers.
Referring to fig. 1a, taking the interface testing device integrated in a terminal as an example, when an interface needs to be tested, a request may be tested first, where the test request may be sent by a user, where the test request may include a to-be-tested interface, a request parameter of the to-be-tested interface, and a predicted response parameter corresponding to the request parameter, the to-be-tested interface is tested through the request parameter to obtain a real response parameter corresponding to the request parameter, a parameter update instruction corresponding to the request parameter of the to-be-tested interface is generated according to the real response parameter and the predicted response parameter, and the request parameter is updated based on the parameter update instruction to obtain an updated request parameter.
The following will describe in detail. It should be noted that the following description order of embodiments is not a limitation of the priority order of embodiments.
An interface testing method, comprising: obtaining a test request, wherein the test request comprises an interface to be tested, a request parameter of the interface to be tested and a predicted response parameter corresponding to the request parameter, testing the interface to be tested through the request parameter to obtain a real response parameter corresponding to the request parameter, generating a parameter updating instruction corresponding to the request parameter of the interface to be tested according to the real response parameter and the predicted response parameter, and updating the request parameter based on the parameter updating instruction to obtain an updated request parameter.
Referring to fig. 1b, fig. 1b is a flow chart of an interface testing method according to an embodiment of the invention. The specific flow of the interface test method can be as follows:
101. a test request is obtained.
The test request may specifically include an interface to be tested, a request parameter of the interface to be tested, and a predicted response parameter corresponding to the request parameter, where a source of the test request may be initiated by a user, and a source of the test request is various, for example, the test request may be a network address, an identity identifier, geographic location information of a client of the client initiating the test request, or may also be user account information, user identity information, etc. of a user initiating the test request for logging in the client.
The method for obtaining the test request may also be various, for example, the test request initiated by the user may be received through a wireless network, the test request initiated by the user may also be received through a communication medium, for example, the test request sent by the user may be received through a network cable, a usb disk, an optical disk, or the like.
It should be noted that, the predicted response parameter corresponding to the request parameter may be preset, for example, when the request parameter is a in the acquired test request, the predicted corresponding parameter corresponding to the request parameter a may be preset to be A1, or may be other, specifically set according to the actual situation, which is not described herein.
102. And testing the interface to be tested through the request parameters to obtain the real response parameters corresponding to the request parameters.
Here, the interface test is a test for testing an interface between components of the system. Interface testing is mainly used for detecting interaction points between external systems and between internal subsystems. The key point of the test is to check the exchange, transmission and control management process of data, the mutual logic dependency relationship among systems and the like, and when the request parameter passes through the interface to be tested, the interface to be tested can generate the real response parameter corresponding to the request parameter based on the request parameter.
In the following, a concept needs to be introduced, reentry refers to multiple requests of the same parameter, that is, there are at least two request parameters with the same parameter in the interface, and only one real response parameter, in order to improve the accuracy of the interface test, it is guaranteed that the real response parameter has and corresponds to one request parameter, so before the step of testing the interface to be tested through the request parameter to obtain the real response parameter corresponding to the request parameter, the method specifically further includes:
(11) Detecting whether the same request parameters exist in the interface to be tested within a preset time;
(12) When the same request parameters exist in the interface to be tested, updating a preset blocking instruction, and returning to the step of executing the acquisition test request, wherein the blocking instruction is used for blocking the test request with the same request parameters as the current test request in a preset time period in the future.
When the same request parameters exist in the interfaces to be tested, the preset blocking instruction can be determined to not block the test requests with the same request parameters as the current test requests in a preset time period in the future, so that the situation can be prevented by updating the preset blocking instruction in the database, and when the same request parameters do not exist in the interfaces to be tested in the preset time, the interfaces to be tested can be tested through the request parameters, and the real response parameters corresponding to the request parameters can be obtained.
It should be further noted that, when there are multiple test requests in the interface, the interface processes which request, and the current test request to be processed can be determined through a preset policy, that is, in some embodiments, before step "test the interface to be tested through the request parameters to obtain the real response parameters corresponding to the request parameters", the method specifically further includes:
(21) When a plurality of test requests exist in the interface to be tested, extracting a time stamp corresponding to each test request;
(22) Determining a test request to be processed currently based on a preset strategy and a time stamp corresponding to each request parameter;
the step of testing the interface to be tested through the request parameters to obtain the real response parameters corresponding to the request parameters may specifically include: and testing the interface to be tested through the request parameters of the test request to be processed currently, and obtaining the real response parameters corresponding to the request parameters to be processed currently.
For example, specifically, when 3 test requests exist in the interface to be tested, the 3 test requests include a test request a1, a test request a2 and a test request a3, a timestamp corresponding to each test request is extracted, and when a difference value between the timestamp of the test request a1 and the timestamp of the test request a2, a difference value between the timestamp of the test request a1 and the timestamp of the test request a3 and a difference value between the timestamp of the test request a2 and the timestamp of the test request a3 are the same, the 3 test requests can be considered to exist in the interface to be tested simultaneously within a preset time, so that the 3 test requests can be processed based on a preset policy, for example, the test request a2 and the test request a3 can be locked, and at this time, the test request a1 is the test request to be processed currently; in addition, when the error between the time stamps of the 3 test requests is smaller than a preset value, the 3 test requests can be considered to exist in the interface to be tested at the same time within a preset time, and the preset value can be preset, and is specific according to actual conditions.
103. And generating a parameter updating instruction corresponding to the request parameter of the interface to be tested according to the real response parameter and the predicted response parameter.
Specifically, an error between the real response parameter and the predicted corresponding parameter may be calculated, and a parameter update instruction corresponding to the request parameter of the interface to be tested is generated according to the error, that is, in some embodiments, the step of generating, according to the real response parameter and the predicted response parameter, a parameter update instruction corresponding to the request parameter of the interface to be tested may specifically include: and comparing the response parameters with the predicted response parameters, and generating a parameter updating instruction corresponding to the request parameters of the interface to be tested based on the comparison result.
For example, the predicted response parameter value corresponding to the request parameter is 100, the corresponding real response parameter value corresponding to the request parameter is 65, the error between the real response parameter value and the predicted response parameter value is 35, and a parameter update instruction may be generated based on this error, for example, the parameter update instruction indicates to increase the request parameter value.
For another example, the range of the real response parameter may be compared with the range of the predicted response parameter, and when the range of the response parameter is inconsistent with the range of the predicted response parameter, a parameter update instruction corresponding to the request parameter of the interface to be tested is generated, that is, in some embodiments, the step of comparing the response parameter with the predicted response parameter, and generating, based on the comparison result, the parameter update instruction corresponding to the request parameter of the interface to be tested may specifically include:
(31) Extracting a range of real response parameters and a range of predicted response parameters;
(32) Comparing the range of the real response parameter with the range of the predicted response parameter;
(33) And when the end points of the range of the real response parameters are different from the end points of the range of the predicted response parameters, generating a parameter updating instruction corresponding to the request parameters of the interface to be tested.
It should be noted that, in the embodiment of the present invention, only when the end point of the range of the real response parameter is the same as the end point of the range of the predicted response parameter, the range of the real response parameter is considered to be identical to the range of the predicted response parameter, for example, the range of the predicted response parameter is greater than or equal to 1 and less than or equal to 100, and the range of the real response parameter is greater than or equal to 1 and less than or equal to 100, and at this time, the range of the real response parameter is identical to the range of the predicted response parameter; if the range of the predicted response parameter is greater than or equal to 1 and less than or equal to 100, and the range of the real response parameter is greater than 1 and less than 100, the range of the real response parameter is inconsistent with the range of the predicted response parameter, that is, the end point of the range of the real response parameter is not identical with the end point of the range of the predicted response parameter, and at this time, a parameter update instruction corresponding to the request parameter of the interface to be tested is generated.
104. And updating the request parameters based on the parameter updating instruction to obtain updated request parameters.
When the request parameter is a specific character, such as english or chinese, then each character in the request parameter is traversed based on the parameter update instruction, so as to update the request parameter, for example, when the request parameter is "afdeg", the "a", "f", "d", "e" and "g" are updated based on the parameter update instruction, so as to obtain the updated request parameter.
Alternatively, the range of the request parameter may be updated according to the parameter update instruction, for example, when the range of the request parameter is (1, 100), that is, a range greater than 1 and less than 100, the range of the request parameter may be enlarged to (1, 500) based on the parameter update instruction, or the range may be reduced to (1, 50) based on the parameter update instruction, that is, in some embodiments, the step of "updating the request parameter based on the parameter update instruction to obtain an updated request parameter" may specifically include:
(41) Extracting a range of request parameters;
(42) Updating the range of the request parameter based on the parameter updating instruction to obtain an updated range;
(43) Based on the request parameters and the updated scope, updated request parameters are generated.
In addition, the value point in the preset interval in the range of the request parameter may be adjusted according to the parameter update instruction, when the range of the request parameter is (1, 100), the value point in the interval may be adjusted (40, 60), for example, all the value points in the interval are removed (40, 50), the updated range of the request parameter is greater than 1 and less than or equal to 40, and greater than or equal to 50 and less than 100, if the range of the request parameter is only a problem in some intervals, and the actual response parameter is not equal to the predicted response parameter, then the efficiency of the interface test may be improved by adjusting the value point in the preset interval, that is, in some embodiments, the step of updating the range of the request parameter based on the parameter update instruction to obtain the updated range may specifically include: and adjusting a value point in a preset interval in the range of the request parameter based on the parameter updating instruction to obtain an updated range interval of the request parameter. The preset interval can be adjusted according to actual requirements.
Of course, the end point of the range of the request parameter may also be adjusted according to the parameter update instruction, that is, in some embodiments, the step of updating the range of the request parameter based on the parameter update instruction to obtain an updated range may specifically include: and adjusting the end points of the range of the request parameters based on the parameter updating instruction to obtain an updated range section of the request parameters.
The adjustment mode may be to expand the value of a certain endpoint or reduce the value of a certain endpoint, which is specifically determined according to the actual situation and will not be described herein.
It should be noted that, in the actual test, one adjustment often cannot obtain the request parameter that the user finally wants, so the request parameter may be continuously adjusted by the updated actual response parameter corresponding to the request parameter and the predicted response parameter corresponding to the request parameter, that is, in some embodiments, the step of generating the updated request parameter "based on the request parameter and the updated range" may specifically include:
(51) Synchronizing the range of the request parameters according to the updated range to obtain synchronized request parameters;
(52) Testing the interface to be tested through the synchronized request parameters to obtain real response parameters corresponding to the synchronized request parameters;
(53) And returning to execute the step of testing the interface to be tested through the synchronized request parameters until the real response parameters corresponding to the synchronized request parameters are consistent with the predicted response parameters, and obtaining updated request parameters.
For example, taking the range of the request parameter as (1, 100), the range of the predicted response parameter corresponding to the request parameter is (1, 1000), and the interface to be tested is tested by the request parameter to obtain the range of the real response parameter corresponding to the request parameter as (3, 460), then the updated range of the request parameter can be obtained according to the range of the real response parameter and the range of the predicted response parameter, then the range of the request parameter is synchronized according to the updated range to obtain the synchronized request parameter, at this time, the range of the synchronized request parameter is (5, 150), then the interface to be tested is tested by the synchronized request parameter to obtain the real response parameter corresponding to the synchronized request parameter, for example, the range of the real response parameter corresponding to the synchronized request parameter is (9, 560), and the range of the real response parameter corresponding to the predicted response parameter is different from the range of the predicted response parameter.
After a test request is acquired, the test request comprises a to-be-tested interface, a request parameter of the to-be-tested interface and a predicted response parameter corresponding to the request parameter, the to-be-tested interface is tested through the request parameter to obtain a real response parameter corresponding to the request parameter, then a parameter updating instruction corresponding to the request parameter of the to-be-tested interface is generated according to the real response parameter and the predicted response parameter, and finally the request parameter is updated based on the parameter updating instruction to obtain the updated request parameter. Compared with the existing interface test scheme, the interface test method of the embodiment of the invention does not need to scan response parameters by manually setting data, but adjusts the request parameters according to real response parameters and predicted response parameters, so that the problem of missed detection of the existing interface can be solved, and the accuracy of the test interface can be improved.
The method according to the embodiment will be described in further detail by way of example.
In this embodiment, an example will be described in which the interface wiping apparatus is specifically integrated in a terminal.
Referring to fig. 2, a specific flow of the data detection method may be as follows:
201. The terminal obtains the test request.
For example, the terminal may receive a test request initiated by a user through a wireless network, or the terminal may also receive a test request initiated by a user through a communication medium, for example, the terminal may receive a test request sent by a user through a network cable, a usb disk, an optical disk, or the like.
202. And the terminal tests the interface to be tested through the request parameters to obtain the real response parameters corresponding to the request parameters.
Optionally, in some embodiments, the terminal may detect whether the same request parameter exists in the interface to be tested within a preset time, when the same request parameter exists in the interface to be tested, the terminal updates a preset blocking instruction, and returns to execute the step of obtaining the test request, where the blocking instruction is used to block the test request having the same request parameter as the current test request within a preset time period in the future, and it needs to be described that after the terminal updates the preset blocking instruction, the terminal tests the interface to be tested still through the same request parameter, so as to obtain the real response parameter corresponding to the request parameter.
In addition, when the terminal detects that a plurality of test requests exist in the interface to be tested, the terminal can determine the test request to be processed currently based on a preset strategy and a timestamp corresponding to each request parameter, for example, the terminal can lock part of the test requests so as to determine the test request to be processed currently, and it should be noted that in the embodiment of the invention, the locking of the test request can be considered as a necessary condition of a database lock table and a database lock table: (1) mutually exclusive conditions: refers to the exclusive use of an allocated resource by a process, i.e., a resource is occupied by only one process for a period of time. If other processes request the resource at this time, the requester can only wait until the process occupying the resource is released after use. (2) request and hold conditions: meaning that a process has maintained at least one resource but has made a new resource request that has been held by other processes, the requesting process blocks but remains unremoved to other resources that it has acquired. (3) no deprivation conditions: refers to the resources that a process has acquired, cannot be deprived before it is used up, and can only be released by itself when it is used up. (4) loop wait condition: meaning that when a deadlock occurs, there must be a process-a circular chain of resources, i.e. a set of processes P0, P0 in P1, P2, & Pn is waiting for a resource occupied by P1; p1 is waiting for the resources occupied by P2, … …, pn is waiting for the resources already occupied by P0.
203. And the terminal generates a parameter updating instruction corresponding to the request parameter of the interface to be tested according to the real response parameter and the predicted response parameter.
For example, the terminal may compare the range of the real response parameter with the range of the predicted response parameter, and generate a parameter update instruction corresponding to the request parameter of the interface to be tested when the range of the real response parameter is inconsistent with the range of the predicted response parameter, which is specifically referred to the previous embodiment and will not be described herein.
204. And the terminal updates the request parameters based on the parameter updating instruction to obtain updated request parameters.
The terminal can traverse each value in the request parameters based on the parameter updating instruction to update the request parameters and obtain updated request parameters; or, the terminal may update the range of the request parameter according to the parameter update instruction. The updating of the range of the request parameter by the terminal according to the parameter updating instruction may include two modes.
The first way is: the terminal can adjust the value point in the preset interval in the range of the request parameter according to the parameter updating instruction, so that the updated request parameter is obtained;
the second way is: the terminal can adjust the end point of the range of the request parameter according to the parameter updating instruction, so that the updated request parameter is obtained;
The method specifically may be configured according to actual situations, and the terminal updates the request parameters based on the parameter update instruction, so that the updated request parameters refer to the foregoing embodiments, which are not described herein again.
As can be seen from the foregoing, after the terminal in the embodiment of the present invention obtains the test request, the test request includes the interface to be tested, the request parameter of the interface to be tested, and the predicted response parameter corresponding to the request parameter, the terminal tests the interface to be tested through the request parameter to obtain the real response parameter corresponding to the request parameter, then the terminal generates the parameter update instruction corresponding to the request parameter of the interface to be tested according to the real response parameter and the predicted response parameter, and finally, the terminal updates the request parameter based on the parameter update instruction to obtain the updated request parameter. Compared with the existing interface test scheme, the terminal of the embodiment of the invention does not need to scan response parameters by manually setting data, but adjusts the request parameters according to the real response parameters and the predicted response parameters, so that the problem of missed detection of the existing interface can be solved, and the accuracy of the test interface can be improved.
In order to facilitate better implementation of the interface testing method according to the embodiment of the present invention, the embodiment of the present invention further provides an interface testing device (abbreviated as testing device) based on the foregoing embodiment of the present invention. The meaning of the nouns is the same as that in the interface testing method, and specific implementation details can refer to the description in the method embodiment.
Referring to fig. 3a, fig. 3a is a schematic structural diagram of a data detection device according to an embodiment of the present invention, where the processing device may include an acquisition module 301, a test module 302, a generation module 303, and an update module 304, and may specifically be as follows:
the obtaining module 301 is configured to obtain a test request.
The test request may specifically include an interface to be tested, a request parameter of the interface to be tested, and a predicted response parameter corresponding to the request parameter, where a source of the test request may be initiated by a user, and a source of the test request is various, for example, the test request may be a network address, an identity identifier, geographic location information of a client of the client initiating the test request, or may also be user account information, user identity information, etc. of a user initiating the test request for logging in the client.
For example, the acquiring module 301 may receive a test request initiated by a user through a wireless network, or may receive a test request initiated by a user through a communication medium, for example, a test request sent by a user through a network cable, a usb disk, an optical disk, or the like.
And the test module 302 is configured to test the interface to be tested through the request parameter, so as to obtain a real response parameter corresponding to the request parameter.
Optionally, in some embodiments of the present invention, referring to fig. 3b, the apparatus further includes a detection module 305, where the detection module 305 may specifically be configured to: detecting whether the same request parameters exist in the interface to be tested within the preset time, updating the preset blocking instruction when the same request parameters exist in the interface to be tested, and returning to the step of executing the acquisition test request. The blocking instruction is used for blocking the test request with the same request parameters as the current test request in a preset time period in the future.
When the same request parameters exist in the interface to be tested, the detection module 305 may determine that the preset blocking instruction cannot block the test request with the same request parameters as the current test request within the preset time period in the future, so that the occurrence of the situation can be prevented by updating the preset blocking instruction in the database, and when the same request parameters are not detected in the interface to be tested within the preset time period, the interface to be tested can be tested by the request parameters, so as to obtain the real response parameters corresponding to the request parameters
Optionally, in some embodiments of the present invention, please refer to fig. 3c, further comprising a determining module 306, where the determining module 306 may specifically be configured to: when a plurality of test requests exist in the interface to be tested, extracting a time stamp corresponding to each test request, and determining the test request to be processed currently based on a preset strategy and the time stamp corresponding to each request parameter.
The test module 302 may be specifically configured to: and testing the interface to be tested through the request parameters of the test request to be processed currently, and obtaining the real response parameters corresponding to the request parameters to be processed currently.
The generating module 303 is configured to generate a parameter update instruction corresponding to the request parameter of the interface to be tested according to the real response parameter and the predicted response parameter.
For example, the generating module 303 may compare the range of the real response parameter with the range of the predicted response parameter, and when the range of the response parameter is inconsistent with the range of the predicted response parameter, generate a parameter update instruction corresponding to the request parameter of the interface to be tested, that is, in some embodiments, the generating module may be specifically configured to: and comparing the response parameters with the predicted response parameters, and generating a parameter updating instruction corresponding to the request parameters of the interface to be tested based on the comparison result.
Alternatively, in some embodiments of the present invention, the generating module 303 may include:
a first extraction unit for extracting a range of real response parameters and a range of predicted response parameters;
the comparison unit is used for comparing the range of the real response parameter with the range of the predicted response parameter;
the first generating unit is used for generating a parameter updating instruction corresponding to the request parameter of the interface to be tested when the end point of the range of the real response parameter is different from the end point of the range of the predicted response parameter.
The updating module 304 is configured to update the request parameter based on the parameter updating instruction, and obtain an updated request parameter.
The update module 304 may update the range of requested parameters according to the parameter update instructions, i.e., in some embodiments, the update module 304 may specifically include:
a second extraction unit for extracting a range of the request parameter;
the updating unit is used for updating the range of the request parameter based on the parameter updating instruction to obtain an updated range;
and the second generation unit is used for generating updated request parameters based on the request parameters and the updated range.
Optionally, in some embodiments of the present invention, the updating unit may specifically be configured to: and adjusting a value point in a preset interval in the range of the request parameter based on the parameter updating instruction to obtain an updated range interval of the request parameter.
Optionally, in some embodiments of the present invention, the updating unit may specifically be configured to: and adjusting the end points of the range of the request parameters based on the parameter updating instruction to obtain an updated range section of the request parameters.
Optionally, in some embodiments of the present invention, the update module may specifically be configured to: and synchronizing the range of the request parameters according to the updated range to obtain synchronized request parameters, testing the interface to be tested through the synchronized request parameters to obtain real response parameters corresponding to the synchronized request parameters, and returning to the step of executing the test on the interface to be tested through the synchronized request parameters until the real response parameters corresponding to the synchronized request parameters are consistent with the predicted response parameters to obtain updated request parameters.
It can be seen that, after the obtaining module 301 in the interface detecting device of the present embodiment obtains the test request, the test request includes the interface to be tested, the request parameter of the interface to be tested, and the predicted response parameter corresponding to the request parameter, the test module 302 tests the interface to be tested through the request parameter to obtain the real response parameter corresponding to the request parameter, then the generating module 303 generates the parameter update instruction corresponding to the request parameter of the interface to be tested according to the real response parameter and the predicted response parameter, and finally the updating module 304 updates the request parameter based on the parameter update instruction to obtain the updated request parameter. Compared with the existing interface test scheme, the interface test method of the embodiment of the invention does not need to scan response parameters by manually setting data, but adjusts the request parameters according to real response parameters and predicted response parameters, so that the problem of missed detection of the existing interface can be solved, and the accuracy of the test interface can be improved.
Correspondingly, the embodiment of the present invention further provides a terminal, as shown in fig. 4, where the terminal may include a Radio Frequency (RF) circuit 401, a memory 402 including one or more computer readable storage media, an input unit 403, a display unit 404, a sensor 405, an audio circuit 406, a wireless fidelity (WiFi, wireless Fidelity) module 407, a processor 408 including one or more processing cores, and a power supply 409. It will be appreciated by those skilled in the art that the terminal structure shown in fig. 4 is not limiting of the terminal and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components. Wherein:
the RF circuit 401 may be used for receiving and transmitting signals during the process of receiving and transmitting information or communication, in particular, after receiving downlink information of a base station, the downlink information is processed by one or more processors 408; in addition, data relating to uplink is transmitted to the base station. Typically, RF circuitry 401 includes, but is not limited to, an antenna, at least one amplifier, a tuner, one or more oscillators, a subscriber identity module (SIM, subscriber Identity Module) card, a transceiver, a coupler, a low noise amplifier (LNA, low Noise Amplifier), a duplexer, and the like. In addition, the RF circuitry 401 may also communicate with networks and other devices through wireless communications. The wireless communication may use any communication standard or protocol including, but not limited to, global system for mobile communications (GSM, global System of Mobile communication), general packet radio service (GPRS, general Packet Radio Service), code division multiple access (CDMA, code Division Multiple Access), wideband code division multiple access (WCDMA, wideband Code Division Multiple Access), long term evolution (LTE, long Term Evolution), email, short message service (SMS, short Messaging Service), and the like.
The memory 402 may be used to store software programs and modules, and the processor 408 may execute various functional applications and data processing by executing the software programs and modules stored in the memory 402. The memory 402 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like; the storage data area may store data (such as audio data, phonebook, etc.) created according to the use of the terminal, etc. In addition, memory 402 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 402 may also include a memory controller to provide access to the memory 402 by the processor 408 and the input unit 403.
The input unit 403 may be used to receive input numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control. In particular, in one particular embodiment, input unit 403 may include a touch-sensitive surface, as well as other input devices. The touch-sensitive surface, also referred to as a touch display screen or a touch pad, may collect touch operations thereon or thereabout by a user (e.g., operations thereon or thereabout by a user using any suitable object or accessory such as a finger, stylus, etc.), and actuate the corresponding connection means according to a predetermined program. Alternatively, the touch-sensitive surface may comprise two parts, a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device and converts it into touch point coordinates, which are then sent to the processor 408, and can receive commands from the processor 408 and execute them. In addition, touch sensitive surfaces may be implemented in a variety of types, such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch-sensitive surface, the input unit 403 may also comprise other input devices. In particular, other input devices may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, mouse, joystick, etc.
The display unit 404 may be used to display information input by a user or information provided to the user and various graphical user interfaces of the terminal, which may be composed of graphics, text, icons, video and any combination thereof. The display unit 404 may include a display panel, which may be optionally configured in the form of a liquid crystal display (LCD, liquid Crystal Display), an Organic Light-Emitting Diode (OLED), or the like. Further, the touch-sensitive surface may overlay a display panel, and upon detection of a touch operation thereon or thereabout, the touch-sensitive surface is communicated to the processor 408 to determine a type of touch event, and the processor 408 then provides a corresponding visual output on the display panel based on the type of touch event. Although in fig. 4 the touch sensitive surface and the display panel are implemented as two separate components for input and output functions, in some embodiments the touch sensitive surface may be integrated with the display panel to implement the input and output functions.
The terminal may also include at least one sensor 405, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor that may adjust the brightness of the display panel according to the brightness of ambient light, and a proximity sensor that may turn off the display panel and/or backlight when the terminal moves to the ear. The gravity acceleration sensor can detect the acceleration in all directions (generally three axes), can detect the gravity and the direction when the mobile phone is stationary, can be used for identifying the gesture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration identification related functions (such as pedometer and knocking), and other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor and the like which are also configured by the terminal are not repeated herein.
Audio circuitry 406, speakers, and a microphone may provide an audio interface between the user and the terminal. The audio circuit 406 may transmit the received electrical signal after audio data conversion to a speaker, where the electrical signal is converted to a sound signal for output; on the other hand, the microphone converts the collected sound signals into electrical signals, which are received by the audio circuit 406 and converted into audio data, which are processed by the audio data output processor 408 for transmission to, for example, another terminal via the RF circuit 401, or which are output to the memory 402 for further processing. Audio circuitry 406 may also include an ear bud jack to provide communication of the peripheral ear bud with the terminal.
The WiFi belongs to a short-distance wireless transmission technology, and the terminal can help the user to send and receive e-mail, browse web pages, access streaming media and the like through the WiFi module 407, so that wireless broadband internet access is provided for the user. Although fig. 4 shows a WiFi module 407, it is understood that it does not belong to the essential constitution of the terminal, and can be omitted entirely as required within the scope of not changing the essence of the invention.
The processor 408 is a control center of the terminal, and connects various parts of the entire handset using various interfaces and lines, and performs various functions of the terminal and processes data by running or executing software programs and/or modules stored in the memory 402, and calling data stored in the memory 402, thereby performing overall monitoring of the handset. Optionally, the processor 408 may include one or more processing cores; preferably, the processor 408 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 408.
The terminal also includes a power supply 409 (e.g., a battery) for powering the various components, which may be logically connected to the processor 408 through a power management system that performs functions such as managing charge, discharge, and power consumption. The power supply 409 may also include one or more of any of a direct current or alternating current power supply, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.
Although not shown, the terminal may further include a camera, a bluetooth module, etc., which will not be described herein. In this embodiment, the processor 408 in the terminal loads executable files corresponding to the processes of one or more application programs into the memory 402 according to the following instructions, and the processor 408 executes the application programs stored in the memory 402, so as to implement various functions:
obtaining a test request, wherein the test request comprises an interface to be tested, a request parameter of the interface to be tested and a predicted response parameter corresponding to the request parameter, testing the interface to be tested through the request parameter to obtain a real response parameter corresponding to the request parameter, generating a parameter updating instruction corresponding to the request parameter of the interface to be tested according to the real response parameter and the predicted response parameter, and updating the request parameter based on the parameter updating instruction to obtain an updated request parameter.
After a test request is acquired, the test request comprises a to-be-tested interface, a request parameter of the to-be-tested interface and a predicted response parameter corresponding to the request parameter, the to-be-tested interface is tested through the request parameter to obtain a real response parameter corresponding to the request parameter, then a parameter updating instruction corresponding to the request parameter of the to-be-tested interface is generated according to the real response parameter and the predicted response parameter, and finally the request parameter is updated based on the parameter updating instruction to obtain the updated request parameter. Compared with the existing interface test scheme, the interface test method of the embodiment of the invention does not need to scan response parameters by manually setting data, but adjusts the request parameters according to real response parameters and predicted response parameters, so that the problem of missed detection of the existing interface can be solved, and the accuracy of the test interface can be improved.
Those of ordinary skill in the art will appreciate that all or a portion of the steps of the various methods of the above embodiments may be performed by instructions, or by instructions controlling associated hardware, which may be stored in a computer-readable storage medium and loaded and executed by a processor.
To this end, an embodiment of the present invention provides a storage medium having stored therein a plurality of instructions capable of being loaded by a processor to perform the steps of any of the interface testing methods provided by the embodiments of the present invention. For example, the instructions may perform the steps of:
obtaining a test request, wherein the test request comprises an interface to be tested, a request parameter of the interface to be tested and a predicted response parameter corresponding to the request parameter, testing the interface to be tested through the request parameter to obtain a real response parameter corresponding to the request parameter, generating a parameter updating instruction corresponding to the request parameter of the interface to be tested according to the real response parameter and the predicted response parameter, and updating the request parameter based on the parameter updating instruction to obtain an updated request parameter.
The specific implementation of each operation above may be referred to the previous embodiments, and will not be described herein.
Wherein the storage medium may include: read Only Memory (ROM), random access Memory (RAM, random Access Memory), magnetic or optical disk, and the like.
The instructions stored in the storage medium can execute the steps in any of the interface testing methods provided in the embodiments of the present invention, so that the beneficial effects that any of the interface testing methods provided in the embodiments of the present invention can be achieved are detailed in the previous embodiments, and are not repeated here.
The foregoing describes in detail a method, apparatus, terminal and storage medium for testing an interface provided by the embodiments of the present invention, and specific examples are applied to illustrate the principles and embodiments of the present invention, where the foregoing examples are only used to help understand the method and core idea of the present invention; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in light of the ideas of the present invention, the present description should not be construed as limiting the present invention.
Claims (10)
1. An interface testing method, comprising:
acquiring a test request, wherein the test request comprises an interface to be tested, a request parameter of the interface to be tested and a predicted response parameter corresponding to the request parameter;
testing the interface to be tested through the request parameters to obtain real response parameters corresponding to the request parameters;
generating a parameter updating instruction corresponding to the request parameter of the interface to be tested according to the error of the real response parameter and the predicted response parameter;
extracting the range of the request parameters;
updating the range of the request parameter based on the parameter updating instruction to obtain an updated range;
Synchronizing the range of the request parameters according to the updated range to obtain synchronized request parameters;
and testing the interface to be tested through the synchronized request parameters to obtain real response parameters corresponding to the synchronized request parameters until the real response parameters corresponding to the synchronized request parameters are consistent with the predicted response parameters, thereby obtaining updated request parameters.
2. The method according to claim 1, wherein the generating a parameter update instruction corresponding to the request parameter of the interface to be tested according to the error between the real response parameter and the predicted response parameter includes:
and comparing the response parameters with the predicted response parameters, and generating a parameter updating instruction corresponding to the request parameters of the interface to be tested based on the comparison result.
3. The method according to claim 2, wherein comparing the response parameter with the predicted response parameter, and generating a parameter update instruction corresponding to the request parameter of the interface to be tested based on the comparison result, includes:
extracting the range of the real response parameters and the range of the predicted response parameters;
comparing the range of the real response parameter with the range of the predicted response parameter;
And when the end points of the range of the real response parameters are different from the end points of the range of the predicted response parameters, generating a parameter updating instruction corresponding to the request parameters of the interface to be tested.
4. A method according to any one of claims 1 to 3, wherein updating the range of the requested parameter based on the parameter update instruction to obtain an updated range comprises:
and adjusting a value point in a preset interval in the range of the request parameter based on the parameter updating instruction to obtain an updated request parameter range interval.
5. The method of claim 4, wherein updating the range of the requested parameter based on the parameter update instruction results in an updated range, comprising:
and adjusting the end points of the request parameter range based on the parameter updating instruction to obtain an updated request parameter range interval.
6. The method according to claim 1, further comprising, before testing the interface to be tested by the request parameter to obtain a real response parameter corresponding to the request parameter:
detecting whether the same request parameters exist in the interface to be detected within preset time;
When the same request parameters exist in the interface to be tested, updating a preset blocking instruction, and returning to execute the step of acquiring the test request, wherein the blocking instruction is used for blocking the test request with the same request parameters as the current test request in a preset time period in the future.
7. The method according to claim 1, further comprising, before testing the interface to be tested by the request parameter to obtain a real response parameter corresponding to the request parameter:
when a plurality of test requests exist in the interface to be tested, extracting a time stamp corresponding to each test request;
determining a test request to be processed currently based on a preset strategy and a time stamp corresponding to each request parameter;
the step of testing the interface to be tested through the request parameters to obtain real response parameters corresponding to the request parameters comprises the following steps: and testing the interface to be tested through the request parameters of the test request to be processed currently, and obtaining the real response parameters corresponding to the request parameters to be processed currently.
8. An interface testing apparatus, comprising:
the test system comprises an acquisition module, a test module and a test module, wherein the acquisition module is used for acquiring a test request, and the test request comprises an interface to be tested, a request parameter of the interface to be tested and a predicted response parameter corresponding to the request parameter;
The test module is used for testing the interface to be tested through the request parameters to obtain real response parameters corresponding to the request parameters;
the generating module is used for generating a parameter updating instruction corresponding to the request parameter of the interface to be tested according to the error of the real response parameter and the predicted response parameter;
the updating module is used for extracting the range of the request parameters; updating the range of the request parameter based on the parameter updating instruction to obtain an updated range; synchronizing the range of the request parameters according to the updated range to obtain synchronized request parameters; and testing the interface to be tested through the synchronized request parameters to obtain real response parameters corresponding to the synchronized request parameters until the real response parameters corresponding to the synchronized request parameters are consistent with the predicted response parameters, thereby obtaining updated request parameters.
9. A terminal comprising a processor and a memory, the memory storing a computer program adapted to be loaded by the processor to perform the interface testing method of any of claims 1-7.
10. A computer readable storage medium storing a plurality of instructions adapted to be loaded by a processor to perform the interface testing method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910975010.XA CN112732548B (en) | 2019-10-14 | 2019-10-14 | Interface testing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910975010.XA CN112732548B (en) | 2019-10-14 | 2019-10-14 | Interface testing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112732548A CN112732548A (en) | 2021-04-30 |
| CN112732548B true CN112732548B (en) | 2024-01-26 |
Family
ID=75588680
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910975010.XA Active CN112732548B (en) | 2019-10-14 | 2019-10-14 | Interface testing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112732548B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116756054B (en) * | 2023-08-23 | 2023-10-24 | 北京集度科技有限公司 | Test method, test device, electronic equipment and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107577602A (en) * | 2017-08-25 | 2018-01-12 | 上海斐讯数据通信技术有限公司 | A kind of method of testing of APP interfaces, apparatus and system |
| CN108255730A (en) * | 2018-01-23 | 2018-07-06 | 平安普惠企业管理有限公司 | Software interface test approach, test equipment, storage medium and device |
| CN108268375A (en) * | 2018-01-12 | 2018-07-10 | 深圳壹账通智能科技有限公司 | Applied program testing method, device, computer equipment and storage medium |
| US20180285490A1 (en) * | 2017-03-31 | 2018-10-04 | Change Healthcare Holdings, Llc | Method, apparatus, and computer program product for simulating client and application interface integration |
| CN109446068A (en) * | 2018-09-26 | 2019-03-08 | 平安健康保险股份有限公司 | Interface test method, device, computer equipment and storage medium |
| CN109656817A (en) * | 2018-12-04 | 2019-04-19 | 北京马上慧科技术有限公司 | A kind of automation interface test device and equipment |
| CN109726128A (en) * | 2018-12-29 | 2019-05-07 | 亚信科技（中国）有限公司 | A kind of method for generating test case, device and server |
| CN109783359A (en) * | 2018-12-14 | 2019-05-21 | 深圳壹账通智能科技有限公司 | The method, apparatus and computer equipment that automatic detection interface effectively identifies |
-
2019
- 2019-10-14 CN CN201910975010.XA patent/CN112732548B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180285490A1 (en) * | 2017-03-31 | 2018-10-04 | Change Healthcare Holdings, Llc | Method, apparatus, and computer program product for simulating client and application interface integration |
| CN107577602A (en) * | 2017-08-25 | 2018-01-12 | 上海斐讯数据通信技术有限公司 | A kind of method of testing of APP interfaces, apparatus and system |
| CN108268375A (en) * | 2018-01-12 | 2018-07-10 | 深圳壹账通智能科技有限公司 | Applied program testing method, device, computer equipment and storage medium |
| CN108255730A (en) * | 2018-01-23 | 2018-07-06 | 平安普惠企业管理有限公司 | Software interface test approach, test equipment, storage medium and device |
| CN109446068A (en) * | 2018-09-26 | 2019-03-08 | 平安健康保险股份有限公司 | Interface test method, device, computer equipment and storage medium |
| CN109656817A (en) * | 2018-12-04 | 2019-04-19 | 北京马上慧科技术有限公司 | A kind of automation interface test device and equipment |
| CN109783359A (en) * | 2018-12-14 | 2019-05-21 | 深圳壹账通智能科技有限公司 | The method, apparatus and computer equipment that automatic detection interface effectively identifies |
| CN109726128A (en) * | 2018-12-29 | 2019-05-07 | 亚信科技（中国）有限公司 | A kind of method for generating test case, device and server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112732548A (en) | 2021-04-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10635449B2 (en) | Method and apparatus for running game client | |
| RU2660948C2 (en) | Message revoking method and apparatus thereof | |
| EP3525417A1 (en) | Data processing method, device, storage medium, electronic device and server | |
| WO2015090248A1 (en) | Server overload protection method and device | |
| EP3499786B1 (en) | Data synchronization method, apparatus, storage medium and electronic device | |
| CN107329901B (en) | Data packet capturing method, terminal, server and storage medium | |
| CN106874077B (en) | Process running method and device | |
| JP6492184B2 (en) | Method, device, and system for managing information recommendations | |
| WO2018077041A1 (en) | Method and apparatus for running application | |
| WO2014206138A1 (en) | Webpage data update method, apparatus and terminal device | |
| CN112749074B (en) | Test case recommending method and device | |
| CN109144596B (en) | Quick starting method, device, terminal, server and system | |
| WO2015062234A1 (en) | Mobile terminal resource processing method, device and apparatus | |
| CN107122036B (en) | Method and device for adjusting frequency of central processing unit | |
| CN112732548B (en) | Interface testing method and device | |
| CN107463395B (en) | Component calling method and device | |
| CN110196662B (en) | Method, device, terminal and storage medium for displaying synchronization state | |
| CN106817370B (en) | Method and device for transmitting network data | |
| US10057740B2 (en) | Methods and devices for processing mobile terminal resource | |
| CN107346347B (en) | Webpage table display method and device | |
| CN114189436B (en) | Multi-cluster configuration deployment method and device, electronic equipment and storage medium | |
| CN108280798B (en) | Method and device for rendering and displaying browser kernel | |
| CN106294025B (en) | Method and device for downloading terminal software | |
| CN117234137B (en) | MCU clock frequency switching circuit, MCU and electronic equipment | |
| CN110891304B (en) | gPS power consumption control method for mobile terminal |
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 |