CN107247669A - The performance test methods and device of a kind of routine interface - Google Patents
The performance test methods and device of a kind of routine interface Download PDFInfo
- Publication number
- CN107247669A CN107247669A CN201710423456.2A CN201710423456A CN107247669A CN 107247669 A CN107247669 A CN 107247669A CN 201710423456 A CN201710423456 A CN 201710423456A CN 107247669 A CN107247669 A CN 107247669A
- Authority
- CN
- China
- Prior art keywords
- interface
- routine
- request
- test
- routine interface
- 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
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
Abstract
The embodiment of the present invention is the performance test methods and device on a kind of routine interface, and this method includes：At least two routine interfaces to be tested are determined in routine interface list；Obtain the request allocation proportion, test data and test request amount of at least two routine interface；According to the test request amount and the request allocation proportion, the number of request per second of each routine interface at least two routine interface is calculated；Number of request per second and test data analogue data request based on each routine interface carry out performance test at least two routine interface.The embodiment of the present invention can ensure that each routine interface is tested accordingly according to the actual requirements, so that test result is more accurate.
Description
Technical field
The present embodiments relate to communication technical field, in particular, be related to routine interface performance test methods and
Device.
Background technology
At present, staff is in some routine interface of test system, can first pass through test program simulant-client to
Server send request message, server receive request message after the request message is handled it, then server again should
Answer message and be sent to client, client can receive response message, finally, staff can be to test process and test result
Recorded, to draw test result.
If staff will be in the multiple routine interfaces of same time test, then staff can configure same test
Use-case, to test multiple routine interfaces, and judges that multiple routine interfaces whether there is problem.However, in actual scene, each
The service condition of routine interface is different, so each routine interface can not be surveyed really using same test case
The problem of each routine interface is present is tried out, so the method for testing of current routine interface can not be according to each routine interface
Actual demand tested accordingly, so that the accuracy of test result can not be ensured.
The content of the invention
The embodiment of the present invention provides a kind of performance test methods and device of routine interface so that each routine interface according to
Actual demand is tested accordingly, to ensure that test result is more accurate.
First aspect according to embodiments of the present invention there is provided a kind of performance test methods of routine interface, including：
At least two routine interfaces to be tested are determined in routine interface list；
Obtain the request allocation proportion, test data and test request amount of at least two routine interfaces；
According to test request amount and request allocation proportion, the per second of each routine interface at least two routine interfaces is calculated
Number of request；
Number of request per second and test data analogue data based on each routine interface are asked at least two routine interfaces
Carry out performance test.
Optionally, determine that at least two routine interfaces to be tested include in routine interface list：
Show each routine interface in routine interface list；
When receiving the selection instruction of user's input, determined according to selection instruction in routine interface list to be tested
At least two routine interfaces.
Optionally, determine that at least two routine interfaces to be tested include in routine interface list：
The interface identifier of the routine interface to be tested obtained；
At least two routine interfaces corresponding with interface identifier are determined in routine interface list.
Optionally, in addition to：
The history average request for obtaining target program interface at least two routine interfaces takes；
This average request for extracting this test of target program interface takes；
When the time-consuming difference taken with history average request of this average request is more than threshold value, target program interface is determined
For bottleneck interface.
Optionally, in addition to：
The history average request for obtaining target program interface at least two routine interfaces takes；
This average request for extracting this test of target program interface takes；
When the time-consuming difference taken with history average request of this average request is less than threshold value, target program interface is exported
This test request take.
Second aspect according to embodiments of the present invention there is provided a kind of performance testing device of routine interface, including：
First determining module, for determining at least two routine interfaces to be tested in routine interface list；
First acquisition module, request allocation proportion, test data and test for obtaining at least two routine interfaces please
The amount of asking；
Computing module, for according to test request amount and request allocation proportion, calculating each at least two routine interfaces
The number of request per second of routine interface；
Test module, for the number of request per second based on each routine interface and the request of test data analogue data at least
Two routine interfaces carry out performance test.
Optionally, the first determining module includes：
Display sub-module, for showing each routine interface in routine interface list；
First determination sub-module, for when receiving the selection instruction of user's input, being connect according to selection instruction in program
At least two routine interfaces to be tested are determined in mouth list.
Optionally, the first determining module includes：
Acquisition submodule, the interface identifier for the routine interface to be tested of acquisition；
Second determination sub-module, for determining that at least two programs corresponding with interface identifier connect in routine interface list
Mouthful.
Optionally, in addition to：
Second acquisition module, the history average request consumption for obtaining target program interface at least two routine interfaces
When；
First extraction module, takes for extracting this average request of this test of target program interface；
Second determining module, for being more than threshold value in the time-consuming difference time-consuming with history average request of this average request
When, it is bottleneck interface to determine target program interface.
Optionally, in addition to：
3rd acquisition module, the history average request consumption for obtaining target program interface at least two routine interfaces
When；
Second extraction module, takes for extracting this average request of this test of target program interface；
Output module, it is defeated for when the time-consuming difference taken with history average request of this average request is less than threshold value
The request for going out this test of target program interface takes.
Compared with prior art, the technical scheme that the present embodiment is provided has advantages below and feature：
, will after at least two routine interfaces to be tested are determined in scheme provided in an embodiment of the present invention
The request allocation proportion, test data and test request amount of at least two routine interfaces are obtained, and according to test request amount and is asked
Allocation proportion is sought, the number of request per second of each routine interface at least two routine interfaces is calculated, is finally based on each program and connects
Number of request per second and test data the analogue data request of mouth carry out performance test at least two routine interfaces, so of the invention
Embodiment can ensure that each routine interface is tested accordingly according to the actual requirements, so that test result is more accurate
Really.
Brief description of the drawings
In order to illustrate more clearly about the embodiment of the present invention or technical scheme of the prior art, below will be to institute in embodiment
The accompanying drawing needed to use is briefly described, it should be apparent that, drawings in the following description are only some implementations of the present invention
Example, for those of ordinary skill in the art, on the premise of not paying creative work, can also be obtained according to these accompanying drawings
Obtain other accompanying drawings.
Fig. 1 is a kind of flow chart of the performance test methods of routine interface provided in an embodiment of the present invention.
Fig. 2 is a kind of schematic diagram of the performance testing device of routine interface provided in an embodiment of the present invention.
Fig. 3 is a kind of schematic diagram of server provided in an embodiment of the present invention.
Embodiment
In order that those skilled in the art more fully understand the present invention program, below in conjunction with the embodiment of the present invention
Accompanying drawing, the technical scheme in the embodiment of the present invention is clearly and completely described.
In some flows of description in description and claims of this specification and above-mentioned accompanying drawing, contain according to
Particular order occur multiple operations, but it should be clearly understood that these operation can not herein occur according to it is suitable
Sequence is performed or performed parallel, and the sequence number such as 101,102 etc. of operation is only used for distinguishing each different operation, sequence number
Any execution sequence is not represented for itself.In addition, these flows can include more or less operations, and these operations can
To perform or perform parallel in order.It should be noted that the description such as " first ", " second " herein, is to be used to distinguish not
Same message, equipment, module etc., does not represent sequencing, it is different types also not limit " first " and " second ".
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is carried out clear, complete
Site preparation is described, it is clear that described embodiment is only a part of embodiment of the invention, rather than whole embodiments.It is based on
Embodiment in the present invention, the every other implementation that those skilled in the art are obtained under the premise of creative work is not made
Example, belongs to the scope of protection of the invention.
Fig. 1 is a kind of flow chart of the performance test methods of routine interface provided in an embodiment of the present invention.Journey shown in Fig. 1
The performance test methods of sequence interface can ensure that each routine interface is tested accordingly according to the actual requirements, so that
Test result is more accurate.This method comprises the following steps.
Step S11, at least two routine interfaces to be tested are determined in routine interface list.
Wherein, method provided in an embodiment of the present invention can apply to server, and server can be apparatus such as computer.
Routine interface is referred between multiple programs or service by specified communication protocol (such as http protocol) exchange
A kind of mode of data.Routine interface is one of two class interfaces that operating system is provided the user, and programming personnel is led in a program
Routine interface is crossed to ask operating system to provide service.
Record has the interface identifier of multiple routine interfaces in routine interface list.For example, it is assumed that remembering in routine interface list
Record has the interface identifier of 5 routine interfaces, and the interface identifier of this 5 routine interfaces is respectively interface identifier NO1, interface identifier
NO2, interface identifier NO3, interface identifier NO4 and interface identifier NO5, can be by the interface identifier of this 5 routine interfaces come table
Levy corresponding 5 routine interfaces.
The mode of at least two routine interfaces to be tested is determined in routine interface list many kinds, is provided below two
Plant specific mode.
First way, determines that at least two routine interfaces to be tested comprise the following steps in routine interface list：
First, each routine interface in display routine interface list；Secondly, when receiving the selection instruction of user's input, according to
Selection instruction determines at least two routine interfaces to be tested in routine interface list.
In the first way, server can first show each routine interface in routine interface list, to facilitate work
Make the routine interface that personnel select to need to be tested in each routine interface；Staff can input selection instruction, so that
Server determines at least two routine interfaces to be tested according to selection instruction in routine interface list.
For example, it is assumed that server can first show the interface identifier of 5 routine interfaces recorded in routine interface list, this
The interface identifier of 5 routine interfaces is respectively interface identifier A, interface identifier B, interface identifier C, interface identifier D and interface identifier
E, to facilitate the routine interface that staff selects needs to be tested in the interface identifier of this 5 routine interfaces；Assuming that work
Make personnel and input selection instruction in the routine interface list of display, to click interface identifier A, interface identifier B and interface identifier
C, the selection instruction that server can be inputted according to staff determines routine interface to be tested to connect in routine interface list
Mouth mark A, interface identifier B and interface identifier C, so that it is determined that going out to need the routine interface tested.
The second way, determines that at least two routine interfaces to be tested comprise the following steps in routine interface list：
First, the interface identifier of the routine interface to be tested of acquisition.Secondly, determined in routine interface list corresponding with interface identifier
At least two routine interfaces.
In the second way, server can first get the interface identifier of routine interface to be tested, with learn need into
Which the interface identifier of row test has；Then, server can be determined in routine interface list it is corresponding with interface identifier at least
Two routine interfaces, now, server, which is just learnt, needs which the routine interface tested has.
For example, it is assumed that record has the interface identifier of 5 routine interfaces in routine interface list, this 5 routine interfaces connect
Mouth mark is respectively interface identifier A, interface identifier B, interface identifier C, interface identifier D and interface identifier E.Assuming that server can be first
The interface identifier for getting routine interface to be tested is interface identifier D and interface identifier E, and then server can be arranged in routine interface
Two routine interfaces corresponding with interface identifier D and interface identifier E are determined in table, now, server, which is just known, needs what is tested
Which routine interface is.
Step S12, request allocation proportion, test data and the test request amount for obtaining at least two routine interfaces.
Wherein, test data is the request that at least two routine interfaces are received in historical time section.For example, it is assumed that extremely
The interface identifier of few two routine interfaces is interface identifier A and interface identifier B, and server can get interface identifier A and interface
The HTTP request that mark B is received within the previous moon.
Test request amount can be the number of request per second pre-set, and the english abbreviation of number of request per second is QPS, i.e.,
Query Per Second, namely number of request/second.For example, test request amount is 600 number of request/seconds.
It is the allocation proportion based on test request amount between at least two routine interfaces to ask allocation proportion.Ask distribution ratio
Example can be pre-configured, or staff is according to the numbers of at least two routine interfaces determined in step S11
What amount was configured.
For example, it is assumed that request allocation proportion can be pre-configured, that is, ask allocation proportion to be previously configured as
1:2:3；And for example, it is assumed that request allocation proportion is that staff is matched somebody with somebody according to the quantity at least two routine interfaces determined
Put, that is, the quantity for assuming at least two routine interfaces is 2, then staff can match somebody with somebody according to the demand of routine interface
It is 1 to put request allocation proportion:2.
Step S13, according to test request amount and request allocation proportion, each program at least two routine interfaces that calculates connects
The number of request per second of mouth.
Where it is assumed that test request amount is 600 number of request/seconds, request allocation proportion is 1:2, at least two programs connect
The interface identifier of mouth is interface identifier A and interface identifier B, based on 600 number of request/seconds of test request amount and request allocation proportion
1:2 it is known that interface identifier A number of request per second is 200, and interface identifier B number of request per second is 400.
Step S14, the number of request per second based on each routine interface and the request of test data analogue data are at least two
Routine interface carries out performance test.
Wherein, after the number of request per second of each routine interface is determined, it just can utilize and get in step s 12
Test data simulate request of data, and then performance test is carried out at least two routine interfaces,
In the embodiment shown in fig. 1, determine after at least two routine interfaces to be tested, will obtain in server
The request allocation proportion, test data and test request amount of at least two routine interfaces are taken, and according to test request amount and request
Allocation proportion, calculates the number of request per second of each routine interface at least two routine interfaces, is finally based on each routine interface
Number of request per second and the request of test data analogue data performance test is carried out at least two routine interfaces, so the present invention is real
Applying example can ensure that each routine interface is tested accordingly according to the actual requirements, so that test result is more accurate
Really.
Optionally, in the embodiment shown in fig. 1, after step S14, following sub-step can also be included：First, obtain
The history average request of target program interface at least two routine interfaces is taken to take；Secondly, the sheet of target program interface is extracted
This average request of secondary test takes；Finally, it is more than in the time-consuming difference taken with history average request of this average request
During threshold value, it is bottleneck interface to determine target program interface.
Wherein, the time-consuming average value for referring to the time of all request consumption in historical time section of history average request.
For example, it is assumed that routine interface X receives 3 requests in historical time section, A, request B and request C are respectively asked, wherein,
The time for asking A consumption is 100ms, and the time of request B consumption is 80ms, and the time of request C consumption is 120ms, then history
Average request is taken as (100ms+80ms+120ms)/3=100ms.This average request is time-consuming to refer to that this carries out performance
The average value of the time of all request consumption in test.
If this average request is time-consuming to be more than threshold value with the difference that history average request takes, illustrate target program interface
The problem of there may be certain is, it is necessary to problem present in staff's subsequent analysis target program interface, so at this
When the time-consuming difference taken with history average request of average request is more than threshold value, server can determine whether that target program interface is bottleneck
Interface, in order to which staff can carry out subsequent analysis to bottleneck interface.
Optionally, in the embodiment shown in fig. 1, after step S14, following sub-step can also be included：First, obtain
The history average request of target program interface at least two routine interfaces is taken to take；Secondly, the sheet of target program interface is extracted
This average request of secondary test takes；Finally, it is less than in the time-consuming difference taken with history average request of this average request
During threshold value, the request of this test of output target program interface takes.
Wherein, if this average request is time-consuming to be less than threshold value with the difference that history average request takes, target journey is illustrated
There is no problem for sequence interface, so the request for only needing to export this test of target program interface takes, so that staff
Understand the running situation of the target program interface.
Fig. 2 is a kind of schematic diagram of the performance testing device of routine interface provided in an embodiment of the present invention.Fig. 2 is Fig. 1 pairs
The corresponding embodiments of Fig. 1 are referred to Fig. 1 identical contents in the device embodiment answered, Fig. 2.Reference picture 2, the device bag
Include with lower module：
First determining module 11, for determining at least two routine interfaces to be tested in routine interface list.
First acquisition module 12, request allocation proportion, test data and test for obtaining at least two routine interfaces
Request amount.
Computing module 13, for according to test request amount and request allocation proportion, calculating every at least two routine interfaces
The number of request per second of individual routine interface.
Test module 14, for the number of request per second based on each routine interface and the request of test data analogue data to extremely
Few two routine interfaces carry out performance test.
Optionally, the first determining module 11 can also include display sub-module and the first determination sub-module, wherein：
Display sub-module, for showing each routine interface in routine interface list.
First determination sub-module, for when receiving the selection instruction of user's input, being connect according to selection instruction in program
At least two routine interfaces to be tested are determined in mouth list.
Optionally, the first determining module 11 can also include acquisition submodule and the second determination sub-module, wherein：
Acquisition submodule, the interface identifier for the routine interface to be tested of acquisition.
Second determination sub-module, for determining that at least two programs corresponding with interface identifier connect in routine interface list
Mouthful.
Optionally, the device shown in Fig. 2 can also include with lower module：
Second acquisition module, the history average request consumption for obtaining target program interface at least two routine interfaces
When.
First extraction module, takes for extracting this average request of this test of target program interface.
Second determining module, for being more than threshold value in the time-consuming difference time-consuming with history average request of this average request
When, it is bottleneck interface to determine target program interface.
Optionally, the device shown in Fig. 2 can also include with lower module：
3rd acquisition module, the history average request consumption for obtaining target program interface at least two routine interfaces
When.
Second extraction module, takes for extracting this average request of this test of target program interface.
Output module, it is defeated for when the time-consuming difference taken with history average request of this average request is less than threshold value
The request for going out this test of target program interface takes.
Fig. 3 is a kind of schematic diagram of server provided in an embodiment of the present invention.Reference picture 3, the server includes：Processor
21 and memory 22, wherein, memory 22 is used to store one or more computer instruction, and one or more computer refers to
Order calls execution for processor 21；
Processor 21 is used for：At least two routine interfaces to be tested are determined in routine interface list；Obtain at least two
Request allocation proportion, test data and the test request amount of individual routine interface；According to test request amount and request allocation proportion, meter
Calculate the number of request per second of each routine interface at least two routine interfaces；Based on the number of request per second of each routine interface and survey
Try digital simulation request of data and performance test is carried out at least two routine interfaces.
On the device in above-described embodiment, wherein modules perform the concrete mode of operation in relevant this method
Embodiment in be described in detail, explanation will be not set forth in detail herein.
It is apparent to those skilled in the art that, for convenience and simplicity of description, the system of foregoing description,
The specific work process of device and unit, may be referred to the corresponding process in preceding method embodiment, will not be repeated here.
Device embodiment described above is only schematical, wherein the unit illustrated as separating component can
To be or may not be physically separate, the part shown as unit can be or may not be physics list
Member, you can with positioned at a place, or can also be distributed on multiple NEs.It can be selected according to the actual needs
In some or all of module realize the purpose of this embodiment scheme.Those of ordinary skill in the art are not paying creativeness
Work in the case of, you can to understand and implement.
Through the above description of the embodiments, those skilled in the art can be understood that each embodiment can
Realized by the mode of software plus required general hardware platform, naturally it is also possible to pass through hardware.Understood based on such, on
The part that technical scheme substantially in other words contributes to prior art is stated to embody in the form of software product, should
Computer software product can be stored in a computer-readable storage medium, such as ROM/RAM, magnetic disc, CD, including some fingers
Order is to cause a computer equipment (can be personal computer, server, or network equipment etc.) to perform each implementation
Method described in some parts of example or embodiment.
Finally it should be noted that：The above embodiments are merely illustrative of the technical solutions of the present invention, rather than its limitations；Although
The present invention is described in detail with reference to the foregoing embodiments, it will be understood by those within the art that：It still may be used
To be modified to the technical scheme described in foregoing embodiments, or equivalent substitution is carried out to which part technical characteristic；
And these modification or replace, do not make appropriate technical solution essence depart from various embodiments of the present invention technical scheme spirit and
Scope.
Claims (10)
1. a kind of performance test methods of routine interface, it is characterised in that including：
At least two routine interfaces to be tested are determined in routine interface list；
Obtain the request allocation proportion, test data and test request amount of at least two routine interface；
According to the test request amount and the request allocation proportion, each program at least two routine interface that calculates connects
The number of request per second of mouth；
Number of request per second and the test data analogue data based on each routine interface are asked to described at least two
Routine interface carries out performance test.
2. the performance test methods of routine interface according to claim 1, it is characterised in that described in routine interface list
It is middle to determine that at least two routine interfaces to be tested include：
Show each routine interface in described program interface list；
When receiving the selection instruction of user's input, determined according to the selection instruction in described program interface list to be measured
At least two routine interfaces of examination.
3. the performance test methods of routine interface according to claim 1, it is characterised in that described in routine interface list
It is middle to determine that at least two routine interfaces to be tested include：
The interface identifier of the routine interface to be tested obtained；
At least two routine interfaces corresponding with the interface identifier are determined in routine interface list.
4. the performance test methods of routine interface according to claim 1, it is characterised in that also include：
The history average request for obtaining target program interface at least two routine interface takes；
This average request for extracting this test of the target program interface takes；
When the time-consuming difference taken with the history average request of this described average request is more than threshold value, the target is determined
Routine interface is bottleneck interface.
5. the performance test methods of routine interface according to claim 1, it is characterised in that also include：
The history average request for obtaining target program interface at least two routine interface takes；
This average request for extracting this test of the target program interface takes；
When the time-consuming difference taken with the history average request of this described average request is less than threshold value, the target is exported
The request of this test of routine interface takes.
6. a kind of performance testing device of routine interface, it is characterised in that including：
First determining module, for determining at least two routine interfaces to be tested in routine interface list；
First acquisition module, request allocation proportion, test data and test for obtaining at least two routine interface please
The amount of asking；
Computing module, connects for according to the test request amount and the request allocation proportion, calculating at least two program
The number of request per second of each routine interface in mouthful；
Test module, for the number of request per second based on each routine interface and test data analogue data request pair
At least two routine interface carries out performance test.
7. the performance testing device of routine interface according to claim 6, it is characterised in that the first determining module bag
Include：
Display sub-module, for showing each routine interface in described program interface list；
First determination sub-module, for when receiving the selection instruction of user's input, according to the selection instruction in the journey
At least two routine interfaces to be tested are determined in sequence interface list.
8. the performance testing device of routine interface according to claim 6, it is characterised in that the first determining module bag
Include：
Acquisition submodule, the interface identifier for the routine interface to be tested of acquisition；
Second determination sub-module, for determining that at least two programs corresponding with the interface identifier connect in routine interface list
Mouthful.
9. the performance testing device of routine interface according to claim 6, it is characterised in that also include：
Second acquisition module, the history average request for obtaining target program interface at least two routine interface consumes
When；
First extraction module, takes for extracting this average request of this test of the target program interface；
Second determining module, for being more than threshold in the time-consuming difference time-consuming with the history average request of this described average request
During value, it is bottleneck interface to determine the target program interface.
10. the performance testing device of routine interface according to claim 6, it is characterised in that also include：
3rd acquisition module, the history average request for obtaining target program interface at least two routine interface consumes
When；
Second extraction module, takes for extracting this average request of this test of the target program interface；
Output module, for being less than threshold value in the time-consuming difference time-consuming with the history average request of this described average request
When, the request for exporting this test of the target program interface takes.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710423456.2A CN107247669A (en) | 2017-06-07 | 2017-06-07 | The performance test methods and device of a kind of routine interface |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710423456.2A CN107247669A (en) | 2017-06-07 | 2017-06-07 | The performance test methods and device of a kind of routine interface |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107247669A true CN107247669A (en) | 2017-10-13 |
Family
ID=60017822
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710423456.2A Pending CN107247669A (en) | 2017-06-07 | 2017-06-07 | The performance test methods and device of a kind of routine interface |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107247669A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111324536A (en) * | 2020-02-19 | 2020-06-23 | 香港乐蜜有限公司 | Pressure testing method and device, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105281978A (en) * | 2015-10-23 | 2016-01-27 | 小米科技有限责任公司 | Performance test method, device and system |
| US20160092348A1 (en) * | 2014-09-26 | 2016-03-31 | Oracle International Corporation | Updatable native mobile application for testing new features |
| CN106294177A (en) * | 2016-08-22 | 2017-01-04 | 腾讯科技（深圳）有限公司 | The method for testing pressure of a kind of interface and test equipment |
| CN106484610A (en) * | 2015-09-02 | 2017-03-08 | 阿里巴巴集团控股有限公司 | A kind of Beta method and apparatus |
-
2017
- 2017-06-07 CN CN201710423456.2A patent/CN107247669A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160092348A1 (en) * | 2014-09-26 | 2016-03-31 | Oracle International Corporation | Updatable native mobile application for testing new features |
| CN106484610A (en) * | 2015-09-02 | 2017-03-08 | 阿里巴巴集团控股有限公司 | A kind of Beta method and apparatus |
| CN105281978A (en) * | 2015-10-23 | 2016-01-27 | 小米科技有限责任公司 | Performance test method, device and system |
| CN106294177A (en) * | 2016-08-22 | 2017-01-04 | 腾讯科技（深圳）有限公司 | The method for testing pressure of a kind of interface and test equipment |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111324536A (en) * | 2020-02-19 | 2020-06-23 | 香港乐蜜有限公司 | Pressure testing method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111917878B (en) | Message processing method, device, equipment and storage medium | |
| CN109976997B (en) | Test method and device | |
| CN109359007B (en) | Method and system for processing error log, electronic device and storage medium | |
| CN109684947A (en) | Mark quality control method, device, computer equipment and storage medium | |
| CN106095673A (en) | Automated testing method based on WEB interface and system | |
| CN108399114A (en) | A kind of system performance testing method, apparatus and storage medium | |
| CN105099801B (en) | The test system of information management system and test environment analogy method | |
| CN108255707A (en) | Development roles creation method, device, equipment and the storage medium of test case | |
| CN108628747A (en) | H5 application testing methods, device, computer equipment and storage medium | |
| CN110263748A (en) | Method and apparatus for sending information | |
| CN109582550B (en) | Method, device and server for acquiring full-service scene fault set | |
| CN108984490A (en) | A kind of data mask method, device, electronic equipment and storage medium | |
| CN107038108A (en) | The method of testing and device of software | |
| CN107038120A (en) | A kind of method for testing software and equipment | |
| CN109088793B (en) | Method and apparatus for detecting network failure | |
| CN108109580A (en) | Parameter adaptation method, apparatus, equipment and the storage medium of LED display | |
| CN107247669A (en) | The performance test methods and device of a kind of routine interface | |
| CN107273112A (en) | A kind of present list method for information display and device | |
| CN109711703A (en) | The line loss querying method and system of power distribution network | |
| CN109408304A (en) | Block chain introduces test method, device, equipment and readable storage medium storing program for executing | |
| CN109817045A (en) | A kind of mathematical studying householder method, system and its apparatus | |
| CN114416597A (en) | Test case record generation method and device | |
| CN117097789A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN110764909B (en) | Method and system for load balancing of storage device of cloud computing platform | |
| CN107192899B (en) | The method, apparatus and system of measurement application and test equipment Auto-matching |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20171013 |