CN110083537B - Method and system for testing APP port of mobile phone - Google Patents
Method and system for testing APP port of mobile phone Download PDFInfo
- Publication number
- CN110083537B CN110083537B CN201910344706.2A CN201910344706A CN110083537B CN 110083537 B CN110083537 B CN 110083537B CN 201910344706 A CN201910344706 A CN 201910344706A CN 110083537 B CN110083537 B CN 110083537B
- Authority
- CN
- China
- Prior art keywords
- test
- priority
- module
- interface
- machine
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
S1, obtaining an interface document of each APP, and converting the interface document into a standard document through a data standardization module, wherein each interface in the standard document corresponds to a plurality of sub-items, and when data corresponding to the sub-items are not found in the interface document, the value of the sub-item is marked as null. By setting different priorities, the filling of the rest data is completed while the test is performed, and the waiting time between the interface tests of the two priorities is shortened. The test case distribution module realizes the dispatching and the use of a plurality of test machines, so that the calculation efficiency is maximized, and the time of the whole test task is further shortened. After all interface tests are completed, verification tests are carried out by using different machines, so that errors of test results caused by configuration environments, performance and network fluctuation of the machines can be avoided.
Description
Technical Field
The invention relates to the field of software testing, in particular to a method and a system for testing an APP port of a mobile phone.
Background
Interface testing is a test that tests interfaces between components of a system. Interface testing is mainly used for detecting interaction points between external systems and between internal subsystems. The focus of the test is to check if the business logic meets the business requirements, check if the field is normal and if the actual results meet expectations. Most of the existing test methods are used for manually testing all interfaces by test staff through test tools, but when a plurality of programs are required to be tested simultaneously, the manpower requirement is high, and when the number of the test staff is small, a plurality of test devices cannot be operated simultaneously, so that the performance of the test devices cannot be fully utilized, and the test efficiency is reduced.
Disclosure of Invention
In order to solve the technical problems, the invention aims to provide a method and a system for testing an APP port of a mobile phone.
The technical problems to be solved by the invention are as follows:
(1) How to maximize the use of all test equipment when operated by a single person to improve the efficiency of simultaneous testing of multiple programs.
(2) How to avoid testing errors caused by testing machine differences.
The aim of the invention can be achieved by the following technical scheme:
the method for testing the APP port of the mobile phone comprises the following specific steps:
s1, acquiring an interface document of each APP, and converting the interface document into a standard document through a data standardization module, wherein each interface in the standard document corresponds to a plurality of sub-items, and when data corresponding to the sub-items are not found in the interface document, marking the value of the sub-item as null;
s2, counting the number N of subitems with the median null in all the interfaces corresponding to all the subitems by a priority ordering module, and ordering the priorities according to the size of N, wherein the smaller the value of N is, the higher the priority is, wherein the interfaces with the n=0 are marked as a first priority, and the interfaces with the number 0< N are marked as a second priority;
s3, screening out standard documents corresponding to all interfaces with the second priority by the priority ordering module, taking the standard documents as documents to be supplemented, sending the documents to be supplemented to a developer through the network module, reminding the developer to fill in data in the standard documents, and sending the data back to the priority ordering module after the completion of filling in;
s4, after determining the interfaces of the first priority, the test case distribution module associates at least one corresponding test case with each interface of the first priority according to a standard document, counts the number m of all the test cases and the number n of machines used for testing, numbers the machines, distributes m/n test cases to each machine, wherein if m/n is a non-integer, the integer part is taken, and distributes redundant test cases to the machines with the number 1;
s5, after receiving the test cases, an interface test module in the machine changes the running state of the machine into a test, marks all the test cases as incomplete and packages the test cases into a file to be tested, reads the test cases in the file to be tested one by one through an automatic script, marks the test cases as completed when finishing one test case, sends a test report containing the number of the tested machine and the test result to a test statistics module after finishing the interface test, and changes the running state of the machine into idle;
s6, after testing is completed on all interfaces with the first priority, screening out interfaces with the number of subitems of 0 in the subitems of null corresponding to the interfaces with the second priority by the priority sorting module, and re-marking the interfaces with the first priority, and executing the steps S3-S5 again until testing of all the interfaces is completed;
s7, screening out test cases which do not reach expectations according to the test report by the test statistics module, acquiring a machine number i of the test cases for testing, wherein i is less than n, distributing the test cases to a machine with the division number i through the test case distribution module, performing verification test through the interface test module, and making a verification test report, if the verification test report does not reach expectations, marking the test cases and the corresponding interfaces as abnormal by the test statistics module, acquiring all the test cases marked as abnormal and the corresponding interfaces, and generating an abnormal form.
Further, in S1, the sub-items of the standard document include an interface description, a call url, a request method, a request parameter, a parameter type, and a request parameter description.
Further, in S5, after the running state of the machine becomes idle, the remaining running states are that the machine under test sends the number q of incomplete test cases to the test case allocation module, the machine with the largest number q of incomplete test cases is screened out, and the number q/2 of incomplete test cases are allocated to the machine with the idle running state for continuing the test until all the test cases corresponding to the interfaces of the first priority are completely tested.
Further, in S4, the method for numbering the machine includes:
SS1, performing running division on the performances of all machines through the same software;
SS2, numbering according to the score of the running score, wherein the higher the score is, the lower the numbering is.
The mobile phone APP port test system comprises a plurality of machines for testing and a total control subsystem for controlling, wherein the total control subsystem comprises a man-machine interaction module, a data standardization module, a priority ordering module, a test case allocation module, a test statistics module and a network module for transmitting data, and the machine comprises an interface test module and a network module for transmitting data;
the man-machine interaction module is used for importing an interface document of the APP and displaying an abnormal form;
the data standardization module is used for converting all the APP interface documents into a plurality of sub-item standard documents;
the priority ordering module divides the interface into a first priority and a second priority according to the data in the standard document, the first priority is tested in priority, and the second priority is tested after the data are supplemented;
the test case distribution module distributes test cases to all machines according to the number m of the test cases corresponding to all the interfaces of the first priority and the number n of the machines used for testing, and distributes the test cases which do not reach the expected conditions to all the machines during verification testing;
the interface test module is used for marking all the test cases as incomplete and packaging the test cases into a file to be tested after receiving the test cases, reading the test cases in the file to be tested one by one through an automatic script, and sending a test report containing the machine number and the test result of the test to the test statistics module after completing the interface test;
the test statistics module is used for counting the test cases which do not reach the expectations and generating an abnormal form.
Further, the sub-items of the standard document comprise interface description, called url, request method, request parameters, parameter types and request parameter description, when the data of the corresponding sub-item is not found in the interface document, the value of the sub-item is marked as null, the priority ranking module ranks the priorities according to the number N of the sub-items with the null in the sub-items, the interface with the n=0 is marked as a first priority, and the interface with the value 0< N is marked as a second priority.
Furthermore, the test case distribution module associates at least one corresponding test case with each interface of the first priority according to the standard document, counts the number m of all the test cases and the number n of the machines for testing, runs the performance of all the machines through the same software, numbers the machines according to the score of the running, numbers the higher the score, the lower the number, distributes m/n test cases to each machine after numbering the machines, wherein if m/n is a non-integer, the integer part is taken, and redundant test cases are distributed to the machines with the number 1.
Further, after the interface test module receives the test cases, changing the running state of the machine into a test, marking as finished when one test case is finished, after the running state of the machine becomes idle, sending the number q of the incomplete test cases to the test case distribution module by the machine with the rest running states in the test, screening out the machine with the largest number q of the incomplete test cases, distributing the number q/2 of the incomplete test cases to the machine with the idle running state, continuing to test until all the test cases corresponding to the interfaces with the first priority are finished, screening out the interfaces with the number 0 of the subitems with the null corresponding to the interfaces with the second priority by the priority sorting module after the interfaces with the first priority are finished, and re-marking as the first priority, and executing the step of the interface test with the first priority again until the test of all the interfaces is finished.
Further, the test statistics module screens out test cases which do not reach expectations according to the test report, obtains the machine number i of the test cases for testing, wherein i < n, distributes the test cases to the machine with the division number i through the test case distribution module, performs verification test through the interface test module, and makes a verification test report, if the verification test report does not reach expectations, the test statistics module marks the test cases and the corresponding interfaces as abnormal, obtains all the test cases marked as abnormal and the corresponding interfaces, and generates an abnormal form.
The invention has the beneficial effects that:
(1) The interface documents of a plurality of programs are analyzed and processed through the master control subsystem, standardization of the interface documents is achieved, basis is provided for priority setting, and by setting different priorities, the test progress is not delayed when the rest data are completed, so that time is strived for the test of the low-priority interface, and waiting time between the interface tests of the two priorities is shortened.
(2) The test case distribution module realizes the dispatching and the use of a plurality of machines for testing, so that the most machines for remaining incomplete test cases can be separated into a part, the calculation pressure is shared, the plurality of machines can be ensured to finish the test simultaneously after the adjustment for a plurality of times, the calculation efficiency is maximized, meanwhile, the working intensity of a tester is reduced, and only the test result is needed to be checked, thereby shortening the time of the whole test task.
(3) After all interface tests are completed, verification tests are carried out by using different machines, so that errors of test results caused by configuration environments, performance and network fluctuation of the machines can be avoided.
Drawings
The invention is further described below with reference to the accompanying drawings.
Fig. 1 is a system block diagram of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The embodiment provides a method for testing an APP port of a mobile phone, which comprises the following specific steps:
s1, acquiring an interface document of each APP, and converting the interface document into a standard document through a data standardization module, wherein each interface in the standard document corresponds to a plurality of sub-items, and when data corresponding to the sub-items are not found in the interface document, marking the value of the sub-item as null; the sub-items of the standard document include interface description, call url, request method, request parameters, parameter type, request parameter description. When testing multiple software simultaneously, since developers are not usually in the same batch, interface documents of each software may have differences, so that the interface documents need to be sorted to form a standard format and unfilled data is counted.
S2, counting the number N of subitems with the median null in all the interfaces corresponding to all the subitems by a priority ordering module, and ordering the priorities according to the size of N, wherein the smaller the value of N is, the higher the priority is, wherein the interfaces with the n=0 are marked as a first priority, and the interfaces with the number 0< N are marked as a second priority; the fewer the number N of the subitems with the value null, the more complete the data of the interface is, and the test can be ensured to be carried out.
S3, screening out standard documents corresponding to all interfaces with the second priority by the priority ordering module, taking the standard documents as documents to be supplemented, sending the documents to be supplemented to a developer through the network module, reminding the developer to fill in data in the standard documents, and sending the data back to the priority ordering module after the completion of filling in; the interfaces with complete data are tested in priority, and the missing data in the interfaces with the second priority are complemented in the time of testing the interfaces with the first priority, so that the data can be complemented without delaying the progress.
S4, after determining the interfaces of the first priority, the test case distribution module associates at least one corresponding test case with each interface of the first priority according to a standard document, wherein the test cases can be obtained through writing by technicians and imported to the test case distribution module, or can be automatically generated by using software, the number m of all the test cases and the number n of machines used for testing are counted, m/n test cases are distributed to each machine after numbering the machines, if m/n is a non-integer, the integer part is taken, and redundant test cases are distributed to the machines with the number 1; the numbering method of the machine comprises the following steps:
SS1, performing running division on the performances of all machines through the same software;
SS2, numbering according to the score of the running score, wherein the higher the score is, the lower the numbering is.
All the test cases are distributed uniformly as much as possible, and redundant test cases are distributed to the machine with the strongest performance, so that the test time can be reduced.
S5, after receiving test cases, an interface test module in the machine changes the running state of the machine into a test, marks all the test cases as incomplete and packages the test cases into a file to be tested, reads the test cases in the file to be tested one by one through an automatic script, marks the test cases as completed when each test case is completed, realizes automatic test, and is completed automatically by the machine without being attended by personnel, and only needs to be checked after a result is obtained, and after interface test is completed, sends a test report containing the number of the tested machine and the test result to a test statistics module and changes the running state of the machine into idle; after the running state of the machine is changed to be idle, the other running states are that the machine under test sends the quantity q of the incomplete test cases to the test case distribution module, the machine with the largest quantity q of the incomplete test cases is screened out, the quantity q/2 of the incomplete test cases are distributed to the machine with the idle running state, and the test is continued until all the test cases corresponding to the interfaces with the first priority are completely tested. Because of the difference of machine performance, some machines can complete testing first, and the idle state is very wasteful of computing resources after completion, so that the machine with the largest number of remaining incomplete test cases can be separated into a part to share computing pressure, and after multiple adjustments, a plurality of machines can be ensured to complete testing simultaneously, and further the testing is completed in advance.
S6, after testing is completed on all interfaces with the first priority, screening out interfaces with the number of subitems of 0 in the subitems of null corresponding to the interfaces with the second priority by the priority sorting module, and re-marking the interfaces with the first priority, and executing the steps S3-S5 again until testing of all the interfaces is completed; if the interface is still not filled with data before the expiration date, the interface is manually tested, after the test is completed, the second priority of the data which is filled with the data is screened out, the data is lifted to the first priority, the test is performed again, the time for filling the data is strived for through the first test, the calculation efficiency of the machine is maximized, and the test time is shortened.
S7, screening out the test cases which do not reach the expectations according to the test report by the test statistics module, obtaining the machine number i of the test cases for testing, wherein i is less than n, distributing the test cases to the machine with the division number i through the test case distribution module, carrying out verification test through the interface test module, and making a verification test report, if the verification test report does not reach the expectations, marking the test cases and the corresponding interfaces as abnormal by the test statistics module, obtaining all the test cases marked as abnormal and the corresponding interfaces, and generating an abnormal form. By using different machines to carry out verification test, errors of test results caused by configuration environment, performance and network fluctuation of the machines can be avoided, and if the two test results are not expected, non-hardware reasons are described, so that interface abnormality is judged.
Referring to fig. 1, the embodiment further provides a mobile phone APP port test system, which includes a plurality of machines for testing, and a master control subsystem for controlling, wherein the master control subsystem includes a man-machine interaction module, a data standardization module, a priority ordering module, a test case allocation module, a test statistics module, and a network module for transmitting data, and the machine includes an interface test module and a network module for transmitting data;
the man-machine interaction module is used for importing an interface document of the APP and displaying an abnormal form; a touch display or the like may be employed.
The data standardization module is used for converting all the interface documents of the APP into a plurality of sub-item standard documents; when testing multiple software simultaneously, since developers are not usually in the same batch, interface documents of each software may have differences, so that the interface documents need to be sorted to form a standard format and unfilled data is counted.
The priority ordering module divides the interface into a first priority and a second priority according to the data in the standard document, the first priority is tested in priority, and the second priority is tested after the data are supplemented; the interfaces with complete data are tested in priority, and the missing data in the interfaces with the second priority are complemented in the time of testing the interfaces with the first priority, so that the data can be complemented without delaying the progress.
The test case distribution module distributes the test cases to each machine according to the number m of the test cases corresponding to all the interfaces of the first priority and the number n of the machines used for testing, and distributes the test cases which do not reach the expected conditions to each machine during verification testing; the test cases can be obtained through writing by technicians and imported into the test case distribution module, automatic generation can be performed by using software, all the test cases can be distributed uniformly as much as possible, redundant test cases can be distributed to the machine with the strongest performance, and the test time can be reduced.
The interface test module is used for marking all the test cases as unfinished and packaging the test cases into a file to be tested after receiving the test cases, reading the test cases in the file to be tested one by one through an automatic script, and sending a test report containing the machine number and the test result of the test to the test statistics module after completing the interface test.
The test statistics module is used for counting the test cases which do not reach the expectations and generating an abnormal form.
The sub-items of the standard document comprise interface description, called url, request method, request parameters, parameter types and request parameter description, when the data of the corresponding sub-items are not found in the interface document, the value of the sub-item is marked as null, the priority ranking module ranks the priorities according to the number N of the sub-items with the value null in the sub-items, the interfaces with N=0 are marked as first priorities, and the interfaces with the value 0< N are marked as second priorities.
The test case distribution module associates at least one corresponding test case with each interface of the first priority according to the standard document, counts the number m of all the test cases and the number n of the machines for testing, runs the performance of all the machines through the same software, numbers the machines according to the score of the running, numbers the higher the score, the lower the number, distributes m/n test cases to each machine after numbering the machines, wherein if m/n is a non-integer, the integer part is taken, and redundant test cases are distributed to the machines with the number 1.
After receiving the test cases, the interface test module changes the running state of the machine into a test, marks that one test case is finished every time the running state of the machine is finished, after the running state of the machine is changed into idle, the other running states of the machine in the test send the number q of the incomplete test cases to the test case distribution module, screens out the machine with the largest number q of the incomplete test cases, distributes the number q/2 of the incomplete test cases to the machine with the idle running state to continue the test until all the test cases corresponding to the interfaces with the first priority finish the test, and after the interfaces with the first priority finish the test, the priority ordering module screens out the interfaces with the number 0 in the subitems null corresponding to the interfaces with the second priority, and re-marks the interfaces with the first priority, and executes the step of the interface test with the first priority again until the test of all the interfaces is finished. Because of the difference of machine performance, some machines can complete testing first, and the idle state is very wasteful of computing resources after completion, so that the machine with the largest number of remaining incomplete test cases can be separated into a part to share computing pressure, and after multiple adjustments, a plurality of machines can be ensured to complete testing simultaneously, and further the testing is completed in advance.
The test statistics module screens out the test cases which do not reach the expectations according to the test report, obtains the machine number i of the test cases for testing, wherein i is less than n, distributes the test cases to the machine with the division number i through the test case distribution module, performs verification test through the interface test module, and makes a verification test report, if the verification test report does not reach the expectations, the test statistics module marks the test cases and the corresponding interfaces as abnormal, obtains all the test cases marked as abnormal and the corresponding interfaces, and generates an abnormal form. By using different machines to carry out verification test, errors of test results caused by configuration environment, performance and network fluctuation of the machines can be avoided, and if the two test results are not expected, non-hardware reasons are described, so that interface abnormality is judged.
The interface documents of a plurality of programs are analyzed and processed through the master control subsystem, standardization of the interface documents is achieved, basis is provided for priority setting, and by setting different priorities, the test progress is not delayed when the rest data are completed, so that time is strived for the test of the low-priority interface, and waiting time between the interface tests of the two priorities is shortened. The test case distribution module realizes the dispatching and the use of a plurality of machines for testing, so that the most machines with the rest incomplete test cases can be separated into a part, the calculation pressure is shared, and after the multiple times of adjustment, the plurality of machines can be ensured to finish the test at the same time, the calculation efficiency is maximized, and the time of the whole test task is further shortened. After all interface tests are completed, verification tests are carried out by using different machines, so that errors of test results caused by configuration environments, performance and network fluctuation of the machines can be avoided.
Claims (9)
1. The method for testing the APP port of the mobile phone is characterized by comprising the following specific steps:
s1, acquiring an interface document of each APP, and converting the interface document into a standard document through a data standardization module, wherein each interface in the standard document corresponds to a plurality of sub-items, and when data corresponding to the sub-items are not found in the interface document, marking the value of the sub-item as null;
s2, counting the number N of subitems with the median null in all the interfaces corresponding to all the subitems by a priority ordering module, and ordering the priorities according to the size of N, wherein the smaller the value of N is, the higher the priority is, wherein the interfaces with the n=0 are marked as a first priority, and the interfaces with the number 0< N are marked as a second priority;
s3, screening out standard documents corresponding to all interfaces with the second priority by the priority ordering module, taking the standard documents as documents to be supplemented, sending the documents to be supplemented to a developer through the network module, reminding the developer to fill in data in the standard documents, and sending the data back to the priority ordering module after the completion of filling in;
s4, after determining the interfaces of the first priority, the test case distribution module associates at least one corresponding test case with each interface of the first priority according to a standard document, counts the number m of all the test cases and the number n of machines used for testing, numbers the machines, distributes m/n test cases to each machine, wherein if m/n is a non-integer, the integer part is taken, and distributes redundant test cases to the machines with the number 1;
s5, after receiving the test cases, an interface test module in the machine changes the running state of the machine into a test, marks all the test cases as incomplete and packages the test cases into a file to be tested, reads the test cases in the file to be tested one by one through an automatic script, marks the test cases as completed when finishing one test case, sends a test report containing the number of the tested machine and the test result to a test statistics module after finishing the interface test, and changes the running state of the machine into idle;
s6, after testing is completed on all interfaces with the first priority, screening out interfaces with the number of subitems of 0 in the subitems of null corresponding to the interfaces with the second priority by the priority sorting module, and re-marking the interfaces with the first priority, and executing the steps S3-S5 again until testing of all the interfaces is completed;
s7, screening out test cases which do not reach expectations according to the test report by the test statistics module, obtaining a machine number i of the test cases for testing, wherein i is less than or equal to n, distributing the test cases to a machine with the division number i through the test case distribution module, carrying out verification test through the interface test module, and making a verification test report, if the verification test report does not reach expectations, marking the test cases and the corresponding interfaces as abnormal by the test statistics module, obtaining all the test cases marked as abnormal and the corresponding interfaces, and generating an abnormal form.
2. The method according to claim 1, wherein in S1, the sub-items of the standard document include interface description, url called, request method, request parameter, parameter type, request parameter description.
3. The method for testing the mobile phone APP port according to claim 1, wherein in S5, after the running state of the machine is changed to be idle, the remaining running states are that the machine under test sends the number q of incomplete test cases to the test case allocation module, the machine with the largest number q of incomplete test cases is screened out, the number q/2 of incomplete test cases are allocated to the machine with the idle running state, and the test is continued until all the test cases corresponding to the interfaces with the first priority are completely tested.
4. The method of claim 1, wherein in S4, the method of numbering the machine is:
SS1, performing running division on the performances of all machines through the same software;
SS2, numbering according to the score of the running score, wherein the higher the score is, the lower the numbering is.
5. The mobile phone APP port test system comprises a plurality of machines for testing and is characterized by further comprising a master control subsystem for control, wherein the master control subsystem comprises a man-machine interaction module, a data standardization module, a priority ordering module, a test case distribution module, a test statistics module and a network module for transmitting data, and the machine comprises an interface test module and a network module for transmitting data;
the man-machine interaction module is used for importing an interface document of the APP and displaying an abnormal form;
the data standardization module is used for converting all the APP interface documents into a plurality of sub-item standard documents;
the priority ordering module divides the interface into a first priority and a second priority according to the data in the standard document, the first priority is tested in priority, and the second priority is tested after the data are supplemented; the sub-items of the standard document comprise interface description, called url, request method, request parameters, parameter types and request parameter description, when the data of the corresponding sub-item is not found in the interface document, the value of the sub-item is recorded as nul, the priority ordering module performs priority ordering according to the number N of the sub-items with the value null in the sub-item, the interface with N=0 is marked as a first priority, and the interface with the value 0< N is marked as a second priority;
the test case distribution module distributes the test cases to all machines according to the number m of the test cases corresponding to all the interfaces of the first priority and the number n of the machines used for testing; the test statistics module screens out test cases which do not reach expectations according to the test report, obtains the machine number i of the test cases for testing, wherein i is less than or equal to n, and distributes the test cases to the machine with the division number i through the test case distribution module;
the interface test module is used for marking all the test cases as incomplete and packaging the test cases into a file to be tested after receiving the test cases, reading the test cases in the file to be tested one by one through an automatic script, and sending a test report containing the machine number and the test result of the test to the test statistics module after completing the interface test;
the test statistics module is used for counting the test cases which do not reach the expectations and generating an abnormal form.
6. The system of claim 5, wherein the sub-items of the standard document include interface description, call url, request method, request parameter, parameter type, request parameter description, and when no data corresponding to the sub-item is found in the interface document, the value of the sub-item is marked as null, and the priority ranking module ranks the priorities according to the number N of sub-items with null in the sub-item, the interface with n=0 is marked as a first priority, and the interface with 0< N is marked as a second priority.
7. The system according to claim 5, wherein the test case allocation module associates at least one corresponding test case with each interface of the first priority according to a standard document, counts the number m of all test cases and the number n of machines used for testing, runs the performance of all machines through the same software, numbers the machines according to the score of the run, numbers the higher the score, numbers the lower the score, allocates m/n test cases to each machine after numbering the machines, wherein if m/n is a non-integer, the integer part is taken, and allocates redundant test cases to the machine with the number 1.
8. The system of claim 5, wherein the interface test module changes the running state of the machine into test after receiving test cases, marks as completed when one test case is completed, and after the running state of the machine becomes idle, the remaining running state of the machine in test sends the number q of incomplete test cases to the test case allocation module, screens out the machine with the largest number q of incomplete test cases, allocates the number q/2 of incomplete test cases to the machine with the idle running state, and continues to test until all test cases corresponding to the interfaces of the first priority are completely tested, and the priority ordering module screens out the interfaces with the number 0 corresponding to the sub items null when the interfaces of the second priority are completely tested, and re-marks as the first priority, and executes the step of testing the interfaces of the first priority again until the test of all interfaces is completed.
9. The system of claim 5, wherein the test statistics module screens out test cases which do not reach expectations according to the test report, obtains a machine number i of the test cases for testing, wherein i is less than or equal to n, distributes the test cases to machines with the division number i through the test case distribution module, performs verification test through the interface test module, and makes a verification test report, if the verification test report does not reach expectations, the test statistics module marks the test cases and the corresponding interfaces as abnormal, obtains all the test cases marked as abnormal and the corresponding interfaces, and generates an abnormal form.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910344706.2A CN110083537B (en) | 2019-04-26 | 2019-04-26 | Method and system for testing APP port of mobile phone |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910344706.2A CN110083537B (en) | 2019-04-26 | 2019-04-26 | Method and system for testing APP port of mobile phone |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110083537A CN110083537A (en) | 2019-08-02 |
| CN110083537B true CN110083537B (en) | 2023-08-18 |
Family
ID=67416993
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910344706.2A Active CN110083537B (en) | 2019-04-26 | 2019-04-26 | Method and system for testing APP port of mobile phone |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110083537B (en) |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105893235B (en) * | 2015-01-26 | 2019-03-01 | 中国移动通信集团浙江有限公司 | A kind of emulation test method, device and server |
| CN105528294B (en) * | 2015-12-29 | 2018-05-25 | 广东金赋科技股份有限公司 | The method and system that a kind of interface testing use-case automatically generates |
| JP6568017B2 (en) * | 2016-06-07 | 2019-08-28 | 株式会社日立製作所 | Test support apparatus and test support method |
| CN107577602A (en) * | 2017-08-25 | 2018-01-12 | 上海斐讯数据通信技术有限公司 | A kind of method of testing of APP interfaces, apparatus and system |
| CN107729243B (en) * | 2017-10-12 | 2020-06-16 | 上海携程金融信息服务有限公司 | Application programming interface automatic test method, system, equipment and storage medium |
| CN109446072A (en) * | 2018-09-27 | 2019-03-08 | 深圳壹账通智能科技有限公司 | The generation method and device of test script |
-
2019
- 2019-04-26 CN CN201910344706.2A patent/CN110083537B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN110083537A (en) | 2019-08-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11847103B2 (en) | Data migration using customizable database consolidation rules | |
| US20200104375A1 (en) | Data Migration Using Source Classification and Mapping | |
| CN106254144B (en) | Fault positioning platform, fault positioning method and device | |
| CN106933709B (en) | Test method and device | |
| CN108255707B (en) | Development role creating method, device, equipment and storage medium of test case | |
| CN110362473B (en) | Test environment optimization method and device, storage medium and terminal | |
| CN110308980A (en) | Batch processing method, device, equipment and the storage medium of data | |
| CN109871328B (en) | Software testing method and device | |
| CN110096353A (en) | Method for scheduling task and device | |
| CN102981951A (en) | Platform and method of cloud test development | |
| CN108509344B (en) | Daily cutting batch test method, equipment and readable storage medium | |
| CN110347602B (en) | Method and device for executing multitasking script, electronic equipment and readable storage medium | |
| CN110928655A (en) | Task processing method and device | |
| CN105446871B (en) | A kind of resource leakage detection method, apparatus and system | |
| CN107992362A (en) | The method, apparatus and system of automated performance testing | |
| CN106383764A (en) | Data acquisition method and device | |
| CN106980571A (en) | The construction method and equipment of a kind of test use cases | |
| CN112862098A (en) | Method and system for processing cluster training task | |
| CN113656174A (en) | Resource allocation method, system, computer device and storage medium | |
| CN110083537B (en) | Method and system for testing APP port of mobile phone | |
| CN110231981B (en) | Service calling method and device | |
| CN109992408B (en) | Resource allocation method, device, electronic equipment and storage medium | |
| CN113722107B (en) | Cloud product management and control service deployment method, device, equipment and storage medium | |
| CN107885593B (en) | User authentication method and device | |
| CN114942833A (en) | Method and related device for dynamically scheduling timing task resources |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20230721 Address after: Room 312 and 313, 3rd Floor, Phase 1, Ruibo Ao Building, No. 79 Ruihe Road, Science City, Huangpu District, Guangzhou City, Guangdong Province, 510700 (self declared) Applicant after: Guangdong Tianshun Information Technology Co.,Ltd. Address before: 317605 Software Building, Zhongshan Village, Chumen Town, Yuhuan City, Taizhou City, Zhejiang Province Applicant before: Tian Jinyue |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |