CN105938453A - Automatic test method and system - Google Patents
Automatic test method and system Download PDFInfo
- Publication number
- CN105938453A CN105938453A CN201610232057.3A CN201610232057A CN105938453A CN 105938453 A CN105938453 A CN 105938453A CN 201610232057 A CN201610232057 A CN 201610232057A CN 105938453 A CN105938453 A CN 105938453A
- Authority
- CN
- China
- Prior art keywords
- test
- case
- failure information
- document
- failure
- 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
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- 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/3692—Test management for test results analysis
Abstract
The present invention discloses an automatic test method and system, and belongs to the technical field of equipment test. The method comprises receiving use case information; calling at least one corresponding standard test case according to the use case information and operating the test, and outputting a test report; analyzing the test report and recording failure information of all test failure items in a first failure information document; operating the test on all of the test failure items, and recording failure information of all test failure items in a second failure information document; determining whether the test failure items in the second failure information document are identical with the test failure items in the first failure information document; if not, using the second failure information document to cover and update the first failure information document, and then performing retest; and if so, ending the test. The system comprises a use case database, a receiving unit, a calling unit, a test unit, an analysis unit and a determination unit. The technical scheme has the beneficial effects that workload is reduced, period and cost are reduced, and test quality is ensured.
Description
Technical field
The present invention relates to equipment technical field of measurement and test, particularly relate to a kind of automatic test approach and system.
Background technology
In prior art, for the wireless device of SOHO type, its method of testing is usually manual test,
The management personnel of test select testing scheme (case), distribute different test assignments to each test owner
Member, test report is given management personnel after testing and is responsible for integration by each test owner person again.?
The test report integrated eventually is distributed to each test owner person and other related personnel again.So
Test process occupy the longest test period, and the maximum of manual test is limited in that test
Personnel can not test for 24 hours, and the speed that carries out of test depend on tester self state and
Ability.And, the false failure rate of manual test is higher, needs to take the longer time after having tested and enters
Row repetition measurement is with check test result.Management personnel own select testing scheme allocation for test task and whole
The work such as reason test report also can take the longer testing time, thus reduces the test of whole equipment test
Efficiency.And manual test makes the task of each tester heavy, adds the human cost of test.
Summary of the invention
According to the above-mentioned problems in the prior art, now provide the skill of a kind of automatic test approach and system
Art scheme, it is intended to alleviate the workload of tester, shortens test period, reduces testing cost, it is ensured that
Test quality.
Technique scheme specifically includes:
A kind of automatic test approach, it is adaptable to wireless device；Wherein, preset one and include multiple standard
The use-case data base of test case, also includes:
Step S1, receives the use-case information being associated with test case of user input；
Step S2, according to described use-case information, transfers corresponding at least one in described use-case data base
Described standard testing use-case；
Step S3, according to the described standard testing use-case testing results transferred and defeated when test completes
Go out test report；
Step S4, analyzes described test report and the failure information of all test crash items is documented in one
In one failure information document；
Step S5, to all described test crash Xiang Yun being documented in described first failure information document
Row test, and the described failure information of all described test crash items is documented in one second failure information literary composition
In Dang；
Step S6, it is judged that the described test crash item described in described second failure information document and described the
Record in one failure document is the most consistent:
Update if it is not, then cover using described second failure information document as described first failure information document,
It is then returned to described step S5；
The most then terminate test.
Preferably, this automatic test approach, wherein, described use-case information includes:
The use-case label of described test case, or
The use-case title of described test case, or
The set of uses case title of described test case.
Preferably, this automatic test approach, wherein, described step S2 specifically includes:
Step S21, judges the use-case type of the described test case of input according to described use-case information；
Step S22, transfers the described standard in described use-case data base according to described use-case type selecting and surveys
The control command of example on probation；
Step S23, transfers the described standard of correspondence from described use-case data base according to described control command
Test case, is subsequently diverted to described step S3.
Preferably, this automatic test approach, wherein, described failure information includes:
The use-case title of each described test crash item, and
The number of all described test crash item being documented in described first failure information document.
Preferably, this automatic test approach, wherein, in described step S6, if described second unsuccessfully believes
The breath described test crash item described in document is inconsistent with the record in described first failure document, then exist
Cover using described second failure information document as described first failure information document before updating, first hold
Row following step:
The described failure information of inconsistent described test crash item is documented in described second failure information literary composition
In Dang, using as test risk item.
A kind of Auto-Test System, it is adaptable to wireless device；Wherein, including:
Use-case data base, preserves multiple standard testing use-case set in advance；
Receive unit, for receiving the use-case information being associated with test case of user input；
Transfer unit, connect described reception unit and described use-case data base respectively, for according to described use
Example information, transfers at least one described standard testing use-case of correspondence in described use-case data base；
Test cell, transfers unit described in connection, for transporting according to the described standard testing use-case transferred
Row test, and test report is exported when test completes；
Analytic unit, connects described test cell, is used for analyzing described test report and all tests being lost
The failure information losing item is documented in one first failure information document；
Described test cell is additionally operable to all described survey being documented in described first failure information document
Trying unsuccessfully item testing results, described analytic unit is additionally operable to the described failure of all described test crash items
Information is documented in one second failure information document；
Judging unit, connects described analytic unit, is used for judging described in described second failure information document
Described test crash item the most consistent with the record in described first failure document, and export judged result；
Described analytic unit is according to described judged result, in the institute described in described second failure information document
State test crash item with described first failure document in record inconsistent time, with described second failure information
Document covers as described first failure information document and updates, and notifies that described test cell is according to described the
One failure information document reruns test.
Preferably, this Auto-Test System, wherein, described use-case information includes:
The use-case label of described test case, or
The use-case title of described test case, or
The set of uses case title of described test case.
Preferably, this Auto-Test System, wherein, described in transfer unit and specifically include:
Type judging module, for judging the use-case of the described test case of input according to described use-case information
Type；
Command selection module, connects described type judging module, for adjusting according to described use-case type selecting
Take the control command of described standard testing use-case in described use-case data base；
Transfer module, connect described command selection module, be used for according to described control command from described use-case
Data base transfers the described standard testing use-case of correspondence.
Preferably, this Auto-Test System, wherein, described failure information includes:
The use-case title of each described test crash item, and
The number of all described test crash item being documented in described first failure information document.
Preferably, this Auto-Test System, wherein, in the institute described in described second failure information document
State test crash item with described first failure document in record inconsistent time, described analytic unit first will
The described failure information of inconsistent described test crash item is documented in described second failure information document,
Using as test risk item, the most again using described second failure information document as described first failure information
Document covers and updates.
Technique scheme provides the benefit that:
1) a kind of automatic test approach is provided, it is possible to alleviate the workload of tester, shorten test period,
Reduce testing cost, it is ensured that test quality；
2) a kind of Auto-Test System is provided, it would be preferable to support realize above-mentioned automatic test approach.
Accompanying drawing explanation
Fig. 1 is in the preferred embodiment of the present invention, the overall procedure schematic diagram of a kind of automatic test approach；
Fig. 2 is in the preferred embodiment of the present invention, on the basis of Fig. 1, transfers standard testing use-case
Schematic flow sheet；
Fig. 3 is in the preferred embodiment of the present invention, the population structure schematic diagram of a kind of Auto-Test System；
Fig. 4 is in the preferred embodiment of the present invention, on the basis of Fig. 3, transfers the concrete knot of unit
Structure schematic diagram.
Detailed description of the invention
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
Clearly and completely describe, it is clear that described embodiment is only a part of embodiment of the present invention, and
It is not all, of embodiment.Based on the embodiment in the present invention, those of ordinary skill in the art are not making
The every other embodiment obtained on the premise of going out creative work, broadly falls into the scope of protection of the invention.
It should be noted that in the case of not conflicting, the embodiment in the present invention and the spy in embodiment
Levy and can be mutually combined.
The invention will be further described with specific embodiment below in conjunction with the accompanying drawings, but not as the present invention's
Limit.
In the preferred embodiment of the present invention, based on the above-mentioned problems in the prior art, now provide one
Planting automatic test approach, the method is applicable to wireless device, goes for SOHO type further
WIFI equipment.In said method, preset the use-case data including multiple standard testing use-case
Storehouse, and include following step as shown in Figure 1:
Step S1, receives the use-case information being associated with test case of user input；
Step S2, according to use-case information, transfers at least one standard testing of correspondence in use-case data base
Use-case；
Step S3, according to the standard testing use-case testing results transferred, and output is surveyed when test completes
Examination report；
Step S4, analyzes test report and the failure information of all test crash items is documented in one first mistake
Lose in information document；
Step S5, to all test crash item testing results being documented in the first failure information document,
And the failure information of all test crash items is documented in one second failure information document；
Step S6, it is judged that in test crash item described in the second failure information document and the first failure document
Record the most consistent:
Update if it is not, then cover using the second failure information document as the first failure information document, return subsequently
Return step S5；
The most then terminate test.
In a specific embodiment, in the use-case data base of system, first preset multiple standard testings to use
Example, these standard testing use-cases can be tester can according to the proprietary of different test equipment designs
Test case with multiplexing, it is also possible to for tester according to different test equipment designs can be general
And the test case of energy multiplexing.System can be automatically performed test behaviour by calling these standard testing use-cases
Make.
Then in this embodiment, first system receives the use being associated with different test cases of user input
Example information.This use-case information can be the use-case title of test case, or the use-case label of test case,
The even title of the set of uses case at test case place.In other words, in order to ensure the efficiency of test, one
The process of secondary test can arrange multiple test case simultaneously.
In this embodiment, according to above-mentioned use-case information, system can be from the use-case data base preset before
Transfer at least one standard testing use-case corresponding and carry out testing results.Specifically, as mentioned above it is possible, be
System can transfer multiple standard testing use-case according to use-case information before, includes above-mentioned mark forming one
The testing scheme being specifically designed for this test of quasi-test case, and realize by running this testing scheme
This automatic test.
In this embodiment, system is after testing results, and output includes all being test for standard testing
The test report of the test result of use-case, with this test report of post analysis with find including all surveys
Try unsuccessfully item, the failure information of all test crash items is documented in a first failure information document.
Specifically, so-called test crash item, refer to the project of test crash in test case, or test crash
Standard testing use-case.The failure information of so-called test crash item, can include that test crash item is corresponding
The quantity of the test crash item in the use-case title of standard testing use-case, and this test.
In this embodiment, for the first failure information document formed after test the most automatically, according to it
Described in each test crash Xiang Jun carry out repetition measurement, i.e. retest the mark that each test crash item is corresponding
Quasi-test case, and export test report equally.
In this embodiment, for second time test, as mentioned above it is possible, test object is for be documented in before
The standard testing use-case that test crash item in first failure information document is corresponding, then be similarly formed corresponding
Test report, and this test report is analyzed, obtain the test crash item of this test, by its phase
The failure information closed is documented in one second failure information document.
Subsequently, in this embodiment, the first failure information document and the second failure information document are judged,
Particularly as follows:
Judge the test crash item in the first failure information document whether with the survey in the second failure information document
Try unsuccessfully item consistent:
If consistent, then it represents that to need not continue to repetition measurement, directly terminate test and exit flow process.
If inconsistent, then it represents that to need to continue repetition measurement, now need first to be made by the second failure information document
It is the first failure information document storing, i.e. uses the second failure information document to cover the first failure information document
To carry out document renewal, return again to above-mentioned steps S5 subsequently and carry out repetition measurement.In other words, now first
Test crash item described in failure information document is the result after second time test.
In this embodiment, after eventually passing through repeatedly repetition measurement, reach the result that double test crash item is consistent,
Thus verify that this is successfully tested automatically, finish test procedure.
In sum, in technical solution of the present invention, first preset multiple standard testing use-case, basis subsequently
The use-case information of user input determines at least one test case the testing results of these test needs.
The failure information document of the relevant information including test crash item is write after test terminates, and in repetition measurement mistake
Journey being verified in double test, the test crash item described in failure information document is the most consistent: if not
Unanimously, then continue the test crash item to recording and carry out repetition measurement；If consistent, then terminate test.Above-mentioned from
The process of dynamic test can alleviate the workload of tester, shortens test period, reduces testing cost,
And ensure to test quality by the way of repeatedly repetition measurement.
In the preferred embodiment of the present invention, owing to repetition measurement is directed in a front test process appearance
The object of test crash item, i.e. repetition measurement will not once test out existing all test crash items more than front.Cause
This, in the matching process of above-mentioned failure information document, if inconsistent, then directly according to repetition measurement during
The test crash item occurred carries out repetition measurement again, and without paying close attention to the test occurred in a front test process
Failure item.
In the preferred embodiment of the present invention, as in figure 2 it is shown, above-mentioned steps S2 specifically includes:
Step S21, judges the use-case type of the test case of input according to use-case information；
Step S22, transfers the control of standard testing use-case in use-case data base according to use-case type selecting
Order；
Step S23, transfers the standard testing use-case of correspondence from use-case data base according to control command, with
Rear steering step S3.
Specifically, in the preferred embodiment of the present invention, as mentioned above it is possible, once test is involved automatically
And test case may be more, now have only to user and input this automatically test involved by test
The use-case label of use-case, use-case title or set of uses case title, system can be automatically according to above-mentioned use-case
Information judges the use-case type of this standard testing use-case involved by automatic test.Subsequently system according to
Judge that the use-case type selecting obtained transfers the control command of standard testing use-case, and further according to this control
System order is transferred should the standard testing use-case of use-case type to run this automatic from use-case data base
Test.
In the preferred embodiment of the present invention, in step S6, if described in the second failure information document
Test crash item and first failure document in record inconsistent, then using the second failure information document as
First failure information document covers before updating, and following step be first carried out:
The failure information of inconsistent test crash item is documented in the second failure information document, using as
Test risk item.
Specifically, in the preferred embodiment of the present invention, unsuccessfully believe at the first failure information document and second
In the case of breath document is inconsistent, should record in above-mentioned second failure information document:
1) lost by the test being originally documented in the first failure information document of (pass) during repetition measurement
Losing item, these test crash items are recited as testing risk item in the second failure information document, i.e. represent
These projects once test crash mistake, although pass through eventually through repetition measurement, but still be judged as there is wind
Danger, needs to further look at and test.
2) the most failed during repetition measurement test crash item, these test crash items are documented in the second mistake
Lose in information document.
Subsequently, after repetition measurement terminates, this second failure information document is covered as the first failure information document
Update.
In the preferred embodiment of the present invention, above-mentioned automatic test approach is transported based on python design language
OK.So-called python design language, is the computer programming language of a kind of object-oriented, explanation type.
Python has abundant and powerful storehouse, it is possible to the various modules made of other language are the most easily joined
Knot is together.And Python is a kind of language representing simple doctrine thought, and owing to there being comparison simple
Single explanation document, is therefore easier left-hand seat.
Then in a preferred embodiment of the present invention, python design language is used to run above-mentioned automatic survey
Method for testing can be realized by following process:
First, tester fills in the use-case label of test case, or use-case title in systems, or
Person's set of uses case title.The use-case information that system calling logic function if inputs according to tester judges it
Use-case type, the order (control command) of use-case type selecting pybot obtained according to judgement subsequently.
System calls the Popen order in the subprocess module in python subsequently at computer command prompt
Lower input selected pybot order, to select correspondence for above-mentioned use-case type from use-case data base
Standard testing use-case and the test that brings into operation.
After this has been tested automatically, system can generate output file (test report), and adjusts
Open output file with the open order in python, call the search order in re module subsequently
Carry out matching test failure item (fail item), and record the use-case title of test crash item and all surveys
Try the quantity of unsuccessfully item and be saved in the first failure information document.
Subsequently, system calls pybot R order with to the test crash Xiang Yun in above-mentioned output file
Row repetition measurement.New output file is generated after having tested.Similarly, system is called open order and is beaten
Open this newly-generated output file, and call search commands match test crash item and by test crash
Use-case title and the quantity of item are documented in the second failure information document.
Subsequently, two failure information documents are judged by system calling logic function if:
If the test crash item in two failure information documents is consistent, then terminate test；
If the test crash item in two failure information documents is inconsistent, then the survey that will obtain in this repetition measurement
The test crash item trying to obtain during unsuccessfully Xiang Yuqian once tests compares, and to the second failure information literary composition
Shelves do following adjustment: as test risk item, the test crash item passed through in this repetition measurement is documented in second
In failure information document, and test crash item the most unsanctioned in this repetition measurement is unsuccessfully believed as second
Breath test crash item described in document.Subsequently using the second failure information document as the first failure information literary composition
Shelves preserve.
Finally, repetition system is called pybot R order and is lost with the test in the new output file of repetition measurement
Lose item, and carry out above-mentioned judgement and the process of document covering renewal, until in the document of double test
Till the test crash item recorded is consistent.Now can call smtplib and the email module in python
The test case item (test risk item) passed through in repetition measurement and the final test not passing through test are lost
Lose item to fill in mail text, and add journal file and send together to the addressee specified.Above-mentioned
The mode sending test result can also be realized by additive method, is not limited in the mode that mail sends.
In the preferred embodiment of the present invention, based on the above automatic test approach, also provide for one
Planting Auto-Test System, this Auto-Test System is equally applicable to wireless device, is applicable to further
The WIFI equipment of SOHO type.
Then in the preferred embodiment of the present invention, as it is shown on figure 3, above-mentioned Auto-Test System specifically includes:
Use-case data base 1, preserves multiple standard testing use-case set in advance；
Receive unit 2, for receiving the use-case information being associated with test case of user input；
Transfer unit 3, connect respectively and receive unit 2 and use-case data base 1, be used for according to use-case information,
At least one standard testing use-case of correspondence is transferred in use-case data base 1；
Test cell 4, connects and transfers unit 3, is used for according to the standard testing use-case testing results transferred,
And test report is exported when test completes；
Analytic unit 5, connecting test unit 4, for analyzing test report and by all test crash items
Failure information is documented in one first failure information document；
Test cell 4 is additionally operable to all test crash Xiang Yun being documented in the first failure information document
Row test, analytic unit 5 is additionally operable to the failure information of all test crash items is documented in one second failure
In information document；
Judging unit 6, linking parsing unit 5, for judging the test described in the second failure information document
Record in failure item and the first failure document is the most consistent, and exports judged result；
Analytic unit 5 according to judged result, the test crash item described in the second failure information document with
First failure document in record inconsistent time, using the second failure information document as first failure information literary composition
Shelves cover and update, and notify that test cell 4 reruns test according to the first failure information document.
In the preferred embodiment of the present invention, as mentioned above it is possible, above-mentioned use-case information includes: test is used
The use-case label of example, or the use-case title of test case, or the set of uses case title of test case.
In the preferred embodiment of the present invention, as shown in Figure 4, above-mentioned unit 3 of transferring specifically includes:
Type judging module 31, for judging the use-case type of the test case of input according to use-case information；
Command selection module 32, connection type judge module 31, for transferring use according to use-case type selecting
The control command of the standard testing use-case in example data base；
Transferring module 33, bind command selects module 32, is used for according to control command from use-case data base
Transfer the standard testing use-case of correspondence.
In the preferred embodiment of the present invention, as mentioned above it is possible, above-mentioned failure information includes: each survey
Try the use-case title of unsuccessfully item, and all test crash items being documented in the first failure information document
Number.
In the preferred embodiment of the present invention, the test crash item described in the second failure information document with
First failure document in record inconsistent time, analytic unit is first by the mistake of inconsistent test crash item
The information of losing is documented in the second failure information document, using as test risk item, the most again with the second failure
Information document covers as the first failure information document and updates.
In the preferred embodiment of the present invention, above-mentioned Auto-Test System is transported based on python design language
OK.
The foregoing is only preferred embodiment of the present invention, not thereby limit embodiments of the present invention and
Protection domain, to those skilled in the art, it should can appreciate that all utilization description of the invention
And the equivalent done by diagramatic content and the scheme obtained by obvious change, all should comprise
Within the scope of the present invention.
Claims (10)
1. an automatic test approach, it is adaptable to wireless device；It is characterized in that, preset one and include
The use-case data base of multiple standard testing use-cases, also includes:
Step S1, receives the use-case information being associated with test case of user input；
Step S2, according to described use-case information, transfers corresponding at least one in described use-case data base
Described standard testing use-case；
Step S3, according to the described standard testing use-case testing results transferred and defeated when test completes
Go out test report；
Step S4, analyzes described test report and the failure information of all test crash items is documented in one
In one failure information document；
Step S5, to all described test crash Xiang Yun being documented in described first failure information document
Row test, and the described failure information of all described test crash items is documented in one second failure information literary composition
In Dang；
Step S6, it is judged that the described test crash item described in described second failure information document and described the
Record in one failure document is the most consistent:
Update if it is not, then cover using described second failure information document as described first failure information document,
It is then returned to described step S5；
The most then terminate test.
2. automatic test approach as claimed in claim 1, it is characterised in that described use-case information includes:
The use-case label of described test case, or
The use-case title of described test case, or
The set of uses case title of described test case.
3. automatic test approach as claimed in claim 1, it is characterised in that described step S2 is concrete
Including:
Step S21, judges the use-case type of the described test case of input according to described use-case information；
Step S22, transfers the described standard in described use-case data base according to described use-case type selecting and surveys
The control command of example on probation；
Step S23, transfers the described standard of correspondence from described use-case data base according to described control command
Test case, is subsequently diverted to described step S3.
4. automatic test approach as claimed in claim 1, it is characterised in that described failure information includes:
The use-case title of each described test crash item, and
The number of all described test crash item being documented in described first failure information document.
5. automatic test approach as claimed in claim 1, it is characterised in that in described step S6,
If in the described test crash item described in described second failure information document and described first failure document
Record inconsistent, then covering as described first failure information document using described second failure information document
Before renewal, following step it is first carried out:
The described failure information of inconsistent described test crash item is documented in described second failure information literary composition
In Dang, using as test risk item.
6. an Auto-Test System, it is adaptable to wireless device；It is characterized in that, including:
Use-case data base, preserves multiple standard testing use-case set in advance；
Receive unit, for receiving the use-case information being associated with test case of user input；
Transfer unit, connect described reception unit and described use-case data base respectively, for according to described use
Example information, transfers at least one described standard testing use-case of correspondence in described use-case data base；
Test cell, transfers unit described in connection, for transporting according to the described standard testing use-case transferred
Row test, and test report is exported when test completes；
Analytic unit, connects described test cell, is used for analyzing described test report and all tests being lost
The failure information losing item is documented in one first failure information document；
Described test cell is additionally operable to all described survey being documented in described first failure information document
Trying unsuccessfully item testing results, described analytic unit is additionally operable to the described failure of all described test crash items
Information is documented in one second failure information document；
Judging unit, connects described analytic unit, is used for judging described in described second failure information document
Described test crash item the most consistent with the record in described first failure document, and export judged result；
Described analytic unit is according to described judged result, in the institute described in described second failure information document
State test crash item with described first failure document in record inconsistent time, with described second failure information
Document covers as described first failure information document and updates, and notifies that described test cell is according to described the
One failure information document reruns test.
7. Auto-Test System as claimed in claim 6, it is characterised in that described use-case information includes:
The use-case label of described test case, or
The use-case title of described test case, or
The set of uses case title of described test case.
8. Auto-Test System as claimed in claim 6, it is characterised in that described in transfer unit concrete
Including:
Type judging module, for judging the use-case of the described test case of input according to described use-case information
Type；
Command selection module, connects described type judging module, for adjusting according to described use-case type selecting
Take the control command of described standard testing use-case in described use-case data base；
Transfer module, connect described command selection module, be used for according to described control command from described use-case
Data base transfers the described standard testing use-case of correspondence.
9. Auto-Test System as claimed in claim 6, it is characterised in that described failure information includes:
The use-case title of each described test crash item, and
The number of all described test crash item being documented in described first failure information document.
10. Auto-Test System as claimed in claim 6, it is characterised in that in described second failure
When described test crash item described in information document is inconsistent with the record in described first failure document,
First the described failure information of inconsistent described test crash item is documented in described by described analytic unit
In two failure information documents, using as test risk item, make with described second failure information document the most again
Cover for described first failure information document and update.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610232057.3A CN105938453A (en) | 2016-04-14 | 2016-04-14 | Automatic test method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610232057.3A CN105938453A (en) | 2016-04-14 | 2016-04-14 | Automatic test method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105938453A true CN105938453A (en) | 2016-09-14 |
Family
ID=57151376
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610232057.3A Pending CN105938453A (en) | 2016-04-14 | 2016-04-14 | Automatic test method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105938453A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106776273A (en) * | 2016-11-16 | 2017-05-31 | 乐视控股（北京）有限公司 | The method and apparatus of automatic test |
| CN107480053A (en) * | 2017-07-21 | 2017-12-15 | 杭州销冠网络科技有限公司 | A kind of Software Test Data Generation Method and device |
| CN107561379A (en) * | 2017-08-11 | 2018-01-09 | 上海斐讯数据通信技术有限公司 | The method of testing and system of a kind of electronic product |
| CN107632256A (en) * | 2017-08-21 | 2018-01-26 | 上海斐讯数据通信技术有限公司 | A kind of relay stability test method, apparatus and system |
| CN109189672A (en) * | 2018-08-13 | 2019-01-11 | 中国平安人寿保险股份有限公司 | Automatic test approach, server and the computer readable storage medium of micro services |
| CN114978973A (en) * | 2022-05-18 | 2022-08-30 | 宁畅信息产业(北京)有限公司 | Communication interface testing method, device, testing machine and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080115029A1 (en) * | 2006-10-25 | 2008-05-15 | International Business Machines Corporation | iterative test generation and diagnostic method based on modeled and unmodeled faults |
| CN103377123A (en) * | 2012-04-25 | 2013-10-30 | 腾讯科技（深圳）有限公司 | Automatic test method and device for web page codes |
| CN104363324A (en) * | 2014-11-20 | 2015-02-18 | 惠州Tcl移动通信有限公司 | Method and system for carrying out automatic test on mobile phone mainboard |
-
2016
- 2016-04-14 CN CN201610232057.3A patent/CN105938453A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080115029A1 (en) * | 2006-10-25 | 2008-05-15 | International Business Machines Corporation | iterative test generation and diagnostic method based on modeled and unmodeled faults |
| CN103377123A (en) * | 2012-04-25 | 2013-10-30 | 腾讯科技（深圳）有限公司 | Automatic test method and device for web page codes |
| CN104363324A (en) * | 2014-11-20 | 2015-02-18 | 惠州Tcl移动通信有限公司 | Method and system for carrying out automatic test on mobile phone mainboard |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106776273A (en) * | 2016-11-16 | 2017-05-31 | 乐视控股（北京）有限公司 | The method and apparatus of automatic test |
| CN107480053A (en) * | 2017-07-21 | 2017-12-15 | 杭州销冠网络科技有限公司 | A kind of Software Test Data Generation Method and device |
| CN107561379A (en) * | 2017-08-11 | 2018-01-09 | 上海斐讯数据通信技术有限公司 | The method of testing and system of a kind of electronic product |
| CN107632256A (en) * | 2017-08-21 | 2018-01-26 | 上海斐讯数据通信技术有限公司 | A kind of relay stability test method, apparatus and system |
| CN109189672A (en) * | 2018-08-13 | 2019-01-11 | 中国平安人寿保险股份有限公司 | Automatic test approach, server and the computer readable storage medium of micro services |
| CN109189672B (en) * | 2018-08-13 | 2024-03-29 | 中国平安人寿保险股份有限公司 | Automatic testing method for micro-service, server and computer readable storage medium |
| CN114978973A (en) * | 2022-05-18 | 2022-08-30 | 宁畅信息产业(北京)有限公司 | Communication interface testing method, device, testing machine and storage medium |
| CN114978973B (en) * | 2022-05-18 | 2023-05-09 | 宁畅信息产业(北京)有限公司 | Communication interface testing method and device, testing machine and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105938453A (en) | Automatic test method and system | |
| US8214803B2 (en) | Program testing method and testing device | |
| Tosun et al. | Practical considerations in deploying statistical methods for defect prediction: A case study within the Turkish telecommunications industry | |
| CN105335281B (en) | A kind of method and device relied on outside automatic mock | |
| CN106291336A (en) | A kind of FPGA real-time method for down loading of test configurations code stream and system | |
| CN107577599A (en) | A kind of automatic interface testing method and platform based on custom script | |
| CN103186466A (en) | Information interaction device and method based on automatic generation of associated test cases | |
| CN106776273A (en) | The method and apparatus of automatic test | |
| CN109885499B (en) | Robot automatic test system and test method | |
| CN109840206A (en) | Data test method, apparatus, terminal and storage medium | |
| CN104375943A (en) | Embedded software black-box test case generation method based on static models | |
| CN107390056A (en) | Detect the method and system of charging pile | |
| CN108459850A (en) | Generate the method, apparatus and system of test script | |
| CN106547681A (en) | The method and apparatus that data load simultaneously multiplexed analog service testing automatically | |
| CN102810076B (en) | storage medium switching control system and method | |
| CN111428431A (en) | Method and system for supporting automatic test and recording of EDA (electronic design automation) software | |
| CN104794057A (en) | Automatic testing method and device for crossed event | |
| CN103345439B (en) | A kind of full link monitoring method of health state of information system and device | |
| CN106059853A (en) | Network connectivity test method and device | |
| CN110377471A (en) | Generation method, device, storage medium and the electronic equipment of interface check data | |
| CN109473121A (en) | Speech synthesis quality detecting method and device | |
| CN107966648B (en) | A kind of embedded failure diagnosis method based on correlation matrix | |
| CN111930617A (en) | Automatic testing method and device based on data objectification | |
| CN111444051A (en) | Complete machine production testing method and system for product | |
| CN110399304B (en) | Script testing method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | 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: 20160914 |