CN105138461A - Interface testing method and device for application program - Google Patents
Interface testing method and device for application program Download PDFInfo
- Publication number
- CN105138461A CN105138461A CN201510613781.6A CN201510613781A CN105138461A CN 105138461 A CN105138461 A CN 105138461A CN 201510613781 A CN201510613781 A CN 201510613781A CN 105138461 A CN105138461 A CN 105138461A
- Authority
- CN
- China
- Prior art keywords
- interface
- case
- test
- testing use
- interface testing
- 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.)
- Granted
Links
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention discloses an interface testing method and device for an application program. The interface testing method for the application program includes the steps that at least one interface testing case of the application program to be tested is acquired; grouping is conducted on the at least one interface testing case according to the logical relation between each interface testing case and other interface testing cases, and each group of interface testing cases comprises at least one testing case after grouping is completed; the corresponding interfaces are tested through each group of interface testing cases, so that testing results of each group of interface testing cases are acquired. By the adoption of the method and device, complex interface testing can be carried out, and interface testing accuracy is improved.
Description
Technical field
The present invention relates to field of computer technology, particularly relate to a kind of interface test method and device of application program.
Background technology
Along with software engineering development, more and more software turns to user by platform provides service, and third party can provide interface to customize according to platform oneself needs service, and therefore nowadays software often relates to interface testing.Interface is some predefined functions, and object is to provide application program and developer is able to the ability of access one group of routine based on certain software or hardware, and without the need to accessing source code, or understand the details of internal work mechanism.Interface testing submits input data to interface, and acquisition returns results also analysis result and whether meets the test of expection.Various system command, testing tool may be related to, even programming technique in interface testing.
At present, interface automatic test has two kinds of modes substantially.First kind of way is that each test case is encapsulated as function, then realizes the robotization of interface function test by calling this function.The second way whole test case is encapsulated in a file, then automatized script one by one read test use-case complete interface testing.
Two kinds of update modes that background technology is mentioned all can realize the interface testing of application program, but each Shortcomings, for the first test mode, if test case has hundreds of bar even several thousand, the automatized script of interface testing is very huge, the at substantial time is needed to write test case, and, once interface variation, also very large to the change amount of test case, meanwhile, tester needs to spend the plenty of time to learn the realization of each function.For test mode in second, read test use-case can not realize complicated interface testing one by one.
The embodiment of the present invention proposes a kind of interface test method and device of application program, can realize complicated interface testing, improves the accuracy of interface testing.
The embodiment of the present invention provides a kind of interface test method of application program, comprising:
Obtain at least one interface testing use-case of application program to be measured;
According to the logical relation of each interface testing use-case and other interface testing use-cases, at least one interface testing use-case described is divided into groups, makes the every group interface test case after grouping be at least one;
Every group interface test case is utilized to test corresponding interface, to obtain the test result of every group interface test case.
In one preferably embodiment, described logical relation comprises stand alone type, and each interface testing use-case independently forms a described grouping.
In another preferably embodiment, described logical relation comprises laddering, multiple described interface testing use-case with group is arranged in order, if the Output rusults utilizing each interface testing use-case to test corresponding interface is all consistent with the expectation value of this interface testing use-case, then as the input parameter utilizing next interface testing use-case to test corresponding interface, and using the Output rusults that utilizes last interface testing use-case to test the corresponding interface test result as this group interface test case.
In another preferably embodiment, described logical relation comprises block form, multiple described interface testing use-case with group is arranged in order to be performed and tests corresponding interface, and using the Output rusults that utilizes last interface testing use-case to test the corresponding interface test result as this group interface test case.
Further, each interface testing use-case comprises use-case type, is confirmed the logical relation of each interface testing use-case and other interface testing use-cases by described use-case type.
Further, each interface testing use-case comprises interface identification code, utilizes each interface testing use-case to test the interface corresponding to the interface identification code of this interface testing use-case.
Further, described every group interface test case comprises checking data;
After the test result of the every group interface test case of described acquisition, also comprise:
Described test result and described checking data are compared, and comparative result is write test report.
Further, after the test result of the every group interface test case of described acquisition, also comprise:
When a group interface test case also comprises database statement identification code and database checking data, from the database statement template set up in advance, inquiry obtains the corresponding database statement of described database statement identification code;
According to described database statement, database is checked, obtain the check result of described database;
Described check result and described database checking data are compared, and comparative result is write test report.
Further, each interface testing use-case all has standardised generic structure.
Accordingly, the embodiment of the present invention also comprises a kind of interface test device of application program, comprising:
Interface testing use-case acquisition module, for obtaining at least one interface testing use-case of application program to be measured;
Grouping module, for the logical relation according to each interface testing use-case and other interface testing use-cases, divides into groups at least one interface testing use-case described, makes the every group interface test case after grouping be at least one; And,
Test module, for utilizing every group interface test case to test corresponding interface, to obtain the test result of every group interface test case.
In one preferably embodiment, described logical relation comprises stand alone type, and each interface testing use-case independently forms a described grouping.
In another preferably embodiment, described logical relation comprises laddering, multiple described interface testing use-case with group is arranged in order, if the Output rusults utilizing each interface testing use-case to test corresponding interface is all consistent with the expectation value of this interface testing use-case, then as the input parameter utilizing next interface testing use-case to test corresponding interface, and using the Output rusults that utilizes last interface testing use-case to test the corresponding interface test result as this group interface test case.
In another preferably embodiment, described logical relation comprises block form, multiple described interface testing use-case with group is arranged in order to be performed and tests corresponding interface, and using the Output rusults that utilizes last interface testing use-case to test the corresponding interface test result as this group interface test case.
Further, each interface testing use-case comprises use-case type, is confirmed the logical relation of each interface testing use-case and other interface testing use-cases by described use-case type.
Further, each interface testing use-case comprises interface identification code, utilizes each interface testing use-case to test the interface corresponding to the interface identification code of this interface testing use-case.
Further, described every group interface test case comprises checking data;
The interface test device of described application program also comprises:
Correction verification module, for described test result and described checking data being compared, and writes test report by comparative result.
Further, the interface test device of described application program also comprises:
Enquiry module, for when a group interface test case also comprises database statement identification code and database checking data, from the database statement template set up in advance, inquiry obtains the corresponding database statement of described database statement identification code;
Checking module, for checking database according to described database statement, obtains the check result of described database; And,
Comparison module, for described check result and described database checking data being compared, and writes test report by comparative result.
Further, each interface testing use-case all has standardised generic structure.
Implement the embodiment of the present invention, there is following beneficial effect:
The interface test method of the application program that the embodiment of the present invention provides and device, can according to the logical relation between interface testing use-case, the interface testing use-case of application program to be measured is divided into groups, and according to every group interface test case, the corresponding interface is tested, to realize complicated interface testing, improve the accuracy of interface testing; The interface testing use-case with progressive relationship is divided into one group, realize the interface testing of Output rusults as the input parameter of next interface of an interface, the interface testing use-case with coordination is divided into one group, realize the interface testing that multiple interface testing use-case exports a test result, make interface testing more comprehensive and accurate; After a test, database result is checked, improve the accuracy of test; Each interface testing use-case all has standardised generic structure, makes interface testing use-case be applied to different application programs, improves the applicability of interface testing use-case.
Summary of the invention
Accompanying drawing explanation
Fig. 1 is the schematic flow sheet of an embodiment of the interface test method of application program provided by the invention;
Fig. 2 is the part run schematic diagram of another embodiment of the interface test method of application program provided by the invention;
Fig. 3 is the structural representation of an embodiment of the interface test device of application program provided by the invention;
Fig. 4 is the part-structure schematic diagram of another embodiment of the interface test device of application program provided by the invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, be clearly and completely described the technical scheme in the embodiment of the present invention, obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.
See Fig. 1, be the schematic flow sheet of an embodiment of the interface test method of application program provided by the invention, comprise:
S1, obtain at least one interface testing use-case of application program to be measured;
S2, logical relation according to each interface testing use-case and other interface testing use-cases, divide into groups at least one interface testing use-case described, make the every group interface test case after grouping be at least one;
S3, every group interface test case is utilized to test corresponding interface, to obtain the test result of every group interface test case.
It should be noted that, after the interface testing use-case obtaining application program to be measured, the interface testing use-case of application program to be measured is divided into groups, the interface testing use-case with logical relation is made to be one group, thus according to every group interface test case, corresponding interface is tested, and obtain the corresponding test result of every group interface test case, thus realize complicated interface testing, to improve the accuracy of test.
In one preferably embodiment, described logical relation comprises stand alone type, and each interface testing use-case independently forms a described grouping.
If an interface testing use-case and other interface testing use-cases are freestanding logical relation, then this interface testing use-case is independently divided into one group.When testing, this interface testing use-case is utilized to test corresponding interface, to obtain the test result of this interface testing use-case.
In another preferably embodiment, described logical relation comprises laddering, multiple described interface testing use-case with group is arranged in order, if the Output rusults utilizing each interface testing use-case to test corresponding interface is all consistent with the expectation value of this interface testing use-case, then as the input parameter utilizing next interface testing use-case to test corresponding interface, and using the Output rusults that utilizes last interface testing use-case to test the corresponding interface test result as this group interface test case.
If multiple interface testing use-case has laddering logical relation, then described multiple interface testing use-case is divided into one group, and is arranged in order according to progressive relationship.When testing, each interface testing use-case of this group is utilized to carry out interface testing one by one according to putting in order.Wherein, complete and obtain after this connects the Output rusults returned to corresponding interface testing at an interface testing use-case, expectation value in this Output rusults and this interface testing use-case is compared, if Output rusults is consistent with expectation value, then this Output rusults is cached in cache, when utilizing next interface testing use-case to test, from buffer memory cache, obtain this Output rusults proceed test as the input parameter of next interface testing use-case, and after utilizing last interface testing use-case of this group to test corresponding interface, the Output rusults returned by this interface is as the test result of this group interface test case, if Output rusults and expectation value inconsistent, then terminate the test of this group.
Such as, first interface test case and the second interface testing use-case with progressive relationship are divided into one group.First interface test case is first utilized to test corresponding first interface, obtain the Output rusults that first interface returns, the expectation value of the Output rusults returned by first interface and first interface test case compares, if this Output rusults is identical with expectation value, then this Output rusults is cached in cache, when utilizing the second interface testing use-case to test, from buffer memory cache, obtain this Output rusults test corresponding second interface as the input parameter of the second interface testing use-case, obtain Output rusults that the second interface the returns test result as this group, if the Output rusults that first interface returns and expectation value are not identical, then terminate the test of this group.
In another preferably embodiment, described logical relation comprises block form, multiple described interface testing use-case with group is arranged in order to be performed and tests corresponding interface, and using the Output rusults that utilizes last interface testing use-case to test the corresponding interface test result as this group interface test case.
If multiple interface testing use-cases have the logical relation of block form, then described multiple interface testing use-case is divided into one group, and logically order is arranged in order.When testing, each interface testing use-case of this group is utilized to carry out interface testing one by one according to putting in order.Wherein, after utilizing an interface testing use-case to test corresponding interface, without the need to the Output rusults checking this interface to return, continue to utilize next interface testing use-case to test corresponding interface.After utilizing last interface testing use-case of this group to test corresponding interface, obtain Output rusults that this interface the returns test result as this group.
Further, each interface testing use-case comprises use-case type, is confirmed the logical relation of each interface testing use-case and other interface testing use-cases by described use-case type.
It should be noted that, after the interface testing use-case obtaining application program to be measured, interface testing use-case is added in test list, and then resolve the interface testing use-case in test list one by one, with the grouping of mouthful test case that achieves a butt joint.If the type of interface testing use-case is separate type, then this interface testing use-case is divided into alone one group; If the type of multiple interface testing use-cases adjacent in test list is type of going forward one by one, then described multiple interface testing use-case is divided into one group, and according to putting in order in test list multiple interface testing use-cases of this group is arranged; If the type of multiple interface testing use-cases adjacent in test list is parallel-type, then described multiple interface testing use-case is divided into one group, and according to putting in order in test list multiple interface testing use-cases of this group is arranged.
Further, each interface testing use-case comprises interface identification code, utilizes each interface testing use-case to test the interface corresponding to the interface identification code of this interface testing use-case.
Wherein, interface identification code is the unique identifier of interface.Interface identification code according to interface testing use-case can ask corresponding interface, realizes the test to this interface.
Further, described every group interface test case comprises checking data;
After the test result of the every group interface test case of described acquisition, also comprise:
Described test result and described checking data are compared, and comparative result is write test report.
It should be noted that, after utilizing every group interface test case to carry out interface testing, also need to verify the test result of every group interface test case.Wherein, the checking data carrying out verifying is present in last interface testing use-case of every group interface test case, and checking data comprises check field and proof test value.From test result, obtain the corresponding test data of described check field, and judge that whether this test data is identical with proof test value, if identical, then this test result is correct, if not identical, then this test result mistake, and by correct or wrong comparative result write test report.
Further, as shown in Figure 2, after the test result of the every group interface test case of described acquisition, also comprise:
S21, when a group interface test case also comprises database statement identification code and database checking data, from the database statement template set up in advance inquiry obtain the corresponding database statement of described database statement identification code;
S22, according to described database statement, database to be checked, obtain the check result of described database;
S23, described check result and described database checking data to be compared, and comparative result is write test report.
It should be noted that, part of interface test also needs to verify database, when a group interface test case also comprises database statement identification code and database checking data, also need to verify database according to database statement identification code and database checking data.Wherein, database statement identification code and database checking data are present in last interface testing use-case of every group interface test case, and database checking data comprises database check field and database proof test value.The database statement first finding database statement identification code corresponding from the database statement template set up in advance, and then according to this database statement, database is checked, to obtain check result.From this check result, obtain database check field check data accordingly, and judge that whether these inspection data are identical with database proof test value, if identical, then the check result of database is correct, if not identical, the then check result mistake of database, and by correct or wrong comparative result write test report.
Further, each interface testing use-case all has standardised generic structure.
It should be noted that, each interface testing use-case all adopts standardised generic structure to write, such as, the compiling form of each interface testing use-case is { ' name ': ' interface testing use-case name ', ' group ': ' use-case type ', ' url ': ' interface identification code ', ' method ': ' method of testing ', ' args ': { ' input parameter ' }, ' ret ': { ' equal ': { ' expectation value/checking data ' }, ' mysql ': { ' database statement identification code and database checking data ' } } }.
As group=0, the logical relation of this interface testing use-case is stand alone type.When utilizing this interface testing use-case to carry out interface testing, the corresponding interface of request interface identification code, to this interface input parameter, and adopts the method for testing in use-case to test this interface.After the test result that this interface of acquisition returns, according to the checking data in use-case, test result is verified.If ' mysql ' field has data in use-case, then according to database statement identification code and database checking data, database is verified; If in use-case, ' mysql ' field is empty, then without the need to verifying database.
As group=1, the second interface testing use-case of this first interface test case and next group=-1 is divided into one group, and its logical relation is laddering.After utilizing first interface test case to test corresponding first interface, the expectation value in the Output rusults return this first interface and use-case compares.When comparative result is consistent, this Output rusults is cached in cache, when utilizing the second interface testing use-case to test, from buffer memory cache, obtains this Output rusults as the input parameter of the second interface testing use-case, corresponding second interface is tested.After the test result that acquisition second interface returns, according to the checking data in the second interface testing use-case, test result is verified.If ' mysql ' field has data in the second interface testing use-case, then according to database statement identification code and database checking data, database is verified; If in the second interface testing use-case, ' mysql ' field is empty, then without the need to verifying database.
As group=m, m interface testing use-case is divided into one group, its logical relation is block form.Wherein, the group in m interface testing use-case is m, m >=2.Each interface testing use-case is utilized to test corresponding interface one by one, after utilizing m interface testing use-case to carry out interface testing, obtain the test result that this interface returns, and according to the checking data in m interface testing use-case, test result is verified.If ' mysql ' field has data in m interface testing use-case, then according to database statement identification code and database checking data, database is verified; If in m interface testing use-case, ' mysql ' field is empty, then without the need to verifying database.
The interface test method of the application program that the embodiment of the present invention provides, can according to the logical relation between interface testing use-case, the interface testing use-case of application program to be measured is divided into groups, and according to every group interface test case, the corresponding interface is tested, to realize complicated interface testing, improve the accuracy of interface testing; The interface testing use-case with progressive relationship is divided into one group, realize the interface testing of Output rusults as the input parameter of next interface of an interface, the interface testing use-case with coordination is divided into one group, realize the interface testing that multiple interface testing use-case exports a test result, make interface testing more comprehensive and accurate; After a test, database result is checked, improve the accuracy of test; Each interface testing use-case all has standardised generic structure, makes interface testing use-case be applied to different application programs, improves the applicability of interface testing use-case.
Accordingly, the present invention also provides a kind of interface test device of application program, can realize all flow processs of the interface test method of the application program in above-described embodiment.
See Fig. 3, be the structural representation of an embodiment of the interface test device of application program provided by the invention, comprise:
Interface testing use-case acquisition module 1, for obtaining at least one interface testing use-case of application program to be measured;
Grouping module 2, for the logical relation according to each interface testing use-case and other interface testing use-cases, divides into groups at least one interface testing use-case described, makes the every group interface test case after grouping be at least one; And,
Test module 3, for utilizing every group interface test case to test corresponding interface, to obtain the test result of every group interface test case.
In one preferably embodiment, described logical relation comprises stand alone type, and each interface testing use-case independently forms a described grouping.
In another preferably embodiment, described logical relation comprises laddering, multiple described interface testing use-case with group is arranged in order, if the Output rusults utilizing each interface testing use-case to test corresponding interface is all consistent with the expectation value of this interface testing use-case, then as the input parameter utilizing next interface testing use-case to test corresponding interface, and using the Output rusults that utilizes last interface testing use-case to test the corresponding interface test result as this group interface test case.
In another preferably embodiment, described logical relation comprises block form, multiple described interface testing use-case with group is arranged in order to be performed and tests corresponding interface, and using the Output rusults that utilizes last interface testing use-case to test the corresponding interface test result as this group interface test case.
Further, each interface testing use-case comprises use-case type, is confirmed the logical relation of each interface testing use-case and other interface testing use-cases by described use-case type.
Further, each interface testing use-case comprises interface identification code, utilizes each interface testing use-case to test the interface corresponding to the interface identification code of this interface testing use-case.
Further, described every group interface test case comprises checking data;
The interface test device of described application program also comprises:
Correction verification module, for described test result and described checking data being compared, and writes test report by comparative result.
Further, as shown in Figure 4, the interface test device of described application program also comprises:
Enquiry module 41, for when a group interface test case also comprises database statement identification code and database checking data, from the database statement template set up in advance, inquiry obtains the corresponding database statement of described database statement identification code;
Checking module 42, for checking database according to described database statement, obtains the check result of described database; And,
Comparison module 43, for described check result and described database checking data being compared, and writes test report by comparative result.
Further, each interface testing use-case all has standardised generic structure.
The interface test device of the application program that the embodiment of the present invention provides, can according to the logical relation between interface testing use-case, the interface testing use-case of application program to be measured is divided into groups, and according to every group interface test case, the corresponding interface is tested, to realize complicated interface testing, improve the accuracy of interface testing; The interface testing use-case with progressive relationship is divided into one group, realize the interface testing of Output rusults as the input parameter of next interface of an interface, the interface testing use-case with coordination is divided into one group, realize the interface testing that multiple interface testing use-case exports a test result, make interface testing more comprehensive and accurate; After a test, database result is checked, improve the accuracy of test; Each interface testing use-case all has standardised generic structure, makes interface testing use-case be applied to different application programs, improves the applicability of interface testing use-case.
The above is the preferred embodiment of the present invention; it should be pointed out that for those skilled in the art, under the premise without departing from the principles of the invention; can also make some improvements and modifications, these improvements and modifications are also considered as protection scope of the present invention.
Claims (18)
1. an interface test method for application program, is characterized in that, comprising:
Obtain at least one interface testing use-case of application program to be measured;
According to the logical relation of each interface testing use-case and other interface testing use-cases, at least one interface testing use-case described is divided into groups, makes the every group interface test case after grouping be at least one;
Every group interface test case is utilized to test corresponding interface, to obtain the test result of every group interface test case.
2. the interface test method of application program as claimed in claim 1, it is characterized in that, described logical relation comprises stand alone type, and each interface testing use-case independently forms a described grouping.
3. the interface test method of application program as claimed in claim 1, it is characterized in that, described logical relation comprises laddering, multiple described interface testing use-case with group is arranged in order, if the Output rusults utilizing each interface testing use-case to test corresponding interface is all consistent with the expectation value of this interface testing use-case, then as the input parameter utilizing next interface testing use-case to test corresponding interface, and using the Output rusults that utilizes last interface testing use-case to test the corresponding interface test result as this group interface test case.
4. the interface test method of application program as claimed in claim 1, it is characterized in that, described logical relation comprises block form, multiple described interface testing use-case with group is arranged in order to be performed and tests corresponding interface, and using the Output rusults that utilizes last interface testing use-case to test the corresponding interface test result as this group interface test case.
5. the interface test method of the application program according to any one of Claims 1 to 4, it is characterized in that, each interface testing use-case comprises use-case type, is confirmed the logical relation of each interface testing use-case and other interface testing use-cases by described use-case type.
6. the interface test method of the application program according to any one of Claims 1 to 4, it is characterized in that, each interface testing use-case comprises interface identification code, utilizes each interface testing use-case to test the interface corresponding to the interface identification code of this interface testing use-case.
7. the interface test method of application program as claimed in claim 1, it is characterized in that, described every group interface test case comprises checking data;
After the test result of the every group interface test case of described acquisition, also comprise:
Described test result and described checking data are compared, and comparative result is write test report.
8. the interface test method of application program as claimed in claim 1, is characterized in that, after the test result of the every group interface test case of described acquisition, also comprise:
When a group interface test case also comprises database statement identification code and database checking data, from the database statement template set up in advance, inquiry obtains the corresponding database statement of described database statement identification code;
According to described database statement, database is checked, obtain the check result of described database;
Described check result and described database checking data are compared, and comparative result is write test report.
9. the interface test method of application program as claimed in claim 1, it is characterized in that, each interface testing use-case all has standardised generic structure.
10. an interface test device for application program, is characterized in that, comprising:
Interface testing use-case acquisition module, for obtaining at least one interface testing use-case of application program to be measured;
Grouping module, for the logical relation according to each interface testing use-case and other interface testing use-cases, divides into groups at least one interface testing use-case described, makes the every group interface test case after grouping be at least one; And,
Test module, for utilizing every group interface test case to test corresponding interface, to obtain the test result of every group interface test case.
The interface test device of 11. application programs as claimed in claim 10, it is characterized in that, described logical relation comprises stand alone type, and each interface testing use-case independently forms a described grouping.
The interface test device of 12. application programs as claimed in claim 10, it is characterized in that, described logical relation comprises laddering, multiple described interface testing use-case with group is arranged in order, if the Output rusults utilizing each interface testing use-case to test corresponding interface is all consistent with the expectation value of this interface testing use-case, then as the input parameter utilizing next interface testing use-case to test corresponding interface, and using the Output rusults that utilizes last interface testing use-case to test the corresponding interface test result as this group interface test case.
The interface test device of 13. application programs as claimed in claim 10, it is characterized in that, described logical relation comprises block form, multiple described interface testing use-case with group is arranged in order to be performed and tests corresponding interface, and using the Output rusults that utilizes last interface testing use-case to test the corresponding interface test result as this group interface test case.
The interface test device of 14. application programs according to any one of claim 10 ~ 13, it is characterized in that, each interface testing use-case comprises use-case type, is confirmed the logical relation of each interface testing use-case and other interface testing use-cases by described use-case type.
The interface test device of 15. application programs according to any one of claim 10 ~ 13, it is characterized in that, each interface testing use-case comprises interface identification code, utilizes each interface testing use-case to test the interface corresponding to the interface identification code of this interface testing use-case.
The interface test device of 16. application programs as claimed in claim 10, is characterized in that, described every group interface test case comprises checking data;
The interface test device of described application program also comprises:
Correction verification module, for described test result and described checking data being compared, and writes test report by comparative result.
The interface test device of 17. application programs as claimed in claim 10, it is characterized in that, the interface test device of described application program also comprises:
Enquiry module, for when a group interface test case also comprises database statement identification code and database checking data, from the database statement template set up in advance, inquiry obtains the corresponding database statement of described database statement identification code;
Checking module, for checking database according to described database statement, obtains the check result of described database; And,
Comparison module, for described check result and described database checking data being compared, and writes test report by comparative result.
The interface test device of 18. application programs as claimed in claim 10, it is characterized in that, each interface testing use-case all has standardised generic structure.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510613781.6A CN105138461B (en) | 2015-09-23 | 2015-09-23 | The interface test method and device of a kind of application program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510613781.6A CN105138461B (en) | 2015-09-23 | 2015-09-23 | The interface test method and device of a kind of application program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105138461A true CN105138461A (en) | 2015-12-09 |
| CN105138461B CN105138461B (en) | 2018-01-26 |
Family
ID=54723815
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510613781.6A Active CN105138461B (en) | 2015-09-23 | 2015-09-23 | The interface test method and device of a kind of application program |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105138461B (en) |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106528418A (en) * | 2016-10-28 | 2017-03-22 | 广东浪潮大数据研究有限公司 | Test method and device |
| CN106776334A (en) * | 2016-12-28 | 2017-05-31 | 北京奇虎科技有限公司 | Based on annotation generation method of test example and device |
| CN107329861A (en) * | 2017-06-12 | 2017-11-07 | 北京奇安信科技有限公司 | A kind of multiplex roles method of testing and device |
| CN107423211A (en) * | 2017-03-15 | 2017-12-01 | 中国互联网络信息中心 | A kind of SDNS interfaces automatization test system and method |
| CN107436844A (en) * | 2017-07-07 | 2017-12-05 | 北京奇安信科技有限公司 | A kind of generation method and device of interface use-case intersection |
| CN107977308A (en) * | 2016-10-25 | 2018-05-01 | 传化物流集团有限公司 | interface test method and device |
| CN108572610A (en) * | 2017-03-13 | 2018-09-25 | 欧姆龙株式会社 | Evaluation system, safety governor, medium capable of reading record and evaluation method |
| CN108959065A (en) * | 2018-05-17 | 2018-12-07 | 烽火通信科技股份有限公司 | The verification method and system of software interface test parameter |
| CN109522211A (en) * | 2018-09-29 | 2019-03-26 | 中国平安人寿保险股份有限公司 | Interface parameters transmission method, device, electronic equipment and storage medium |
| WO2019085087A1 (en) * | 2017-11-02 | 2019-05-09 | 平安科技（深圳）有限公司 | Interface testing and test data generation method, device, terminal, and storage medium |
| CN111163067A (en) * | 2019-12-18 | 2020-05-15 | 支付宝(杭州)信息技术有限公司 | Safety testing method and device and electronic equipment |
| CN111752821A (en) * | 2019-03-29 | 2020-10-09 | 上海哔哩哔哩科技有限公司 | Method and device for packet pressure measurement, computer equipment and readable storage medium |
| CN112559356A (en) * | 2020-12-18 | 2021-03-26 | 杭州兑吧网络科技有限公司 | Automatic software testing method and system |
| CN117033253A (en) * | 2023-10-10 | 2023-11-10 | 北京轻松怡康信息技术有限公司 | Interface testing method and device, electronic equipment and storage medium |
| CN111752821B (en) * | 2019-03-29 | 2024-06-04 | 上海哔哩哔哩科技有限公司 | Method, device, computer equipment and readable storage medium for packet pressure measurement |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1632747A (en) * | 2003-12-22 | 2005-06-29 | 联想(北京)有限公司 | Software interface testing method |
| US20110231709A1 (en) * | 2010-03-19 | 2011-09-22 | Nagravision S.A. | Method for checking data consistency in a system on chip |
| CN102214139A (en) * | 2011-06-01 | 2011-10-12 | 北京航空航天大学 | Automatic test performance control and debugging method facing distributed system |
| CN103164312A (en) * | 2011-12-09 | 2013-06-19 | 阿里巴巴集团控股有限公司 | Method and system for preparing interface testing data |
-
2015
- 2015-09-23 CN CN201510613781.6A patent/CN105138461B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1632747A (en) * | 2003-12-22 | 2005-06-29 | 联想(北京)有限公司 | Software interface testing method |
| US20110231709A1 (en) * | 2010-03-19 | 2011-09-22 | Nagravision S.A. | Method for checking data consistency in a system on chip |
| CN102214139A (en) * | 2011-06-01 | 2011-10-12 | 北京航空航天大学 | Automatic test performance control and debugging method facing distributed system |
| CN103164312A (en) * | 2011-12-09 | 2013-06-19 | 阿里巴巴集团控股有限公司 | Method and system for preparing interface testing data |
Cited By (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107977308A (en) * | 2016-10-25 | 2018-05-01 | 传化物流集团有限公司 | interface test method and device |
| CN106528418A (en) * | 2016-10-28 | 2017-03-22 | 广东浪潮大数据研究有限公司 | Test method and device |
| CN106528418B (en) * | 2016-10-28 | 2019-01-22 | 广东浪潮大数据研究有限公司 | A kind of test method and device |
| CN106776334A (en) * | 2016-12-28 | 2017-05-31 | 北京奇虎科技有限公司 | Based on annotation generation method of test example and device |
| CN106776334B (en) * | 2016-12-28 | 2021-03-23 | 北京奇虎科技有限公司 | Comment-based test case generation method and device |
| CN108572610B (en) * | 2017-03-13 | 2021-05-18 | 欧姆龙株式会社 | Evaluation system, security controller, readable recording medium, and evaluation method |
| CN108572610A (en) * | 2017-03-13 | 2018-09-25 | 欧姆龙株式会社 | Evaluation system, safety governor, medium capable of reading record and evaluation method |
| CN107423211B (en) * | 2017-03-15 | 2020-03-13 | 中国互联网络信息中心 | SDNS interface automatic test system and method |
| CN107423211A (en) * | 2017-03-15 | 2017-12-01 | 中国互联网络信息中心 | A kind of SDNS interfaces automatization test system and method |
| CN107329861B (en) * | 2017-06-12 | 2020-12-22 | 奇安信科技集团股份有限公司 | Multi-interface testing method and device |
| CN107329861A (en) * | 2017-06-12 | 2017-11-07 | 北京奇安信科技有限公司 | A kind of multiplex roles method of testing and device |
| CN107436844B (en) * | 2017-07-07 | 2020-07-14 | 奇安信科技集团股份有限公司 | Method and device for generating interface use case aggregate |
| CN107436844A (en) * | 2017-07-07 | 2017-12-05 | 北京奇安信科技有限公司 | A kind of generation method and device of interface use-case intersection |
| WO2019085087A1 (en) * | 2017-11-02 | 2019-05-09 | 平安科技（深圳）有限公司 | Interface testing and test data generation method, device, terminal, and storage medium |
| CN108959065A (en) * | 2018-05-17 | 2018-12-07 | 烽火通信科技股份有限公司 | The verification method and system of software interface test parameter |
| CN109522211A (en) * | 2018-09-29 | 2019-03-26 | 中国平安人寿保险股份有限公司 | Interface parameters transmission method, device, electronic equipment and storage medium |
| CN111752821A (en) * | 2019-03-29 | 2020-10-09 | 上海哔哩哔哩科技有限公司 | Method and device for packet pressure measurement, computer equipment and readable storage medium |
| CN111752821B (en) * | 2019-03-29 | 2024-06-04 | 上海哔哩哔哩科技有限公司 | Method, device, computer equipment and readable storage medium for packet pressure measurement |
| CN111163067A (en) * | 2019-12-18 | 2020-05-15 | 支付宝(杭州)信息技术有限公司 | Safety testing method and device and electronic equipment |
| CN111163067B (en) * | 2019-12-18 | 2022-05-03 | 支付宝(杭州)信息技术有限公司 | Safety testing method and device and electronic equipment |
| CN112559356A (en) * | 2020-12-18 | 2021-03-26 | 杭州兑吧网络科技有限公司 | Automatic software testing method and system |
| CN117033253A (en) * | 2023-10-10 | 2023-11-10 | 北京轻松怡康信息技术有限公司 | Interface testing method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105138461B (en) | 2018-01-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105138461A (en) | Interface testing method and device for application program | |
| CN107665171B (en) | Automatic regression testing method and device | |
| CN105279090A (en) | Test script generating method and test script generating device applied in financial field | |
| US20130290075A1 (en) | Localization quality assurance of localized software | |
| CN105117345A (en) | Interface testing method and device for application program | |
| CN102236600B (en) | Method and device for obtaining code coverage rate | |
| CN105930242B (en) | A kind of multi-core processor random verification method and device for supporting accurate memory access detection | |
| CN108446223B (en) | Business scene automatic testing method based on dynamic compilation | |
| CN111522728A (en) | Method for generating automatic test case, electronic device and readable storage medium | |
| CN105117341A (en) | Distributed automatic test case generation method based on dynamic symbolic execution | |
| CN107729238A (en) | A kind of plug-in unit adjustment method, system, device and computer-readable recording medium | |
| CN110764998A (en) | Data comparison method, device and equipment based on Django framework and storage medium | |
| CN105279092A (en) | Software testing method and apparatus | |
| CN107451058A (en) | A kind of software development methodology and device | |
| CN109684204A (en) | A kind of http interface automatic test approach | |
| CN110750434A (en) | Interface testing method and device, electronic equipment and computer readable storage medium | |
| CN102981946A (en) | Extract Transform and Load (ETL) smoke test method | |
| CN101739340A (en) | Method and device for verifying script file | |
| CN113220597B (en) | Test method, test device, electronic equipment and storage medium | |
| CN115470125B (en) | Log file-based debugging method, device and storage medium | |
| CN115827636B (en) | Method for storing and reading simulation data of logic system design from waveform database | |
| WO2014174362A1 (en) | Feature model based testing | |
| CN101673200A (en) | Method and device for detecting user input model | |
| CN116860608A (en) | Interface testing method and device, computing equipment and storage medium | |
| CN114238143A (en) | ES data number making method, system and storage medium for interface test |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |