CN105117345A - Interface testing method and device for application program - Google Patents
Interface testing method and device for application program Download PDFInfo
- Publication number
- CN105117345A CN105117345A CN201510613783.5A CN201510613783A CN105117345A CN 105117345 A CN105117345 A CN 105117345A CN 201510613783 A CN201510613783 A CN 201510613783A CN 105117345 A CN105117345 A CN 105117345A
- Authority
- CN
- China
- Prior art keywords
- interface
- test
- case
- 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, sent by a central control unit, of the application program to be tested is received, wherein the interface testing cases are a subset formed by segmenting all interface testing cases of the application program to be tested through the central control unit; corresponding interfaces are tested through the interface testing cases to obtain testing results; a testing report is generated based on the testing results and returned to the central control unit, and the testing report is received by the central control unit and integrated with other testing reports to form an integral testing report of the application program to be tested, wherein the other testing reports are testing reports which are received by the central control unit and returned after testing is preformed based on other subsets formed by segmenting all the interface testing cases of the application program to be tested. By adopting the embodiment of the interface testing method and device, interface testing efficiency can be effectively 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.Another kind of mode 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, the mode of read test use-case makes testing efficiency low one by one.
The embodiment of the present invention proposes a kind of interface test method and device of application program, effectively can improve the efficiency of interface testing.
The embodiment of the present invention provides a kind of interface test method of application program, comprising:
Receive at least one the interface testing use-case of the application program to be measured that central controller sends; At least one interface testing use-case described is that described central controller is by a subset after whole interface testing use-case cutting of described application program to be measured;
At least one interface testing use-case described is utilized to test corresponding interface, to obtain test result;
Generate test report based on described test result and return to described central controller, described test report is received by described central controller and is integrated into the complete test report of described application program to be measured with other test report; Other test report described be described central controller receive test based on other subsets after whole interface testing use-case cutting of described application program to be measured after the test report that returns.
Further, the formula of cutting is as follows:
Wherein, mod_n is the number of whole interface testing use-case, and N is the number of subset, a
n-1for the number of the interface testing use-case that front N-1 son concentrates each subset cutting to arrive, a
nit is the number of the interface testing use-case that N number of subset cutting is arrived.
Further, described in described utilization, at least one interface testing use-case is tested corresponding interface, to obtain test result, specifically comprises:
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 described test report.
Further, each interface testing use-case all has standardised generic structure.
Accordingly, the embodiment of the present invention also provides a kind of interface test method of application program, comprising:
Be N number of subset by whole interface testing use-case cutting of application program to be measured, and described N number of subset one_to_one corresponding is sent to N number of test lead; Wherein, each described subset comprises at least one interface testing use-case; N >=2;
Receive the test report that described N number of test lead returns, and the test report that the described N number of test lead received returns is integrated into the complete test report of described application program to be measured; Wherein, described test report test lead described in each generates the test result that corresponding interface tests rear acquisition based on utilizing the interface testing use-case in described subset.
Further, the formula of cutting is as follows:
Wherein, mod_n is the number of whole interface testing use-case, and N is the number of subset, a
n-1for the number of the interface testing use-case that front N-1 son concentrates each subset cutting to arrive, a
nit is the number of the interface testing use-case that N number of subset cutting is arrived.
Further, described test report is that test lead described in each divides into groups to the interface testing use-case in described subset according to the logical relation of each interface testing use-case and other interface testing use-cases, and the test result utilizing every group interface test case corresponding interface to be tested to every group interface test case of rear acquisition generates; Wherein, the every group interface test case after grouping is at least one.
Further, each interface testing use-case all has standardised generic structure.
Accordingly, the embodiment of the present invention also provides a kind of interface test device of application program, comprising:
Receiver module, for receiving at least one the interface testing use-case of the application program to be measured that central controller sends; At least one interface testing use-case described is that described central controller is by a subset after whole interface testing use-case cutting of described application program to be measured;
Test module, tests corresponding interface for utilizing at least one interface testing use-case described, to obtain test result; And,
Sending module, return to described central controller for generating test report based on described test result, described test report is received by described central controller and is integrated into the complete test report of described application program to be measured with other test report; Other test report described be described central controller receive test based on other subsets after whole interface testing use-case cutting of described application program to be measured after the test report that returns.
Further, the formula of cutting is as follows:
Wherein, mod_n is the number of whole interface testing use-case, and N is the number of subset, a
n-1for the number of the interface testing use-case that front N-1 son concentrates each subset cutting to arrive, a
nit is the number of the interface testing use-case that N number of subset cutting is arrived.
Further, described test module specifically comprises:
Grouped element, 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 cell, 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:
Comparison 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,
Writing module, for described check result and described database checking data being compared, and writes described test report by comparative result.
Further, each interface testing use-case all has standardised generic structure.
The embodiment of the present invention also provides a kind of interface test device of application program, comprising:
Cutting module, for being N number of subset by whole interface testing use-case cutting of application program to be measured, and sends to N number of test lead by described N number of subset one_to_one corresponding; Wherein, each described subset comprises at least one interface testing use-case; N >=2; And,
Integrate module, for receiving the test report that described N number of test lead returns, and is integrated into the complete test report of described application program to be measured by the test report that the described N number of test lead received returns; Wherein, described test report test lead described in each generates the test result that corresponding interface tests rear acquisition based on utilizing the interface testing use-case in described subset.
Further, the formula of cutting is as follows:
Wherein, mod_n is the number of whole interface testing use-case, and N is the number of subset, a
n-1for the number of the interface testing use-case that front N-1 son concentrates each subset cutting to arrive, a
nit is the number of the interface testing use-case that N number of subset cutting is arrived.
Further, described test report is that test lead described in each divides into groups to the interface testing use-case in described subset according to the logical relation of each interface testing use-case and other interface testing use-cases, and the test result utilizing every group interface test case corresponding interface to be tested to every group interface test case of rear acquisition generates; Wherein, the every group interface test case after grouping is at least one.
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 make central controller that whole interface testing use-cases of application program to be measured are carried out cutting, and send to different test leads to test the subset after cutting simultaneously, effectively improve the testing efficiency of application programming interfaces to be measured; Each test lead is 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 first embodiment of the interface test method of application program provided by the invention;
Fig. 2 is the schematic flow sheet of an embodiment of step S12 in the interface test method of application program provided by the invention;
Fig. 3 is the schematic flow sheet of second embodiment of the interface test method of application program provided by the invention;
Fig. 4 is the structural representation of first embodiment of the interface test device of application program provided by the invention;
Fig. 5 is the structural representation of second embodiment of the interface test device of application program provided by the invention;
Fig. 6 is the structural representation of an embodiment of the interface test system 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:
At least one the interface testing use-case of the application program to be measured that S11, reception central controller send; At least one interface testing use-case described is that described central controller is by a subset after whole interface testing use-case cutting of described application program to be measured;
S12, utilization at least one interface testing use-case described are tested corresponding interface, to obtain test result;
S13, generate test report return to described central controller based on described test result, described test report is received by described central controller and is integrated into the complete test report of described application program to be measured with other test report; Other test report described be described central controller receive test based on other subsets after whole interface testing use-case cutting of described application program to be measured after the test report that returns.
It should be noted that, the enormous amount of the interface testing use-case of an application program, in order to improve the testing efficiency of application programming interfaces, the present embodiment provides a kind of distributed http universalized connection test automation framework, realizes all efficient interface testing robotizations based on http application program.In addition, the interface test method of the application program of the present embodiment is realized by test lead, and multiple test lead is connected with central controller, realizes the quick test of application programs.
Before testing, the interface testing use-case of application program to be measured write by the web platform that tester logs in central controller.After having write, the quantity according to whole interface testing use-cases of application program to be measured carries out cutting, also can carry out cutting according to the module number in application program to be measured, forms multiple subsets of interface testing use-case.Wherein, module refers to program element relatively independent in application program, as log-in module, user management module, Virtual Machine Manager module etc.Then, the subset use-case segmented is transferred to corresponding test lead by central controller respectively, wherein, central controller and multiple test lead set up FTP (FileTransferProtocol, file transfer protocol (FTP)) connect, each test lead receives the subset use-case of central controller transmission by FTP technology, and its subset use-case is downloaded to this locality.After each test lead has subset use-case, the each test lead of central controller controls is tested, and wherein, central controller and each test lead are all provided with IBM open source technology staf framework in advance, and configure mutual trust relation, to realize communicating of central controller and each test lead.
When testing beginning, each test lead reads the interface testing use-case of local application program to be measured, and composition test list, and then fetch interface test case is tested the corresponding interface one by one, obtain its test result, and test result is generated test report, and then test report is uploaded to central controller by FTP mode.After all test leads complete test, the complete test report being integrated into application program to be measured after all test report received is pushed to tester by central controller.
Further, the formula of cutting is as follows:
Wherein, mod_n is the number of whole interface testing use-case, and N is the number of subset, a
n-1for the number of the interface testing use-case that front N-1 son concentrates each subset cutting to arrive, a
nit is the number of the interface testing use-case that N number of subset cutting is arrived.
It should be noted that, the subset number that central controller is syncopated as is identical with the number of test lead, and central controller according to the average cutting of number of whole interface testing use-case, also can carry out cutting according to the module number of application program to be measured.Such as, application program to be measured has 10 modules, and test lead has 3, and so the first two test lead all distributes the interface testing use-case of 3 modules, and last, namely the 3rd test lead distributes the interface testing use-case of 4 modules.After cutting is complete, corresponding for each module interface testing use-case is sent to corresponding test lead by central controller.
Further, as shown in Figure 2, described in described utilization, at least one interface testing use-case is tested corresponding interface, to obtain test result, specifically comprises:
S21, 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;
S22, 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.
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, 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 described 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.
See Fig. 3, be the schematic flow sheet of second embodiment of the interface test method of application program provided by the invention, comprise:
S31, be N number of subset by whole interface testing use-case cutting of application program to be measured, and described N number of subset one_to_one corresponding is sent to N number of test lead; Wherein, each described subset comprises at least one interface testing use-case; N >=2;
S32, receive the test report that described N number of test lead returns, and the test report that the described N number of test lead received returns is integrated into the complete test report of described application program to be measured; Wherein, described test report test lead described in each generates the test result that corresponding interface tests rear acquisition based on utilizing the interface testing use-case in described subset.
Further, the formula of cutting is as follows:
Wherein, mod_n is the number of whole interface testing use-case, and N is the number of subset, a
n-1for the number of the interface testing use-case that front N-1 son concentrates each subset cutting to arrive, a
nit is the number of the interface testing use-case that N number of subset cutting is arrived.
Further, described test report is that test lead described in each divides into groups to the interface testing use-case in described subset according to the logical relation of each interface testing use-case and other interface testing use-cases, and the test result utilizing every group interface test case corresponding interface to be tested to every group interface test case of rear acquisition generates; Wherein, the every group interface test case after grouping is at least one.
Further, each interface testing use-case all has standardised generic structure.
The interface test method of the application program that the embodiment of the present invention provides, can make central controller that whole interface testing use-cases of application program to be measured are carried out cutting, and send to different test leads to test the subset after cutting simultaneously, effectively improve the testing efficiency of application programming interfaces to be measured; Each test lead is 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. 4, be the structural representation of first embodiment of the interface test device of application program provided by the invention, comprise:
Receiver module 41, for receiving at least one the interface testing use-case of the application program to be measured that central controller sends; At least one interface testing use-case described is that described central controller is by a subset after whole interface testing use-case cutting of described application program to be measured;
Test module 42, tests corresponding interface for utilizing at least one interface testing use-case described, to obtain test result; And,
Sending module 43, return to described central controller for generating test report based on described test result, described test report is received by described central controller and is integrated into the complete test report of described application program to be measured with other test report; Other test report described be described central controller receive test based on other subsets after whole interface testing use-case cutting of described application program to be measured after the test report that returns.
Further, the formula of cutting is as follows:
Wherein, mod_n is the number of whole interface testing use-case, and N is the number of subset, a
n-1for the number of the interface testing use-case that front N-1 son concentrates each subset cutting to arrive, a
nit is the number of the interface testing use-case that N number of subset cutting is arrived.
Further, described test module 42 specifically comprises:
Grouped element, 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 cell, 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:
Comparison 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,
Writing module, for described check result and described database checking data being compared, and writes described test report by comparative result.
Further, each interface testing use-case all has standardised generic structure.
See Fig. 5, be the structural representation of second embodiment of the interface test device of application program provided by the invention, comprise:
Cutting module 51, for being N number of subset by whole interface testing use-case cutting of application program to be measured, and sends to N number of test lead by described N number of subset one_to_one corresponding; Wherein, each described subset comprises at least one interface testing use-case; N >=2; And,
Integrate module 52, for receiving the test report that described N number of test lead returns, and is integrated into the complete test report of described application program to be measured by the test report that the described N number of test lead received returns; Wherein, described test report test lead described in each generates the test result that corresponding interface tests rear acquisition based on utilizing the interface testing use-case in described subset.
Further, the formula of cutting is as follows:
Wherein, mod_n is the number of whole interface testing use-case, and N is the number of subset, a
n-1for the number of the interface testing use-case that front N-1 son concentrates each subset cutting to arrive, a
nit is the number of the interface testing use-case that N number of subset cutting is arrived.
Further, described test report is that test lead described in each divides into groups to the interface testing use-case in described subset according to the logical relation of each interface testing use-case and other interface testing use-cases, and the test result utilizing every group interface test case corresponding interface to be tested to every group interface test case of rear acquisition generates; Wherein, the every group interface test case after grouping is at least one.
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 make central controller that whole interface testing use-cases of application program to be measured are carried out cutting, and send to different test leads to test the subset after cutting simultaneously, effectively improve the testing efficiency of application programming interfaces to be measured; Each test lead is 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.
See Fig. 6, it is the structural representation of an embodiment of the interface test system of application program provided by the invention.
The interface test system of the application program that the present embodiment provides comprises central controller 61, first test lead 62, second test lead 63 and the 3rd test lead 64.Wherein, central controller 61 is connected with the first test lead 62, second test lead 63 and the 3rd test lead 64 respectively.Whole interface testing use-case cutting of application program to be measured is 3 subsets by central controller 61, and 3 subsets are sent to the first test lead 62, second test lead 63 and the 3rd test lead 64 respectively, and then control the first test lead 62, second test lead 63 respectively and the 3rd test lead 64 utilizes the subset of its interface testing use-case to carry out interface testing.After the first test lead 62, second test lead 63 and the 3rd test lead 64 are all completed, the test report generated sends to central controller 61, and receive 3 test report are integrated into the complete test report of application program to be measured by central controller 61.The embodiment of the present invention carries out interface testing by central controller by being distributed to multiple test lead after the cutting of whole interface testing use-case simultaneously, effectively improves interface testing efficiency.
It should be noted that, the embodiment of the present invention only comprises a central controller with test macro, and this central controller is that example is described with three test leads respectively, but in the middle of concrete enforcement, test macro can comprise multiple test lead, each test lead is connected with central controller respectively, and the quantity of its test lead can configure according to practical application.
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 (30)
1. an interface test method for application program, is characterized in that, comprising:
Receive at least one the interface testing use-case of the application program to be measured that central controller sends; At least one interface testing use-case described is that described central controller is by a subset after whole interface testing use-case cutting of described application program to be measured;
At least one interface testing use-case described is utilized to test corresponding interface, to obtain test result;
Generate test report based on described test result and return to described central controller, described test report is received by described central controller and is integrated into the complete test report of described application program to be measured with other test report; Other test report described be described central controller receive test based on other subsets after whole interface testing use-case cutting of described application program to be measured after the test report that returns.
2. the interface test method of application program as claimed in claim 1, it is characterized in that, the formula of cutting is as follows:
Wherein, mod_n is the number of whole interface testing use-case, and N is the number of subset, a
n-1for the number of the interface testing use-case that front N-1 son concentrates each subset cutting to arrive, a
nit is the number of the interface testing use-case that N number of subset cutting is arrived.
3. the interface test method of application program as claimed in claim 1, it is characterized in that, described in described utilization, at least one interface testing use-case is tested corresponding interface, to obtain test result, specifically comprises:
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.
4. the interface test method of application program as claimed in claim 3, it is characterized in that, described logical relation comprises stand alone type, and each interface testing use-case independently forms a described grouping.
5. the interface test method of application program as claimed in claim 3, 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.
6. the interface test method of application program as claimed in claim 3, 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.
7. the interface test method of the application program according to any one of claim 3 ~ 6, 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.
8. the interface test method of the application program according to any one of claim 1 ~ 6, 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.
9. the interface test method of application program as claimed in claim 3, 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 described test report.
10. the interface test method of application program as claimed in claim 9, 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 described test report.
The interface test method of 11. application programs as claimed in claim 1, it is characterized in that, each interface testing use-case all has standardised generic structure.
The interface test method of 12. 1 kinds of application programs, is characterized in that, comprising:
Be N number of subset by whole interface testing use-case cutting of application program to be measured, and described N number of subset one_to_one corresponding is sent to N number of test lead; Wherein, each described subset comprises at least one interface testing use-case; N >=2;
Receive the test report that described N number of test lead returns, and the test report that the described N number of test lead received returns is integrated into the complete test report of described application program to be measured; Wherein, described test report test lead described in each generates the test result that corresponding interface tests rear acquisition based on utilizing the interface testing use-case in described subset.
The interface test method of 13. application programs as claimed in claim 12, it is characterized in that, the formula of cutting is as follows:
Wherein, mod_n is the number of whole interface testing use-case, and N is the number of subset, a
n-1for the number of the interface testing use-case that front N-1 son concentrates each subset cutting to arrive, a
nit is the number of the interface testing use-case that N number of subset cutting is arrived.
The interface test method of 14. application programs as claimed in claim 12, it is characterized in that, described test report is that test lead described in each divides into groups to the interface testing use-case in described subset according to the logical relation of each interface testing use-case and other interface testing use-cases, and the test result utilizing every group interface test case corresponding interface to be tested to every group interface test case of rear acquisition generates; Wherein, the every group interface test case after grouping is at least one.
The interface test method of 15. application programs as described in any one of claim 12 to 14, it is characterized in that, each interface testing use-case all has standardised generic structure.
The interface test device of 16. 1 kinds of application programs, is characterized in that, comprising:
Receiver module, for receiving at least one the interface testing use-case of the application program to be measured that central controller sends; At least one interface testing use-case described is that described central controller is by a subset after whole interface testing use-case cutting of described application program to be measured;
Test module, tests corresponding interface for utilizing at least one interface testing use-case described, to obtain test result; And,
Sending module, return to described central controller for generating test report based on described test result, described test report is received by described central controller and is integrated into the complete test report of described application program to be measured with other test report; Other test report described be described central controller receive test based on other subsets after whole interface testing use-case cutting of described application program to be measured after the test report that returns.
The interface test device of 17. application programs as claimed in claim 16, it is characterized in that, the formula of cutting is as follows:
Wherein, mod_n is the number of whole interface testing use-case, and N is the number of subset, a
n-1for the number of the interface testing use-case that front N-1 son concentrates each subset cutting to arrive, a
nit is the number of the interface testing use-case that N number of subset cutting is arrived.
The interface test device of 18. application programs as claimed in claim 16, it is characterized in that, described test module specifically comprises:
Grouped element, 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 cell, 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 19. application programs as claimed in claim 18, 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 20. application programs as claimed in claim 18, 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 21. application programs as claimed in claim 18, 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 22. application programs according to any one of claim 18 ~ 21, 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 23. application programs according to any one of claim 16 ~ 21, 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 24. application programs as claimed in claim 18, is characterized in that, described every group interface test case comprises checking data;
The interface test device of described application program also comprises:
Comparison module, for described test result and described checking data being compared, and writes test report by comparative result.
The interface test device of 25. application programs as claimed in claim 24, 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,
Writing module, for described check result and described database checking data being compared, and writes described test report by comparative result.
The interface test device of 26. application programs as claimed in claim 16, it is characterized in that, each interface testing use-case all has standardised generic structure.
The interface test device of 27. 1 kinds of application programs, is characterized in that, comprising:
Cutting module, for being N number of subset by whole interface testing use-case cutting of application program to be measured, and sends to N number of test lead by described N number of subset one_to_one corresponding; Wherein, each described subset comprises at least one interface testing use-case; N >=2; And,
Integrate module, for receiving the test report that described N number of test lead returns, and is integrated into the complete test report of described application program to be measured by the test report that the described N number of test lead received returns; Wherein, described test report test lead described in each generates the test result that corresponding interface tests rear acquisition based on utilizing the interface testing use-case in described subset.
The interface test device of 28. application programs as claimed in claim 27, it is characterized in that, the formula of cutting is as follows:
Wherein, mod_n is the number of whole interface testing use-case, and N is the number of subset, a
n-1for the number of the interface testing use-case that front N-1 son concentrates each subset cutting to arrive, a
nit is the number of the interface testing use-case that N number of subset cutting is arrived.
The interface test device of 29. application programs as claimed in claim 27, it is characterized in that, described test report is that test lead described in each divides into groups to the interface testing use-case in described subset according to the logical relation of each interface testing use-case and other interface testing use-cases, and the test result utilizing every group interface test case corresponding interface to be tested to every group interface test case of rear acquisition generates; Wherein, the every group interface test case after grouping is at least one.
The interface test device of 30. application programs as described in any one of claim 27 to 29, 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 |
|---|---|---|---|
| CN201510613783.5A CN105117345B (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 |
|---|---|---|---|
| CN201510613783.5A CN105117345B (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 |
|---|---|
| CN105117345A true CN105117345A (en) | 2015-12-02 |
| CN105117345B CN105117345B (en) | 2017-12-19 |
Family
ID=54665343
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510613783.5A Active CN105117345B (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) | CN105117345B (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106528418A (en) * | 2016-10-28 | 2017-03-22 | 广东浪潮大数据研究有限公司 | Test method and device |
| CN107203459A (en) * | 2016-03-16 | 2017-09-26 | 阿里巴巴集团控股有限公司 | Interface performance test method and apparatus |
| CN107688526A (en) * | 2017-08-25 | 2018-02-13 | 上海壹账通金融科技有限公司 | Performance test methods, device, computer equipment and the storage medium of application program |
| CN107861870A (en) * | 2017-11-02 | 2018-03-30 | 平安科技（深圳）有限公司 | Interface testing and test data generating method, device, terminal and storage medium |
| CN109117375A (en) * | 2018-08-30 | 2019-01-01 | 上海携程金融信息服务有限公司 | Database interface test method, system, equipment and storage medium |
| CN109359031A (en) * | 2018-09-04 | 2019-02-19 | 中国平安人寿保险股份有限公司 | More appliance applications test methods, device, server and storage medium |
| CN110083526A (en) * | 2019-03-15 | 2019-08-02 | 深圳壹账通智能科技有限公司 | Applied program testing method, device, computer installation and storage medium |
| CN112162914A (en) * | 2020-07-27 | 2021-01-01 | 上海金融期货信息技术有限公司 | Method and device for automatically generating test case |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101727389A (en) * | 2009-11-23 | 2010-06-09 | 中兴通讯股份有限公司 | Automatic test system and method of distributed integrated service |
| CN102214139A (en) * | 2011-06-01 | 2011-10-12 | 北京航空航天大学 | Automatic test performance control and debugging method facing distributed system |
| CN102609352A (en) * | 2011-01-19 | 2012-07-25 | 阿里巴巴集团控股有限公司 | Parallel testing method and parallel testing server |
| CN103164312A (en) * | 2011-12-09 | 2013-06-19 | 阿里巴巴集团控股有限公司 | Method and system for preparing interface testing data |
| CN103414811A (en) * | 2013-08-09 | 2013-11-27 | 北京中创信测科技股份有限公司 | Method and system for synchronization test of multiple terminals |
| CN103455425A (en) * | 2013-09-25 | 2013-12-18 | 中国银行股份有限公司 | System and method for distributed type tests |
| CN103530231A (en) * | 2013-10-12 | 2014-01-22 | 北京京东尚科信息技术有限公司 | Application program testing method and system based on service process control |
| US20140095934A1 (en) * | 2012-10-02 | 2014-04-03 | International Business Machines Corporation | Test case production utilizing problem reports |
| CN103970650A (en) * | 2014-04-09 | 2014-08-06 | 广州杰赛科技股份有限公司 | Distributed testing method and device |
-
2015
- 2015-09-23 CN CN201510613783.5A patent/CN105117345B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101727389A (en) * | 2009-11-23 | 2010-06-09 | 中兴通讯股份有限公司 | Automatic test system and method of distributed integrated service |
| CN102609352A (en) * | 2011-01-19 | 2012-07-25 | 阿里巴巴集团控股有限公司 | Parallel testing method and parallel testing server |
| 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 |
| US20140095934A1 (en) * | 2012-10-02 | 2014-04-03 | International Business Machines Corporation | Test case production utilizing problem reports |
| CN103414811A (en) * | 2013-08-09 | 2013-11-27 | 北京中创信测科技股份有限公司 | Method and system for synchronization test of multiple terminals |
| CN103455425A (en) * | 2013-09-25 | 2013-12-18 | 中国银行股份有限公司 | System and method for distributed type tests |
| CN103530231A (en) * | 2013-10-12 | 2014-01-22 | 北京京东尚科信息技术有限公司 | Application program testing method and system based on service process control |
| CN103970650A (en) * | 2014-04-09 | 2014-08-06 | 广州杰赛科技股份有限公司 | Distributed testing method and device |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107203459A (en) * | 2016-03-16 | 2017-09-26 | 阿里巴巴集团控股有限公司 | Interface performance test method and apparatus |
| 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 |
| CN107688526A (en) * | 2017-08-25 | 2018-02-13 | 上海壹账通金融科技有限公司 | Performance test methods, device, computer equipment and the storage medium of application program |
| CN107861870A (en) * | 2017-11-02 | 2018-03-30 | 平安科技（深圳）有限公司 | Interface testing and test data generating method, device, terminal and storage medium |
| CN109117375A (en) * | 2018-08-30 | 2019-01-01 | 上海携程金融信息服务有限公司 | Database interface test method, system, equipment and storage medium |
| CN109359031A (en) * | 2018-09-04 | 2019-02-19 | 中国平安人寿保险股份有限公司 | More appliance applications test methods, device, server and storage medium |
| CN109359031B (en) * | 2018-09-04 | 2023-08-22 | 中国平安人寿保险股份有限公司 | Multi-device application program testing method and device, server and storage medium |
| CN110083526A (en) * | 2019-03-15 | 2019-08-02 | 深圳壹账通智能科技有限公司 | Applied program testing method, device, computer installation and storage medium |
| CN112162914A (en) * | 2020-07-27 | 2021-01-01 | 上海金融期货信息技术有限公司 | Method and device for automatically generating test case |
| CN112162914B (en) * | 2020-07-27 | 2024-06-04 | 上海金融期货信息技术有限公司 | Method and device for automatically generating test cases |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105117345B (en) | 2017-12-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105117345A (en) | Interface testing method and device for application program | |
| CN105138461A (en) | Interface testing method and device for application program | |
| CN103150238B (en) | A kind of service request processing method, simulated performance method of testing and device | |
| CN102946616B (en) | Internet of things middleware performance testing system and testing method | |
| CN106095673A (en) | Automated testing method based on WEB interface and system | |
| CN104407971A (en) | Method for automatically testing embedded software | |
| CN104363324B (en) | A kind of method of testing and test system tested automatically cell phone mainboard | |
| CN104636254A (en) | Method and device for generating test case, testing method and testing equipment | |
| CN108347356B (en) | Multi-protocol unit testing method and device, electronic equipment and storage medium | |
| 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 | |
| CN101888318A (en) | System and method for testing performance index of communication system | |
| CN109542794A (en) | A kind of Software Automatic Testing Method applied to embedded system | |
| CN110248349A (en) | Search table method, apparatus, electronic equipment and system | |
| CN116107893A (en) | Heterogeneous platform embedded software test verification system and method | |
| CN111813655A (en) | Embedded point testing method and device, embedded point management system and storage medium | |
| CN106201864A (en) | A kind of application programming interface API method of testing, device and mobile device | |
| CN110149241A (en) | A kind of automated testing method and storage medium based on IMS equipment | |
| RU2532714C2 (en) | Method of acquiring data when evaluating network resources and apparatus therefor | |
| CN103457957B (en) | A kind of network penetration test macro and method with adaptation function | |
| CN110413468A (en) | The online fault filling method of FPGA based on code mutation | |
| CN111290937A (en) | Extensible mobile application automatic test platform based on hybrid cloud | |
| CN103019927B (en) | A kind of performance test methods and system | |
| CN115470108A (en) | Gateway route testing method and device for vehicle, electronic equipment and storage medium | |
| CN114416561A (en) | Pressure test configuration method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |