CN111767229A - Performance test method, device and equipment - Google Patents
Performance test method, device and equipment Download PDFInfo
- Publication number
- CN111767229A CN111767229A CN202010615486.5A CN202010615486A CN111767229A CN 111767229 A CN111767229 A CN 111767229A CN 202010615486 A CN202010615486 A CN 202010615486A CN 111767229 A CN111767229 A CN 111767229A
- Authority
- CN
- China
- Prior art keywords
- test
- interface
- sampler
- metadata
- 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.)
- Pending
Links
Images
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/26—Functional testing
Abstract
The application provides a performance test method, a performance test device and performance test equipment, wherein the method comprises the following steps: s1, outputting interface information of the test scene; s2, receiving test metadata input by a user, wherein the test metadata comprises attribute information of an interface to be tested; and S3, testing the interface to be tested through a sampler in the terminal equipment according to the test metadata, wherein the sampler is a Jmeter sampler determined according to the gRPC protocol. According to the method, the performance of the gPC interface can be visually tested through interfacing, the testing method is simple, and the efficiency of performance testing of the gPC interface can be improved.
Description
Technical Field
The embodiment of the application relates to the technical field of software testing, in particular to a performance testing method, device and equipment.
Background
Google Remote Procedure Call (gRPC) is a high-performance open source software framework based on HTTP 2.0 transport layer protocol bearer issued by Google, and provides a method for configuring and managing network equipment, which supports multiple programming languages. Because of the open source framework, both communication parties can perform secondary development, so that the communication between the client and the server is more focused on the content of a business layer, the attention on the underlying communication is reduced, and in recent years, interfaces based on the gRPC protocol are widely applied.
However, on one hand, in the prior art, the performance test method for the gRPC interface is mostly completed by means of performance test tools such as GHZ, Locust and the like, and such tools all need to write corresponding codes, so that the operation is complex and the test efficiency is low. Meanwhile, the performance test of the existing gPC based on the Jmeter is completed by writing Java codes for each interface, and the problems of complex operation and low test efficiency exist.
Disclosure of Invention
The application provides a performance test method, a performance test device and performance test equipment, which can test the performance of a gPC interface visually through interfacing, have a simple test method and can improve the efficiency of performance test of the gPC interface.
In a first aspect, the present application provides a performance testing method, applied to a terminal device, the method including: s1, outputting interface information of the test scene; s2, receiving test metadata input by a user, wherein the test metadata comprises attribute information of an interface to be tested; and S3, testing the interface to be tested through a sampler in the terminal equipment according to the test metadata, wherein the sampler is a Jmeter sampler determined according to the gRPC protocol.
Optionally, the method further includes: and S4, outputting the test result.
Optionally, S1 specifically includes: s11, receiving a test instruction input by a user; s12, calling a task flow corresponding to the test scene according to the test instruction; and S13, determining and outputting the test information corresponding to the task flow.
Optionally, S3 specifically includes: s31, generating a gRPC request message for remote-calling Google according to the test metadata through a sampler in the terminal equipment, wherein the gRPC request message conforms to a gRPC format; s32, sending the gPC request message to a gPC server through a sampler; and S33, receiving the response result sent by the gRPC server through the sampler, and testing the interface to be tested according to the response result.
Optionally, S31 includes: s311, obtaining a class related to the interface to be tested from a preset file according to the test metadata through a sampler, and instantiating the class as an interface client, wherein the preset file comprises at least one of the following information: interface name, interface parameter or interface returned parameter; and S312, generating a gPRC request message according to the test metadata and the interface client through the sampler.
Optionally, S33 specifically includes: s331, converting the response result into an object numbered musical notation JSON format through a gRPC analysis module in the terminal equipment to obtain a converted response result; and S332, testing the interface to be tested according to the converted response result.
Optionally, the attribute information includes: an interface address and/or an interface name.
Optionally, the test metadata further includes at least one of the following data: method name, request parameters, or proto file path.
Optionally, S31 includes: s312, converting the test metadata into JSON format test metadata; and S322, generating a gPRC request message according to the JSON format test metadata through a sampler in the terminal equipment.
Optional S33, including: and S331, according to the converted response result, performing performance test on the interface which passes through the Jmeter in the terminal equipment to obtain a test result.
In a second aspect, the present application provides a performance testing apparatus, comprising:
the output module is used for outputting interface information of the test scene;
the receiving module is used for receiving test metadata input by a user, and the test metadata comprises attribute information of an interface to be tested;
and the test module is used for testing the interface to be tested through a sampler in the terminal equipment according to the test metadata, wherein the sampler is a Jmeter sampler determined according to the gPC protocol.
Optionally, the output module is further configured to output a test result.
Optionally, the output module is specifically configured to receive a test instruction input by a user; calling a task flow corresponding to the test scene according to the test instruction; and determining test information corresponding to the task flow and outputting the test information.
Optionally, the test module is specifically configured to generate a gRPC request message for remote google invocation according to the test metadata through a sampler in the terminal device, where the gRPC request message conforms to a gRPC format; sending the gPRC request message to a gPRC server through a sampler; and receiving a response result sent by the gPC server through the sampler, and testing the interface to be tested according to the response result.
Optionally, the testing module is specifically configured to obtain, by using the sampler, a class related to the interface to be tested from a preset file according to the test metadata, and instantiate the class as the interface client, where the preset file includes at least one of the following information: interface name, interface parameter or interface returned parameter; and generating a gPRC request message according to the test metadata and the interface client by the sampler.
Optionally, the test module is specifically configured to convert the response result into an object notation JSON format through a gRPC analysis module in the terminal device, so as to obtain a converted response result; and testing the interface to be tested according to the converted response result.
Optionally, the attribute information includes: an interface address and/or an interface name.
Optionally, the test metadata further includes at least one of the following data: method name, request parameters, or proto file path.
Optionally, the test module is specifically configured to convert the test metadata into test metadata in a JSON format; and generating a gPRC request message according to the JSON format test metadata through a sampler in the terminal equipment.
Optionally, the test module is specifically configured to perform a performance test on the interface through a meter in the terminal device according to the converted response result, so as to obtain a test result.
In a third aspect, the present application provides 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 the first aspect or the alternatives of the first aspect.
In a fourth aspect, the present application provides a computer-readable storage medium having stored thereon computer-executable instructions for implementing the method as described in the first aspect or the alternatives thereof when executed by a processor.
According to the performance testing method, the performance testing device and the performance testing equipment, the performance of the gPC interface is visually tested through interfacing by outputting the interface information of the testing scene, the testing method is simple, and the efficiency of performance testing of the gPC interface can be improved; receiving test metadata input by a user, wherein the test metadata comprises attribute information of an interface to be tested; according to the test metadata, the interface to be tested is tested through a sampler in the terminal equipment, the sampler is a Jmeter sampler determined according to a gPC protocol, so that the performance of the gPC interface can be tested, and the reliability of communication is guaranteed; the user can also be informed of the test result by outputting the test result.
Drawings
FIG. 1 is a schematic flow chart of a performance testing method provided herein;
FIG. 2 is a schematic diagram of an interactive interface of a terminal device provided in the present application;
FIG. 3 is a schematic flow chart of another performance testing method provided herein;
FIG. 4 is another schematic diagram of an interactive interface of a terminal device provided by the present application;
FIG. 5 is a further schematic diagram of a terminal device interface provided herein;
FIG. 6 is a schematic structural diagram of a performance testing apparatus provided in the present application;
fig. 7 is a schematic structural diagram of an electronic device provided in the present application.
With the foregoing drawings in mind, certain embodiments of the disclosure have been shown and described in more detail below. These drawings and written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the concepts of the disclosure to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
The gPC is a high-performance open source software framework based on HTTP 2.0 transport layer protocol bearer issued by Google, and provides a method for supporting multiple programming languages and configuring and managing network equipment. Because of the open source framework, both communication parties can perform secondary development, so that the communication between the client and the server is more focused on the content of a business layer, the attention on the underlying communication is reduced, and in recent years, interfaces based on the gRPC protocol are widely applied.
On one hand, however, in the prior art, a test method for the performance of the gRPC interface is mostly completed by means of performance test tools such as GHZ, Locust and the like, and such tools all need to write corresponding codes, so that the operation is complex and the test efficiency is low. Meanwhile, the performance test of the existing gPC based on the Jmeter is completed by writing Java codes for each interface, and the problems of complex operation and low test efficiency exist.
The meter sampler is a meter component for sending requests to the server and receiving response data of the server through different protocols. If a Jmeter sampler can send a request to a server and receive response data of the server through a gPC protocol, performance test of a gPC interface can be realized. Based on the above, the application provides a performance test method, which outputs interface information of a test scene through S1; s2, receiving test metadata input by a user, wherein the test metadata comprises attribute information of an interface to be tested; and S3, testing the interface to be tested through a sampler in the terminal equipment according to the test metadata, wherein the sampler is a Jmeter sampler determined according to the gRPC protocol, and the performance of interface communication based on the gRPC protocol is tested.
Please refer to the last comment of the inventor to make a term explanation on the test information, and consider whether to replace the expression
Please make a term explanation for the following words
Metadata: the data is also called intermediate data and relay data, and is data describing data, mainly information describing data attributes, and is used for supporting functions such as indicating storage locations, history data, resource searching, file recording and the like. Metadata is an electronic catalog, and in order to achieve the purpose of creating a catalog, the contents or features of data must be described and collected, so as to achieve the purpose of assisting data retrieval. Test metadata refers to metadata used for testing.
And (3) task flow: the task performs sequencing.
A sampler: a Jmeter component that sends requests to the server and receives response data of the server through different protocols.
Class (c): the method is the basis for realizing information encapsulation by object-oriented programming. A class is a user-defined type of reference data, also called a class type. Each class contains a description of the data and a set of functions that operate on the data or pass messages. Instances of classes are referred to as objects.
Fig. 1 is a schematic flowchart of a performance testing method provided in the present application, where the method is applied to a terminal device, and as shown in fig. 1, the method includes:
and S101, outputting interface information of the test scene.
The terminal device may output interface information of the test scenario through an interactive interface thereof, where the interface information of the test scenario may include an input box of data and the like. Controls to control the progress of the test, such as "start test", "stop test", etc., may also be included.
S102, receiving test metadata input by a user, wherein the test metadata comprises attribute information of an interface to be tested.
The terminal device may receive the test metadata input by the user through its interactive interface, e.g., a graphical user interface. Wherein the attribute information includes one or more of the following information: interface address, interface name, access name, and access name. Fig. 2 is a schematic view of an interactive interface of a terminal device provided in the present application, and as shown in fig. 2, a user may input an interface address to be tested, for example 001, through an input box corresponding to the interface address; the name of the interface to be tested, such as the gRPC interface 01, can also be input through an input box corresponding to the interface name.
And S103, testing the interface to be tested through a sampler in the terminal equipment according to the test metadata.
Wherein, the sampler is a Jmeter sampler determined according to the gRPC protocol.
The Jmeter sampler is used for sending requests to the server and receiving response data of the server through different protocols.
The sampler in the terminal equipment is a Jmeter sampler determined according to a gRPC protocol, namely the sampler sends a request to a server through the gRPC protocol and receives response data of the server.
According to the test metadata, the interface to be tested is tested through a sampler in the terminal equipment, namely: and the terminal equipment controls the sampler to send a request to the server and receive response data of the server through a to-be-tested interface corresponding to-be-tested attribute information corresponding to the metadata according to a gPC protocol. The performance of the interface to be tested is then determined by analyzing information about the sampler, such as the delay between the sampler sending a request to the server and receiving the server's response data.
According to the performance testing method, interface information of a testing scene is output; receiving test metadata input by a user, wherein the test metadata comprises attribute information of an interface to be tested; according to the test metadata, the interface to be tested is tested through a sampler in the terminal equipment, the sampler is a Jmeter sampler determined according to a gPC protocol, performance test can be conducted on the gPC interface, reliability of communication is guaranteed, performance of the gPC interface is tested visually through interfacing, the test method is simple, and efficiency of performance test of the gPC interface can be improved.
In order to enable the user to know the test result, the method may further include outputting the test result based on the above embodiment. Based on this, the present application provides another performance testing method, and fig. 3 is another schematic flow chart of the performance testing method provided in the present application, as shown in fig. 3, the method includes:
and S301, outputting interface information of the test scene.
Optionally, one possible implementation manner of outputting the interface information of the test scenario is as follows: receiving a test instruction input by a user; calling a task flow corresponding to the test scene according to the test instruction; and determining test information corresponding to the task flow and outputting the test information.
By the method, a user can actively control the output of the interface information of the test scene by inputting the test instruction.
The terminal equipment can receive the test instruction input by the user through the interactive interface of the terminal equipment, and can also receive the test instruction input by the user through the voice equipment of the terminal equipment. Fig. 4 is another schematic diagram of the terminal device interaction interface provided in the present application, and as shown in fig. 4, a user may input a test instruction by clicking an "interface performance test" control on the first page 401; after receiving the test instruction, the terminal device invokes a task flow of a corresponding interface test scenario, and determines and outputs test information corresponding to the task flow, for example, the interactive interface jumps from the first page 401 to the second page 402, as shown in fig. 4, the second page 402 includes an input frame of data, and controls a test process such as "start test", "stop test", and the like to obtain a control.
S302, receiving test metadata input by a user, wherein the test metadata comprises attribute information of an interface to be tested.
S302 is similar to S202, and the detailed description can refer to S202, which is not repeated herein.
Optionally, the test metadata further includes at least one of the following data: method name, request parameters, or proto file path. The method can more accurately select the interface to be tested.
And S303, testing the interface to be tested through a sampler in the terminal equipment according to the test metadata.
Wherein, the sampler is a Jmeter sampler determined according to the gRPC protocol.
Optionally, according to the test metadata, a possible implementation manner of testing the interface to be tested through a sampler in the terminal device is as follows: generating a gRPC request message for remote-calling Google according to the test metadata through a sampler in the terminal equipment, wherein the gRPC request message conforms to a gRPC format; sending the gPRC request message to a gPRC server through a sampler; and receiving a response result sent by the gPC server through the sampler, and testing the interface to be tested according to the response result.
By the method, the request message which accords with the gPC format can be sent to the server through the sampler, and the response result sent by the gPC server is received, so that the performance of the gPC interface can be tested.
Specifically, a possible implementation manner for generating a google remote invocation gRPC request message according to test metadata through a sampler in the terminal device is as follows: obtaining a class related to an interface to be tested from a preset file according to the test metadata through a sampler, and instantiating the class as an interface client, wherein the preset file comprises at least one of the following information: interface name, interface parameter or interface returned parameter; and generating a gPRC request message according to the test metadata and the interface client by the sampler.
The method manages the interface information in a unified way through the preset file, is convenient to query, and can improve the efficiency of data processing.
Specifically, a possible implementation manner of receiving a response result sent by the gRPC server through the sampler and testing the interface to be tested according to the response result is as follows: converting the response result into an object numbered musical notation JSON format through a gRPC analysis module in the terminal equipment to obtain a converted response result; and testing the interface to be tested according to the converted response result.
The method can improve the readability of data and the portability of programs by converting the response result into a JSON format.
Optionally, another possible implementation manner of generating a google remote invocation gRPC request message according to the test metadata by using a sampler in the terminal device is as follows: converting the test metadata into JSON format test metadata; and generating a gPRC request message according to the JSON format test metadata through a sampler in the terminal equipment.
The method can also improve the readability of the data and the portability of the program by converting the test metadata into the JSON format.
Optionally, another possible implementation manner that receives the response result sent by the gRPC server through the sampler and tests the interface to be tested according to the response result is as follows: and according to the converted response result, performing performance test on the interface through a meter in the terminal equipment to obtain a test result. Specifically, the interface may be subjected to performance test through policies such as result assertion and logic vacancy in the meter calling layer, so as to obtain a test result.
By the method, performance test can be performed on the gPC interface through the Jmeter, and the operation is simple.
And S304, outputting the test result.
The terminal equipment can output the test result through the interactive interface. FIG. 5 is a schematic diagram of an interface of a terminal device provided in the present application, wherein the terminal device can output "the interface test passes!through its interactive interface as shown in FIG. 5! "to inform the user of the test result, in order to make the readability of the display result higher, the output result may further include attribute information of the interface to be tested.
On the basis of the embodiment, the performance testing method provided by the application can enable a user to check the testing result in time by further outputting the testing result.
To avoid affecting the original meter functionality, an image user interface associated with a gRPC interface test, a meter sampler determined according to the gRPC protocol, a gRPC analysis module, and at least one of the following information: interface name, interface parameter or preset file of parameter returned by interface are compiled and packed into a complete Jmeter plug-in, thus realizing flexibility of gPC interface test and characteristic of no intrusion to Jmeter.
Fig. 6 is a schematic structural diagram of a performance testing apparatus provided in the present application, and as shown in fig. 6, the apparatus includes:
the output module 61 is used for outputting interface information of the test scene;
a receiving module 62, configured to receive test metadata input by a user, where the test metadata includes attribute information of an interface to be tested;
and the test module 63 is configured to test the interface to be tested through a sampler in the terminal device according to the test metadata, where the sampler is a meter sampler determined according to a gRPC protocol.
Optionally, the output module 61 is further configured to output a test result.
Optionally, the output module 61 is specifically configured to receive a test instruction input by a user; calling a task flow corresponding to the test scene according to the test instruction; and determining test information corresponding to the task flow and outputting the test information.
Optionally, the test module 63 is specifically configured to generate a gRPC request message for remote google invocation according to the test metadata through a sampler in the terminal device, where the gRPC request message conforms to a gRPC format; sending the gPRC request message to a gPRC server through a sampler; and receiving a response result sent by the gPC server through the sampler, and testing the interface to be tested according to the response result.
Optionally, the testing module 63 is specifically configured to obtain, by using the sampler, a class related to the interface to be tested from a preset file according to the test metadata, and instantiate the class as the interface client, where the preset file includes at least one of the following information: interface name, interface parameter or interface returned parameter; and generating a gPRC request message according to the test metadata and the interface client by the sampler.
Optionally, the test module 63 is specifically configured to convert the response result into an object notation JSON format through a gRPC analysis module in the terminal device, so as to obtain a converted response result; and testing the interface to be tested according to the converted response result.
Optionally, the attribute information includes: an interface address and/or an interface name.
Optionally, the test metadata further includes at least one of the following data: method name, request parameters, or proto file path.
Optionally, the test module 63 is specifically configured to convert the test metadata into test metadata in a JSON format; and generating a gPRC request message according to the JSON format test metadata through a sampler in the terminal equipment.
Optionally, the test module 63 is specifically configured to perform a performance test on the interface through a meter in the terminal device according to the converted response result, so as to obtain a test result.
The performance testing apparatus can execute the performance testing method, and the content and effect thereof can refer to the method embodiment section, which is not described again.
Fig. 7 is a schematic structural diagram of an electronic device provided in the present application, and as shown in fig. 7, the electronic device includes: a processor 71, a memory 72; the processor 71 is communicatively connected to the memory 72. The memory 72 is used to store computer programs. The processor 71 is adapted to call the computer program stored in the memory 12 to implement the method in the above-described method embodiment.
Optionally, the electronic device further comprises: a transceiver 73 for enabling communication with other devices.
The electronic device may execute the performance testing method, and the content and effect thereof may refer to the method embodiment section, which is not described herein again.
The application also provides a computer-readable storage medium, in which computer-executable instructions are stored, and the computer-executable instructions are executed by a processor to implement the performance testing method.
The content and effect of the performance testing method can be referred to in the embodiment of the method, which is not described herein again.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims. It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (13)
1. A performance testing method is applied to terminal equipment, and the method comprises the following steps:
s1, outputting interface information of the test scene;
s2, receiving test metadata input by a user, wherein the test metadata comprises attribute information of an interface to be tested;
and S3, testing the interface to be tested through a sampler in the terminal equipment according to the test metadata, wherein the sampler is a Jmeter sampler determined according to a gRPC protocol.
2. The method of claim 1, further comprising:
and S4, outputting the test result.
3. The method according to claim 1, wherein the S1 specifically includes:
s11, receiving a test instruction input by a user;
s12, calling a task flow corresponding to the test scene according to the test instruction;
and S13, determining and outputting the test information corresponding to the task flow.
4. The method according to claim 1, wherein the S3 specifically includes:
s31, generating a gRPC request message for remote-invoking Google according to the test metadata through a sampler in the terminal equipment, wherein the gRPC request message conforms to a gRPC format;
s32, sending the gPRC request message to a gPRC server through the sampler;
and S33, receiving the response result sent by the gPC server through the sampler, and testing the interface to be tested according to the response result.
5. The method according to claim 4, wherein the S31 includes:
s311, obtaining a class related to the interface to be tested from a preset file according to the test metadata through the sampler, and instantiating the class as an interface client, wherein the preset file comprises at least one of the following information: interface name, interface parameter or interface returned parameter;
and S312, generating the gPRC request message according to the test metadata and the interface client through the sampler.
6. The method according to claim 4 or 5, wherein the S33 specifically includes:
s331, converting the response result into an object numbered musical notation JSON format through a gRPC analysis module in the terminal equipment to obtain a converted response result;
s332, testing the interface to be tested according to the converted response result.
7. The method according to any one of claims 1-3, wherein the attribute information comprises: an interface address and/or an interface name.
8. The method of any of claims 1-3, wherein the test metadata further comprises at least one of: method name, request parameters, or proto file path.
9. The method according to claim 1, wherein the S31 includes:
s312, converting the test metadata into JSON format test metadata;
and S322, generating a gPRC request message according to the JSON format test metadata through a sampler in the terminal equipment.
10. The method according to claim 9, wherein the S33 includes:
and S331, according to the converted response result, performing performance test on the interface through a Jmeter in the terminal equipment to obtain a test result.
11. A performance testing device, comprising:
the output module is used for outputting interface information of the test scene;
the receiving module is used for receiving test metadata input by a user, and the test metadata comprises attribute information of an interface to be tested;
and the testing module is used for testing the interface to be tested through a sampler in the terminal equipment according to the testing metadata, wherein the sampler is a Jmeter sampler determined according to a gPC protocol.
12. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
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 to 10.
13. A computer-readable storage medium having computer-executable instructions stored thereon, which when executed by a processor, are configured to implement the method of any one of claims 1 to 10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010615486.5A CN111767229A (en) | 2020-06-30 | 2020-06-30 | Performance test method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010615486.5A CN111767229A (en) | 2020-06-30 | 2020-06-30 | Performance test method, device and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111767229A true CN111767229A (en) | 2020-10-13 |
Family
ID=72724188
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010615486.5A Pending CN111767229A (en) | 2020-06-30 | 2020-06-30 | Performance test method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111767229A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113254355A (en) * | 2021-07-06 | 2021-08-13 | 云账户技术(天津)有限公司 | GRPC interface testing method and device, electronic equipment and readable storage medium |
| CN113626322A (en) * | 2021-07-30 | 2021-11-09 | 北京达佳互联信息技术有限公司 | Interface test method, device, equipment and medium based on binary data communication |
| CN114238155A (en) * | 2022-02-25 | 2022-03-25 | 北京宇信科技集团股份有限公司 | Test method, test platform, test device, server and storage medium |
-
2020
- 2020-06-30 CN CN202010615486.5A patent/CN111767229A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113254355A (en) * | 2021-07-06 | 2021-08-13 | 云账户技术(天津)有限公司 | GRPC interface testing method and device, electronic equipment and readable storage medium |
| CN113626322A (en) * | 2021-07-30 | 2021-11-09 | 北京达佳互联信息技术有限公司 | Interface test method, device, equipment and medium based on binary data communication |
| CN114238155A (en) * | 2022-02-25 | 2022-03-25 | 北京宇信科技集团股份有限公司 | Test method, test platform, test device, server and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108574604B (en) | Test method and device | |
| CN111767229A (en) | Performance test method, device and equipment | |
| CN113987074A (en) | Distributed service full-link monitoring method and device, electronic equipment and storage medium | |
| CN110716853A (en) | Test script recording method, application program testing method and related device | |
| CN111026634A (en) | Interface automation test system, method, device and storage medium | |
| CN109582317B (en) | Method and apparatus for debugging hosted applications | |
| CN113900958A (en) | Test case script generation method, system, medium and electronic device | |
| CN110955600A (en) | Interface test method and device | |
| EP4300303A1 (en) | Animation resource information processing method and apparatus, device, medium and product | |
| CN112395027A (en) | Widget interface generation method and device, storage medium and electronic equipment | |
| WO2023284505A1 (en) | Method and apparatus for code-scanning payment | |
| CN112631590A (en) | Component library generation method and device, electronic equipment and computer readable medium | |
| US9736222B1 (en) | System, method, and computer program for automatically exposing application programming interfaces (APIS) associated with an application server to one or more client devices | |
| CN114443905A (en) | Interface document updating method and device, electronic equipment and readable storage medium | |
| CN113836014A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN110807535A (en) | Construction method and construction device of unified reservation platform and unified reservation platform system | |
| CN110489326B (en) | IDS-based HTTPAPI debugging method device, medium and equipment | |
| CN110689285A (en) | Test method, test device, electronic equipment and computer readable storage medium | |
| CN112988872A (en) | Interface document management method and device, storage medium and electronic equipment | |
| CN113704079A (en) | Interface testing method and device based on Protobuf | |
| CN111158661A (en) | System interface docking method, device, medium and electronic equipment | |
| CN111767486A (en) | Method, device, electronic equipment and computer readable medium for displaying page | |
| CN112306324B (en) | Information processing method, apparatus, device and medium | |
| CN111078209B (en) | Development processing method, device and equipment for business page | |
| CN112688863B (en) | Gateway data processing method and device and electronic equipment |
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 |