CN102214140B - Method and system for automatic software testing - Google Patents
Method and system for automatic software testing Download PDFInfo
- Publication number
- CN102214140B CN102214140B CN201110168160.3A CN201110168160A CN102214140B CN 102214140 B CN102214140 B CN 102214140B CN 201110168160 A CN201110168160 A CN 201110168160A CN 102214140 B CN102214140 B CN 102214140B
- Authority
- CN
- China
- Prior art keywords
- case
- message
- measurand
- test
- response
- 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
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/3688—Test management for test execution, e.g. scheduling of test suites
-
- 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/3696—Methods or tools to render software testable
Abstract
The invention discloses a method for automatic software testing, comprising the steps that: a control module notifies stub modules of a response case according to message type and notifies a drive module of a request case and an expected response case; the drive module calls a preset message communication module to send a packaged request case message to a object to be tested in order to cause the object to be tested to send a request message supported by request data to the stub modules; according to the request message sent by the object to be tested, the stub modules call a preset message protocol module to perform message field regulation on the response case in order to meet the demand of running data of the object to be tested; and the drive module receives a response message of the object to be tested, calls the message protocol module to analyze the response message and compares the response message with the expected response case message to determine whether the case passes the test. The invention further provides a system for automatic software testing. The method and the system provided by the invention support the flexible deploy of 1 drive module and a plurality of stub modules.
Description
Technical field
The present invention relates to computer communication field, more particularly, to a kind of automatic test approach of software and system.
Background technology
Software automatic test has been widely used in various software test activities, not only can easily mould by automatic test
Intend various normal or abnormal conditions tests, substantial amounts of time and manpower can also be saved simultaneously, improve testing efficiency.
Software automatic test system majority from structure can be divided into control module, drive module and stubs, wherein controls
The whole auto test flow of module coordination processed, drive module constructs request message according to test case and is driven into measurand, stake
Module is used for responding to the data support that measurand runs needs.
In software test at present, software module often has multiple inputs and multiple output, needs and multiple external modules
Interact with system, I/O mode not only only has function call interface, common at present also have internet message/file/
The input/output interfaces such as data-base recording.But existing software testing technology major part is all single message input, single message
Type export, or from function rank, software module and system are tested it is difficult to from flow process to multiple input how defeated
Outgoing interface interaction data is processed effectively is tested automatically.In addition, each module in current software automatic test system is tied
Structure limits can not separately be deployed in different test environments and runs it is difficult to simulate the real running environment of measurand, often
Test effect is made to have a greatly reduced quality.
Content of the invention
Present invention is primarily targeted at providing a kind of Software Automatic Testing Method and system, can be to multiple-input and multiple-output
The various interfaces of mode are effectively tested automatically, support internet message/file/database multiple input/output interface class
Type, supports the flexible deployment of 1+N mode (i.e. 1 drive module+N number of stubs).
In order to realize goal of the invention, the present invention provides a kind of method of software automatic test, comprises the following steps：
All of test case is preserved in the buffer by control module；Described test case includes responding use-case, request use
Example and expectation response use-case, wherein, described response use-case supports that canonical asterisk wildcard compares；
After test starts, control module will respond use-case according to type of message and notify stubs, will ask use-case and phase
Use-case to be responded notifies drive module；
Drive module calls preset messaging module that the request use-case message after encapsulating is sent to measurand, with
Measurand is caused to send the request message of request data support to stubs；
The request message that stubs send according to measurand, carries out message field adjustment to the response use-case after encapsulation,
To meet the needs of measurand service data；
Drive module receives the response message of measurand, and message call protocol module parses this response message, by its with
Whether described expectation response use-case message is compared, confirm this test case by test.
Preferably, described drive module message call communication module by encapsulate after request use-case message be sent to tested right
As being included to stubs with the request message causing measurand to send request data support：
The request use-case that the encapsulation of message call protocol module is notified by control module；
Request use-case after encapsulating is sent to measurand by message call communication module；
Judge whether to receive the response of measurand.
Preferably, the request message that described stubs send according to measurand, disappears to the response use-case after encapsulation
Breath field adjustment, is included with the needs meeting measurand service data：
The response use-case that the encapsulation of message call protocol module is notified by control module；
Receive the request message of measurand, message call protocol module parses to request message；
According to measurand request message analysis result, message field adjustment is carried out to the response use-case after encapsulation, to accord with
Closing measurand service data needs；
Response use-case after adjustment is responded to measurand.
Preferably, also include after executing all steps：
This test case implementation status is recorded into test log by control module；
Control module checks whether that all test cases are finished, if also test case, transfers next test
Use-case, carries out next round test case and automatically tests；Otherwise, terminate test.
Preferably, described stubs are a plurality of.
The present invention provides a kind of system of software automatic test, leads to including control module, drive module, stubs, message
Letter module and messaging protocol module, wherein：
Control module, for preserving in the buffer all of test case；Described test case includes responding use-case, asks
Seek use-case and expect response use-case；
After test starts, control module will respond use-case according to type of message and notify stubs, will ask use-case and phase
Use-case to be responded notifies drive module；
Drive module is tested right for calling preset messaging module to be sent to the request use-case message after encapsulating
As to cause measurand to send the request message of request data support to stubs；
Stubs, for the request message sending according to measurand, carry out message field to the response use-case after encapsulation
Adjustment, to meet the needs of measurand service data；
Described drive module is additionally operable to receive the response message of measurand, and message call protocol module parses this response and disappears
Breath, with described, it is expected that response use-case message is compared, confirms whether this test case is passed through.
Preferably, described drive module specifically for：
The request use-case that the encapsulation of message call protocol module is notified by control module；
Request use-case after encapsulating is sent to measurand by message call communication module；
Judge whether to receive the response of measurand.
Preferably, described stubs specifically for：
The response use-case that the encapsulation of message call protocol module is notified by control module；
Receive the request message of measurand, message call parsing module parses to request message；
According to measurand request message analysis result, message field adjustment is carried out to the response use-case after encapsulation, to accord with
Closing measurand service data needs；
Response use-case after adjustment is responded to measurand.
Preferably, described control module specifically for：
Use-case will be responded according to type of message and notify stubs, use-case will be asked and expect that response use-case notifies driving
Module；This test case implementation status is recorded into test log；
Check whether that all test cases are finished, if also test case, transfer next test case, carry out
Next round test case is tested automatically；Otherwise, terminate test.
The method of software automatic test provided by the present invention or system, can process one end input use-case, and multiterminal export
To the situation of all kinds stake, message field can customize, and canonical asterisk wildcard can be supported to compare for response use-case so that test case
Many type of messages, flexible configuration can be supported.Dependence test use-case can be unified to preserve, convenient preservation, transmission and loading, greatly carries
Function quick regression tested efficiency is done after having risen code refactoring.Additionally, the present invention also can as needed can by drive module and
Stubs are deployed separately so that test environment more meets actual motion environment.
Brief description
Fig. 1 is the flow chart of the method for software automatic test in an embodiment of the present invention；
Fig. 2 is the flow chart of the method for software automatic test in an embodiment of the present invention；
Fig. 3 is the flow chart of the method for software automatic test in another embodiment of the present invention；
Fig. 4 is the structural representation of the system of software automatic test in an embodiment of the present invention；
Fig. 5 is the workflow diagram of the system of software automatic test in one embodiment of the invention.
The realization of the object of the invention, functional characteristics and advantage will be described further in conjunction with the embodiments referring to the drawings.
Specific embodiment
It should be appreciated that specific embodiment described herein, only in order to explain the present invention, is not intended to limit the present invention.
Fig. 1 shows the method flow of software automatic test in an embodiment of the invention.This flow process is based on and includes
There are control module, drive module, the test system of multiple stubs, messaging protocol module and messaging module.The method bag
Include following steps：
Step S10, the preset messaging module in order to send or to receive message and in order to encapsulate or to parse message
Messaging protocol module；Specifically, messaging protocol module is used for by type of message encapsulation or analysis request use-case or response use-case.Disappear
Message communication module is used for sending the request use-case after encapsulating and receives response use-case.For example, messaging protocol module encapsulation carrys out self-powered
The request use-case of dynamic model block and the response use-case of stubs；Parsing is derived from request message and the response message of measurand.Message
Request use-case packaged for messaging protocol module is sent to measurand by communication module, or receives the request that measurand is sent
Message gives the parsing of messaging protocol module.
Step S20, all of test case is preserved in the buffer by control module；Described test case includes response and uses
Example, request use-case and expectation response use-case；Control module includes case management sub-block, for various link informations, request use-case,
Response use-case and the management expecting response use-case, in this step, control module calls case management sub-block to load all of test
Use-case preserves in the buffer.
Step S30, after test starts, control module will respond use-case according to type of message and notify stubs, will ask
Use-case and expectation response use-case notify drive module；Advice method is not limited to function call, Socket notifies etc..In an enforcement
In example, step S30 may include：First, control module transfers the test case being currently needed for executing；Then by test case
Response use-case notifies to stubs, and waits the feedback of stubs.If notifying stubs success, by the request in test case
Use-case and expectation response use-case notify drive module.Stubs can have N number of, and N is the integer more than 1, configures on demand, control module
Which stubs specific can automatically be notified according to type of message.
Step S40, the request use-case message after encapsulating is sent to measurand by drive module message call communication module,
To cause measurand to send the request message of request data support to stubs；
Step S50, the request message that stubs send according to measurand, message word is carried out to the response use-case after encapsulation
Section adjustment, to meet the needs of measurand service data；
Step S60, drive module receives the response message of measurand, and message call protocol module parses this response and disappears
Whether breath, with described, it is expected that response use-case message is compared, confirms this test case by test.Disappear in the present invention
Breath field can customize, and response use-case supports canonical asterisk wildcard to compare so that test case can support many type of messages, configuration spirit
Live.
With reference to Fig. 2, show the workflow of software automatic test system in the present invention one specific example, this flow process is successively
Comprise the following steps：
Step S101, control module will respond use-case and notify stubs；
Step S102, control module will be asked use-case and be expected that response use-case notifies control module.
Step S103, drive module message call protocol module package request use-case.
Step S104, the request use-case after encapsulating is sent to measurand by drive module message call communication module.
Step S105, measurand receives request use-case, causes measurand to do built-in function.
Step S106, measurand sends a request message to stubs request data and supports, this step is not limited to only send
To a stake, stake can not be sent to only in measurand built-in function it is also possible to be sent to multiple stakes.
Step S107, stubs receive measurand request message, parsing, the response use-case that original control module is notified
Do necessary adjustment.
Step S108, the response use-case after adjusting is responded to measurand by stubs.
Step S109, after measurand receives the response use-case of stubs, causes measurand built-in function.
Step S110, after measurand does built-in function computing, responds to drive module message.
Step S111, drive module message call protocol module resolution response message, by the response message and former after parsing
The expectation response use-case message that first control module notifies is compared, is determined whether this test case is passed through.
So far, complete an auto test flow, according to the number of use-case, next test case will be automatically continued with
Automatically test.
In above-mentioned steps S40, the processing procedure of drive module specifically includes：
The request use-case that the encapsulation of message call protocol module is notified by control module；
Request use-case after encapsulating is sent to measurand by message call communication module；
Enter and wait measurand responsive state, judge whether to receive the response of measurand.If it is, executing step
Rapid S60, if it is not, then receiving measurand response message failure, such as reception message is wrong, measurand is overtime
No response etc..
In above-mentioned steps S50, the processing procedure of stubs specifically includes：
The response use-case that the encapsulation of message call protocol module is notified by control module；
Receive the request message of measurand, message call protocol module parses to request message；
Message field adjustment is carried out to the response use-case after encapsulation, to meet measurand service data needs；
Response use-case after adjustment is responded to measurand.
With reference to Fig. 3, in one embodiment, also include after all steps shown in execution Fig. 1：
Step S70, this test case implementation status is recorded into test log by control module；In the present embodiment, control
Module also includes test log sub-block, for real time record test operation daily record, journal formatting is shown on interface, output
Final test result daily record.
Step S80, control module checks whether that all test cases are finished, if also test case, transfers down
One test case, carries out next round test case and automatically tests；Otherwise, terminate test.
The method of software automatic test provided by the present invention, can process one end input use-case, multiterminal export various
The situation of type stake, message field can customize, response use-case support canonical asterisk wildcard compare so that test case can support many
Type of message, flexible configuration.Dependence test use-case can be unified to preserve, convenient preservation, transmission and loading, greatly improves code
Function quick regression tested efficiency is done after reconstruct.Additionally, drive module and stubs also can be divided by the present invention as needed
From deployment so that test environment more meets actual motion environment.
The present invention also provides a kind of software automatic test system, in order to realize said method.With reference to Fig. 4, this system includes
Control module 10, drive module 20, stubs 30, messaging module 40 and messaging protocol module 50, wherein：
Control module 10, for preserving in the buffer all of test case；Described test case include respond use-case,
Request use-case and expectation response use-case；Control module 10 includes case management sub-block 11, uses for various link informations, request
Example, response use-case and the management expecting response use-case, in this step, it is all that control module 10 calls case management sub-block 11 to load
Test case preserve in the buffer.
After test starts, control module 10 will respond use-case according to type of message and notify stubs 30, will ask use-case
Notify drive module 20 with expectation response use-case；The advice method of control module 10 is not limited to function call, Socket notifies
Deng.In one embodiment, control module 10 transfers the test case being currently needed for executing first；Then by the sound in test case
Application examples notifies to stubs 30, and waits the feedback of stubs 30.If notifying stubs 30 success, by test case
Request use-case and expectation response use-case notify drive module 20.Stubs 30 can have N number of, and N is the integer more than 1, configures on demand,
Control module 10 can be notified which stubs specific automatically according to type of message.
Drive module 20, for call preset messaging module 40 by encapsulate after request use-case message be sent to by
Survey object, to cause measurand to send the request message of request data support to stubs 30；In the present invention, messaging protocol mould
Block 50 is used for by type of message encapsulation or analysis request use-case or response use-case.After messaging module 40 is used for sending encapsulation
Request use-case and reception response use-case.For example, messaging protocol module 50 encapsulation is derived from request use-case and the stake mould of drive module 20
The response use-case of block；Parsing is derived from request message and the response message of measurand.Messaging module 40 is by messaging protocol mould
The packaged request use-case of block 50 is sent to measurand, or the request message that reception measurand is sent gives messaging protocol mould
Block 50 parses.
Stubs 30, for the request message sending according to measurand, carry out message word to the response use-case after encapsulation
Section adjustment, to meet the needs of measurand service data；
Drive module 20 is additionally operable to receive the response message of measurand, and message call protocol module 50 parses this response and disappears
Breath, with described, it is expected that response use-case message is compared, confirms whether this test case is passed through.
In one embodiment, above-mentioned drive module 20 specifically for：
Message call protocol module 50 encapsulates the request use-case being notified by control module；
Request use-case after encapsulating is sent to measurand by message call communication module 40；
Judge whether to receive the response of measurand.
In one embodiment, above-mentioned stubs 30 specifically for：
Message call protocol module 50 encapsulates the response use-case being notified by control module 10；
Receive the request message of measurand, message call parsing module 50 parses to request message；
Message field adjustment is carried out to the response use-case of original encapsulation, to meet measurand service data needs；
Response use-case after adjustment is responded to measurand.
In one embodiment, control module 10 is additionally operable to：
This test case implementation status is recorded into test log；In the present embodiment, control module 10 also includes testing
Daily record sub-block 12, for real time record test operation daily record, journal formatting is shown on interface, exports final test knot
Fruit daily record.
Check whether that all use-cases are finished, if also test case, transfer next test case, carry out next
Wheel test case is tested automatically；Otherwise, terminate test.
With reference to Fig. 5, it is the workflow diagram of invention software Auto-Test System one embodiment.This stream includes following step
Suddenly：
Step S201, control module 10 transfers the test case being currently needed for executing；
Step S202, the response use-case in test case is notified, to stubs 30, then to wait stake mould by control module 10
The feedback of block 30；Advice method is not limited to function call, Socket notifies etc..If notifying stubs success, enter step
S203, otherwise enters step S204 through step S401.
Step S401, stubs 30 wait control module 10 response use-case to notify, if be successfully received response use-case notifying,
Then enter step 402, feed back to control module 10 simultaneously, step 203 is entered by control module 10；If otherwise notifying unsuccessfully,
Feed back to control module 10, enter step 204, response use-case notice stubs 30 are unsuccessfully not limited to malloc failure malloc, Socket surpasses
When no respond.
Step S203, control module 10 by the request use-case in test case and expects that response use-case notifies drive module
20；
So far, control module 10 completes for this use-case to notify stubs 30 and drive module 20.Stubs 30 and drive
Dynamic model block 20 simultaneously enters awaits orders and driving condition.
Step S301, drive module 20 message call protocol module 50 encapsulates the request use-case being notified by control module 10；
Step S302, it is tested right that the request use-case after encapsulating is sent to by drive module 20 message call communication module 40
As causing measurand built-in function, request message being sent to stubs 30；
Step S303, drive module 20 sends request use-case and finishes, and enters and waits measurand responsive state；
Step S404, stubs 30 receive the request message of measurand, and message call protocol module 50 carries out message
Parsing；
Step S405, stubs 30 according to measurand request message analysis result, to the response use-case after original encapsulation
Carry out necessary message field adjustment, to meet measurand service data needs；
Step S406, the response use-case after adjusting is responded to measurand by stubs 30；
Step S304, drive module 20 judges whether to receive the response of measurand；If received successfully, enter step
Rapid S305, if failure, enters step S306, and reception failure is not limited to receive that message is wrong, measurand is overtime no responds
Deng.
Step S305, drive module 20 is successfully received measurand response message, and message call protocol module 50 parses
Response message, response message and original expectation response use-case being notified by control module 10 is compared, confirms this test
Whether use-case passes through；Subsequently into step 204.
Step S306, drive module 10 receives the failure of measurand response message, and reception failure is not limited to reception message to be had
Mistake, measurand time-out no respond, and enter step S204.
Step S204, this test case implementation status is recorded into test log by control module 10.
Step S205, control module 10 checks whether that all test cases are finished, if also test case, takes off
One test case, returns to step S201 continuation next round test case and automatically tests；Otherwise all test cases have executed
Finish, terminate test.
These are only the preferred embodiments of the present invention, not thereby limit the present invention the scope of the claims, every using this
Equivalent structure or equivalent flow conversion that bright description and accompanying drawing content are made, or directly or indirectly it is used in other related skills
Art field, is included within the scope of the present invention.
Claims (10)
1. a kind of method of software automatic test is it is characterised in that comprise the following steps：
All of test case is preserved in the buffer by control module；Described test case include respond use-case, request use-case and
Expect response use-case, wherein, described response use-case supports that canonical asterisk wildcard compares；
After test starts, control module will respond use-case according to type of message and notify stubs, will ask use-case and expect to ring
Application examples notifies drive module；
Drive module calls preset messaging module the request use-case message after encapsulating to be sent to measurand, to cause
Measurand sends the request message of request data support to stubs；
The request message that stubs send according to measurand, carries out message field adjustment to the response use-case after encapsulation, to accord with
Close the needs of measurand service data；
Drive module receives the response message of measurand, and message call protocol module parses this response message, by its with described
Expect that response use-case message is compared, confirm this test case whether by test.
2. the method for claim 1 it is characterised in that described drive module message call communication module will encapsulate after
Request use-case message is sent to measurand, to cause measurand to send the request message of request data support to stubs bag
Include：
The request use-case that the encapsulation of message call protocol module is notified by control module；
Request use-case after encapsulating is sent to measurand by message call communication module；
Judge whether to receive the response of measurand.
3. the method for claim 1 is it is characterised in that the request message that sent according to measurand of described stubs,
Message field adjustment is carried out to the response use-case after encapsulation, is included with the needs meeting measurand service data：
The response use-case that the encapsulation of message call protocol module is notified by control module；
Receive the request message of measurand, message call protocol module parses to request message；
According to measurand request message analysis result, message field adjustment is carried out to the response use-case after encapsulation, with meet by
Surveying object service data needs；
Response use-case after adjustment is responded to measurand.
4. method as claimed any one in claims 1 to 3 is it is characterised in that also include after executing all steps：
This test case implementation status is recorded into test log by control module；
Control module checks whether that all test cases are finished, if also test case, transfers next test case,
Carry out next round test case automatically to test；Otherwise, terminate test.
5. method as claimed in claim 4 is it is characterised in that described stubs are a plurality of.
6. a kind of system of software automatic test is it is characterised in that include control module, drive module, stubs, message communicating
Module and messaging protocol module, wherein：
Control module, for preserving in the buffer all of test case；Described test case includes responding use-case, request use
Example and expectation response use-case, wherein, described response use-case supports that canonical asterisk wildcard compares；
After test starts, control module will respond use-case according to type of message and notify stubs, will ask use-case and expect to ring
Application examples notifies drive module；
Drive module, for calling preset messaging module that the request use-case message after encapsulating is sent to measurand,
To cause measurand to send the request message of request data support to stubs；
Stubs, for the request message sending according to measurand, carry out message field adjustment to the response use-case after encapsulation,
To meet the needs of measurand service data；
Described drive module is additionally operable to receive the response message of measurand, and message call protocol module parses this response message,
With described, it is expected that response use-case message is compared, confirm whether this test case is passed through.
7. system as claimed in claim 6 it is characterised in that described drive module specifically for：
The request use-case that the encapsulation of message call protocol module is notified by control module；
Request use-case after encapsulating is sent to measurand by message call communication module；
Judge whether to receive the response of measurand.
8. system as claimed in claim 7 it is characterised in that described stubs specifically for：
The response use-case that the encapsulation of message call protocol module is notified by control module；
Receive the request message of measurand, message call parsing module parses to request message；
According to measurand request message analysis result, message field adjustment is carried out to the response use-case after encapsulation, with meet by
Surveying object service data needs；
Response use-case after adjustment is responded to measurand.
9. the system as any one of claim 6 to 8 it is characterised in that described control module specifically for：
Use-case will be responded according to type of message and notify stubs, use-case will be asked and expect that response use-case notifies to drive mould
Block；
This test case implementation status is recorded into test log；
Check whether that all test cases are finished, if also test case, transfer next test case, carry out next
Wheel test case is tested automatically；Otherwise, terminate test.
10. system as claimed in claim 9 is it is characterised in that described stubs are a plurality of.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110168160.3A CN102214140B (en) | 2011-06-21 | 2011-06-21 | Method and system for automatic software testing |
| PCT/CN2012/074697 WO2012174946A1 (en) | 2011-06-21 | 2012-04-25 | Automatic software testing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110168160.3A CN102214140B (en) | 2011-06-21 | 2011-06-21 | Method and system for automatic software testing |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102214140A CN102214140A (en) | 2011-10-12 |
| CN102214140B true CN102214140B (en) | 2017-02-15 |
Family
ID=44745459
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110168160.3A Active CN102214140B (en) | 2011-06-21 | 2011-06-21 | Method and system for automatic software testing |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102214140B (en) |
| WO (1) | WO2012174946A1 (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102214140B (en) * | 2011-06-21 | 2017-02-15 | 中兴通讯股份有限公司 | Method and system for automatic software testing |
| CN104077216B (en) * | 2013-03-28 | 2018-04-27 | 腾讯科技（深圳）有限公司 | Method for testing software and test device |
| CN104683386B (en) * | 2013-11-26 | 2019-01-04 | 腾讯科技（深圳）有限公司 | The stake service implementing method and device of customizable response |
| CN105634838A (en) * | 2014-10-28 | 2016-06-01 | 中兴通讯股份有限公司 | Method, device and system of test for protocol stack table management |
| CN106874176B (en) * | 2015-12-14 | 2021-04-27 | 创新先进技术有限公司 | Intelligent test method and device |
| CN105893249A (en) * | 2015-12-31 | 2016-08-24 | 乐视网信息技术（北京）股份有限公司 | Software testing method and device |
| EP3479248A4 (en) * | 2016-06-29 | 2019-12-18 | Synopsys, Inc. | Automated http user flows simulator |
| CN107870854B (en) * | 2016-09-27 | 2020-06-30 | 北京京东尚科信息技术有限公司 | Method and device for testing data accuracy of chart library |
| CN107908544A (en) * | 2017-08-21 | 2018-04-13 | 中国平安人寿保险股份有限公司 | A kind of use-case test method and terminal device |
| CN110213119B (en) * | 2018-03-07 | 2022-02-22 | 财付通支付科技有限公司 | Test pile generation method, test system, test method and test equipment |
| CN115333984B (en) * | 2022-08-17 | 2023-10-31 | 卡斯柯信号有限公司 | Safety protocol communication performance test system and method |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1735252A (en) * | 2004-08-12 | 2006-02-15 | 华为技术有限公司 | Universal automatization testing device and method |
| CN101620565A (en) * | 2008-07-04 | 2010-01-06 | 福建升腾资讯有限公司 | Method for automatically testing functions of terminal system |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050188275A1 (en) * | 2004-02-03 | 2005-08-25 | Maly John W. | Systems and methods for error tracking and recovery in an expectation-based memory agent checker |
| CN100388229C (en) * | 2005-06-01 | 2008-05-14 | 中兴通讯股份有限公司 | Unit test system and method for automatic generating stub and driving function |
| CN102043716A (en) * | 2010-12-24 | 2011-05-04 | 南京联创科技集团股份有限公司 | Automatic software testing method based on business driving |
| CN102214140B (en) * | 2011-06-21 | 2017-02-15 | 中兴通讯股份有限公司 | Method and system for automatic software testing |
-
2011
- 2011-06-21 CN CN201110168160.3A patent/CN102214140B/en active Active
-
2012
- 2012-04-25 WO PCT/CN2012/074697 patent/WO2012174946A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1735252A (en) * | 2004-08-12 | 2006-02-15 | 华为技术有限公司 | Universal automatization testing device and method |
| CN101620565A (en) * | 2008-07-04 | 2010-01-06 | 福建升腾资讯有限公司 | Method for automatically testing functions of terminal system |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2012174946A1 (en) | 2012-12-27 |
| CN102214140A (en) | 2011-10-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102214140B (en) | Method and system for automatic software testing | |
| US8019333B2 (en) | Apparatus and methods for product acceptance testing on a wireless device | |
| US9538404B2 (en) | Apparatus and methods for product acceptance testing on a wireless device | |
| CN108874677B (en) | Android terminal and test method and system thereof | |
| CN105303112B (en) | The detection method and device of component call loophole | |
| US11340859B2 (en) | Synchronous display method, storage medium and electronic device | |
| CN107241315A (en) | Cut-in method, device and the computer-readable recording medium of bank's gateway interface | |
| CN108920376A (en) | Test method, device and the medium of application program | |
| CN112788128B (en) | Business information pushing method and device, storage medium and electronic device | |
| CN102143523A (en) | Service delivery platform and application testing method based on service delivery platform | |
| CN113778879B (en) | Interface fuzzy test method and device | |
| CN110333713A (en) | Car fault diagnosis method and system | |
| CN112134754A (en) | Pressure testing method and device, network equipment and storage medium | |
| CN107483287B (en) | System and method for automatically monitoring network port data packet receiving and sending faults | |
| CN114500343B (en) | Business chain operation monitoring method and device, equipment, medium and product thereof | |
| CN111858113B (en) | Application program repairing method and device, service system and storage medium | |
| CN107122307B (en) | Internet of things execution system | |
| CN113238935A (en) | Application testing method, system, device, medium, and computer program product | |
| CN110825538A (en) | MQ-based method for dynamically interacting data by self-defining data types | |
| CN113934552A (en) | Method and device for determining function code, storage medium and electronic device | |
| CN106294408B (en) | The method and apparatus that the Asynchronous Request of dynamic web page is monitored | |
| CN102546637A (en) | Communication terminal and method thereof for realizing communication protocol | |
| CN115543491A (en) | Microservice processing method and device | |
| CN112073408A (en) | Monitoring method based on Syslog protocol and Kafka queue | |
| CN117270986A (en) | Page loading method and device, storage medium and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |