CN112306855B - Interface automation test method, device, terminal and storage medium - Google Patents
Interface automation test method, device, terminal and storage medium Download PDFInfo
- Publication number
- CN112306855B CN112306855B CN201910710107.8A CN201910710107A CN112306855B CN 112306855 B CN112306855 B CN 112306855B CN 201910710107 A CN201910710107 A CN 201910710107A CN 112306855 B CN112306855 B CN 112306855B
- Authority
- CN
- China
- Prior art keywords
- interface
- test
- data source
- data
- parameters
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3676—Test management for coverage analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Abstract
The invention provides an interface automatic test method, an interface automatic test device, a terminal and a storage medium, wherein the interface automatic test method comprises the following steps: automatically acquiring configuration parameters; connecting a data source according to the configuration parameters; determining a parameter generation rule according to a definition document, a service requirement document and a test case of an interface to be tested; generating interface parameters according to the parameter generation rule; calling an interface according to the interface parameters, and recording a return value of the interface; and determining whether the interface passes the test according to the return value. By the technical scheme of the invention, the accuracy of the interface parameters can be improved, the time for preparing the interface test parameters is reduced, and the accuracy and the efficiency of the interface test are improved.
Description
Technical Field
The invention relates to the technical field of interface testing, in particular to an interface automatic testing method, an interface automatic testing device, a terminal and a computer readable storage medium.
Background
The automatic interface test is one automatic test method, and aims at reducing manual work and raising test efficiency. The testing process mainly comprises the steps of sending parameters to the tested interface, receiving a returned result and comparing the result with an expected result, so as to judge whether the interface can pass the test.
In the related technology, the input parameters of the interface are prepared in advance according to the data of the service flow and the test environment before being tested, the workload of testers is large, the operation steps are multiple, the automation degree of the interface test is low, and the accuracy of the input of the interface parameters and the test efficiency are low.
Disclosure of Invention
The present invention is directed to solving at least one of the problems of the prior art or the related art.
Therefore, the invention aims to provide an interface automatic testing method.
Another object of the present invention is to provide an interface automatic testing device.
Another object of the present invention is to provide a terminal.
It is another object of the present invention to provide a computer-readable storage medium.
In order to achieve the above object, according to a technical solution of a first aspect of the present invention, there is provided an interface automation test method, including: automatically acquiring configuration parameters; connecting a data source according to the configuration parameters; determining a parameter generation rule according to a definition document, a service requirement document and a test case of an interface to be tested; generating interface parameters according to the parameter generation rule; calling an interface according to the interface parameters, and recording a return value of the interface; and determining whether the interface passes the test according to the return value.
In the technical scheme, the interface automatic test method provided by the invention can be applied to the test of a single interface and the test of a business process, the automatic test of the single interface tends to test the parameters of the interface and the business of the interface, and the test of the business process tends to determine whether the interface data flow among the same test project and different test projects is correct. By automatically acquiring the configuration parameters, automatically connecting the data source, automatically generating the input parameters (interface parameters) corresponding to the interface to be tested and determining whether the test passes according to the return value of the interface, the time for modifying the configuration and splicing the parameters is reduced, and the accuracy of the input of the interface parameters and the test efficiency can be improved. For the same interface, more than one group of automatically generated interface parameters are generated, and the generated interface parameters can be the combination of multiple groups of parameters according to different service requirements and different interface specifications and according to the requirements of test cases, so that the method aims to cover service logic, interface normal cases and abnormal cases and achieve code coverage rate of interface test.
In addition, the test case of the interface automation test method provided by the invention can be embedded into the test system according to the service requirement, and during test execution, the test case to be executed can be specified by adding the specified test case through the configuration interface, so that the test case does not need to be rewritten repeatedly before test, the work of writing the test case or importing the test case into the system is reduced, and the test efficiency is improved.
According to the interface automated testing method of the above technical solution, optionally, the method further includes: automatically generating an output expected value of the interface according to the service logic and the test case, wherein for the interface with the non-query function, the output expected value comprises the following steps: carrying out operation according with business logic on the data source by the keyword with the success mark or the keyword with the failure mark; for interfaces of the query class, outputting the expected value includes: keywords with success flags or keywords with failure flags and returning data results that meet business logic.
In the technical scheme, an expected result (output expected value) corresponding to a return value of an interface can be automatically generated according to a service, the output expected value comprises an expected operation which accords with service logic to a data source or an expected data result which is determined according to the service logic, and on the basis of the output expected value, the basis of passing the test is judged not only according to a state code and return information content, but also according to methods of automatically checking whether the operation of the data source is correct (such as addition, deletion, modification and the like) after the interface is called, or according to a tested interface and the service logic, directly inquiring data which accords with conditions from the data source and automatically comparing the data with the return value and the like, the interface test result (the return value) is judged in a deeper level, and the accuracy of the interface test is improved.
According to the interface automation test method of any one of the above technical solutions, optionally, the step of determining whether the interface passes the test according to the return value specifically includes: determining whether the interface passes the test according to the correctness of the operation on the data source after the interface carries out the calling operation; or determining whether the interface passes the test according to whether the return value accords with the service logic after the interface performs the calling operation.
In the technical scheme, based on the operation which is contained in the output expected value and accords with the service logic to the data source, the return value obtained after the interface parameter is input into the interface is judged, and if the operation which is reflected by the return value and accords with the service logic to the data source and is recorded in the output expected value is consistent, the interface is normal in function (passes the test). And judging a return value obtained after the interface parameter is input into the interface based on a data result which is contained in the output expected value and accords with the service logic, and if the data reflected by the return value accords with the service logic, indicating that the interface is normal in function (passes the test). The basis for judging that the test passes is not simple state codes and returned information contents, but deeper judgment is performed on the returned values on the basis, and the test accuracy is improved.
The interface automated testing method according to any one of the above technical solutions, optionally, further includes: recording case information, interface parameter information and return value information of the interface, counting the number of cases passing the test and the number of cases failing the test, and generating a test report.
According to the technical scheme, the test report is automatically generated according to the test result, the content of the test report needs to comprise the number of passed cases and the number of failed cases, the detailed test result can be checked, the detailed test result comprises case information, interface parameter information, interface return result information and the like, and the generated test report can be checked conveniently after the execution is finished, and the test result can be analyzed according to the report.
The interface automated testing method according to any one of the above technical solutions, optionally, further includes: compiling a test case according to the service requirement document and the definition document of the interface; determining the address of an interface server and a test case appointed to be executed; and compiling the definition of the interface into a script with input parameters according to the definition document of the interface so as to be called by the test case.
In the technical scheme, before configuration parameters are automatically acquired, a configuration editing interface is established, test cases are compiled according to a service requirement document and a definition document of the interface, and during execution, selection is performed through the configuration editing interface, and related test cases to be executed are selected for testing. The configuration editing interface is also used for determining the address of the interface server and specifying the test case to be executed. And packaging the definition of the interface according to the definition document of the interface, and reducing repeated definition of the interface, wherein the definition of the interface comprises the name of the interface, the input of the interface, the path and process for calling the interface, the output of the interface and the like, and provides good support for a method for calling the interface in a subsequent use case.
In addition, when the test environment changes, the address of the interface changes, the changed content is extracted into the configuration editing interface, corresponding configuration is carried out before the test is executed, different test requirements can be met, different test environments can be adapted through simple configuration, the operation is simple, and the efficiency is high. According to the test requirements, if all test cases do not need to be executed each time, the test cases can be configured in a configuration editing interface, the test cases to be executed are added, and all added cases or case sets can be executed when the test is executed after the test cases are added, so that the function of customizing the test range is achieved. The test cases can be divided into test cases with a single interface and test cases with a business process. The test case test object of the single interface is an interface and needs to include the test of the service logic and parameter specification of the interface; the testing of the business process needs to involve the mutual calling among all interfaces, and is prone to testing various normal and abnormal conditions of the business process. According to the definition of the requirements and the interfaces, when the test cases are written, each test case is required to be relatively independent from other test cases, the mutual calling and mutual dependency relationship does not exist, the requirement cases must contain normal conditions and abnormal conditions so as to improve the coverage rate of the cases to the requirements, and the purpose of comprehensively verifying the logic, input rules, abnormal operations and the like of the interfaces is achieved.
According to the interface automatic testing method of any one of the above technical solutions, optionally, the step of automatically obtaining the configuration parameters specifically includes: and acquiring the configuration parameters in the configuration file in the server through the server address, and acquiring the parameter values from the configuration parameters according to the parameter names.
In the technical scheme, the configuration parameters do not need to be manually configured, but the configuration parameters in the configuration file in the server are obtained through the server address, and the parameter values are obtained from the configuration parameters according to the parameter names. The automatic generation of the interface parameter values is realized, and the testing efficiency is improved. For example: establishing an object of a client through SSH (Secure Shell); establishing SSH connection according to the server address, the port number, the user name and the password; finding the position of a configuration file for project deployment on a server according to the project name, reading the configuration file and returning the content of the configuration file; and acquiring and storing parameter values in the returned content according to the parameter names.
According to the interface automated testing method of any one of the above technical solutions, optionally, the step of connecting the data source according to the configuration parameter specifically includes: connecting the data source server according to the data source server related information read from the configuration parameters; and executing a detection command on the data source server, detecting whether the data source is started or not, if the data source server is started, connecting the data source, and if the data source server is not started, starting the data source server and connecting the data source.
In the technical scheme, the configuration parameters comprise a server address, a data source name, a user name and a password of a data source, the data source server is automatically connected according to the information, a detection command is executed on the data source server, whether the data source is started or not is detected, if the data source is started, the data source connection is carried out, and if the data source is not started, the data source is started and the data source connection is carried out. And the data source connection is automatically carried out, so that the manual operation steps are reduced, and the test efficiency is improved.
According to the interface automated testing method of any one of the above technical solutions, optionally, the step of generating the interface parameters according to the parameter generation rule specifically includes: compiling a data source operation statement according to the parameter generation rule, and returning a data result; if the returned data result is empty, regenerating the data according to the parameter generation rule and the structural relationship between the data in the data source and inserting the data into the data source; if the returned data result is not null, the data result is formatted according to the input requirement of the interface and is recorded as the interface parameter.
In the technical scheme, the generation rule of the parameters is derived from the definition document, the service requirement document and the case design (the case compiling process) of the interface, the generation parameters can be ensured to accord with the service logic, the parameters which accord with the service logic are generated according to different service requirements and serve as the input of the interface, and the accuracy of the interface is judged according to the output of the interface. When the data source does not have data meeting the conditions (the returned data result is empty), the statement meeting the syntax of the data source is used for adding the business data meeting the logic according to the incidence relation and the specific business logic among the data in the database, then the data is extracted, the data is extracted and formatted, and then the data is input to the interface to be used as the interface parameter.
According to the interface automation test method of any one of the above technical solutions, optionally, the step of determining whether the interface passes the test according to the correctness of the operation on the data source after the interface performs the call operation specifically includes: inquiring a corresponding data table in a data source before the interface carries out calling operation, inquiring the data table after the interface carries out calling operation, judging whether the adding, deleting and modifying operation of the interface to the data table before and after calling accords with a service requirement document, and if so, determining that the interface test is passed.
In the technical scheme, the corresponding data table in the data source is inquired before the interface is called, the data table is inquired after the interface is called, whether the adding, deleting and modifying operations of the data table before and after the interface is called accord with the business requirement document or not is judged, the return value of the interface is further verified, and the testing accuracy is improved.
According to the interface automation test method of any one of the above technical solutions, optionally, the step of determining whether the interface passes the test according to whether the returned value after the interface performs the call operation conforms to the service logic includes: and querying data in the data source according to the service logic, comparing the queried data with corresponding data in the return value, and determining that the interface test is passed if the comparison result is consistent.
In the technical scheme, data are directly inquired in the data source according to the service logic, the inquired data are compared with corresponding data in the return value of the interface, whether the data in the return value accord with the service logic or not is further checked, and the testing accuracy is improved.
According to a second aspect of the present invention, there is provided an interface automation test apparatus, including: the interface automatic testing method comprises a memory, a processor and a program stored on the memory and capable of running on the processor, wherein the program realizes the steps of the interface automatic testing method according to any one of the technical schemes when being executed by the processor. The interface automatic testing device comprises all the beneficial effects of the interface automatic testing method according to any one of the above technical solutions, which are not described herein again.
According to a technical solution of the third aspect of the present invention, there is also provided a terminal, including: the interface automatic testing device according to the second aspect of the present disclosure. The terminal includes all the benefits of the interface automation test method according to any one of the above technical solutions, which are not described herein again.
According to an aspect of the fourth aspect of the present invention, there is further provided a computer-readable storage medium, on which a computer program is stored, wherein the computer program, when executed, implements the interface automation testing method defined in any one of the aspects of the first aspect.
Additional aspects and advantages of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.
Drawings
The above and/or additional aspects and advantages of the present invention will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
FIG. 1 shows a schematic flow diagram of a method for automated testing of an interface according to one embodiment of the invention;
FIG. 2 shows a schematic block diagram of a method for automated testing of an interface according to another embodiment of the invention;
FIG. 3 shows a schematic block diagram of an interface automation test arrangement according to an embodiment of the invention;
fig. 4 shows a schematic block diagram of a terminal according to an embodiment of the invention.
Detailed Description
In order that the above objects, features and advantages of the present invention can be more clearly understood, a more particular description of the invention will be rendered by reference to the appended drawings. It should be noted that the embodiments and features of the embodiments of the present application may be combined with each other without conflict.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention, however, the present invention may be practiced in other ways than those specifically described herein, and therefore the scope of the present invention is not limited by the specific embodiments disclosed below.
Example one
As shown in fig. 1, an interface automation test method according to an embodiment of the present invention includes:
step 102, automatically acquiring configuration parameters;
step 104, connecting a data source according to the configuration parameters;
step 106, determining a parameter generation rule according to a definition document, a service requirement document and a test case of an interface to be tested;
step 108, generating interface parameters according to the parameter generation rules;
step 110, calling an interface according to the interface parameters, and recording a return value of the interface;
based on the returned value, it is determined whether the interface passes the test, step 112.
In this embodiment, the interface automation test method may be applied to a test of a single interface and a test of a business process, where the automation test of the single interface tends to test parameters of the interface and a business of the interface, and the business process test tends to determine whether interface data flow between the same test item and different test items is correct. By automatically acquiring the configuration parameters, automatically connecting the data source, automatically generating the input parameters (interface parameters) corresponding to the interface to be tested and determining whether the test passes according to the return value of the interface, the time for modifying the configuration and splicing the parameters is reduced, and the accuracy of the input of the interface parameters and the test efficiency can be improved. For the same interface, more than one group of automatically generated interface parameters are generated, and the generated interface parameters can be the combination of multiple groups of parameters according to different service requirements and different interface specifications and according to the requirements of test cases, so that the method aims to cover service logic, interface normal cases and abnormal cases and achieve code coverage rate of interface test.
In addition, the test case of the interface automation test method provided by the invention can be embedded into a test system according to the service requirement, and the test case to be executed can be specified by adding the specified test case through the configuration interface during test execution, so that the test case does not need to be rewritten before the test, the work of compiling the test case or importing the test case into the system is reduced, and the test efficiency is improved.
In the above embodiment, optionally, the method further includes: automatically generating an output expected value of the interface according to the service logic and the test case, wherein for the interface with the non-query function, the output expected value comprises the following steps: carrying out operation according with business logic on the data source by the keyword with the success mark or the keyword with the failure mark; for interfaces of the query class, outputting the expected value includes: the keyword with success mark or the keyword with failure mark and the data result conforming to the business logic.
In this embodiment, an expected result (output expected value) corresponding to the return value of the interface can be automatically generated according to the service, where the output expected value includes an expected operation that is performed on the data source according to the service logic or an expected data result determined according to the service logic, and on the basis of the output expected value, the basis for passing the test is judged not only by the status code and the content of the return information, but also by automatically checking whether the operation of the data source is correct (such as addition, deletion, modification, and the like) after the interface is called, or by directly querying the data that is in accordance with the condition from the data source according to the interface to be tested and the service logic and automatically comparing the data with the return value, and the like, so as to perform a deeper judgment on the interface test result (return value), thereby improving the accuracy of the interface test.
In any of the above embodiments, optionally, the step of determining whether the interface passes the test according to the return value specifically includes: determining whether the interface passes the test according to the correctness of the operation on the data source after the interface carries out the calling operation; or determining whether the interface passes the test according to whether the return value accords with the service logic after the interface carries out calling operation.
In this embodiment, based on the operation that conforms to the service logic on the data source included in the output expected value, the return value obtained after the interface parameter is input to the interface is determined, and if the operation that is reflected by the return value and that conforms to the service logic on the data source recorded in the output expected value is the same, it is indicated that the interface functions normally (through the test). And judging a return value obtained after the interface parameter is input into the interface based on a data result which is contained in the output expected value and accords with the service logic, and if the data reflected by the return value accords with the service logic, indicating that the interface is normal in function (passes the test). The basis of passing the judgment test is not simple state codes and returned information contents, but deeper judgment is carried out on the returned values on the basis, and the test accuracy is improved.
In any one of the above embodiments, optionally, the method further includes: recording case information, interface parameter information and return value information of the interface, counting the number of cases passing the test and the number of cases failing the test, and generating a test report.
In this embodiment, the test report is automatically generated according to the test result, the content of the test report needs to include the number of passed cases and the number of failed cases, and the detailed test result can be checked, and the detailed test result includes case information, interface parameter information, interface return result information, and the like, so that the generated test report can be checked after the execution is finished, and the test result can be analyzed according to the report.
In any one of the above embodiments, optionally, the method further includes: compiling a test case according to the service requirement document and the definition document of the interface; determining the address of an interface server and a test case appointed to be executed; and compiling the definition of the interface into a script with input parameters according to the definition document of the interface so as to be called by the test case.
In the embodiment, before the configuration parameters are automatically acquired, a configuration editing interface is set, test cases are compiled according to the service requirement document and the definition document of the interface, and the configuration editing interface is used for selecting during execution and selecting the related test cases to be executed for testing. The configuration editing interface is also used for determining the address of the interface server and specifying the test case to be executed. And packaging the definition of the interface according to the definition document of the interface, and reducing repeated definition of the interface, wherein the definition of the interface comprises the name of the interface, the input of the interface, the path and process for calling the interface, the output of the interface and the like, and provides good support for a method for calling the interface in a subsequent use case.
In addition, when the test environment changes, the address of the interface changes, the changed content is extracted into the configuration editing interface, corresponding configuration is carried out before the test is executed, different test requirements can be met, different test environments can be adapted through simple configuration, and the method is simple to operate and high in efficiency. According to the test requirements, if all test cases do not need to be executed each time, the test cases can be configured in a configuration editing interface, the test cases to be executed are added, and all added cases or case sets can be executed when the test is executed after the test cases are added, so that the function of customizing the test range is achieved. The test cases can be divided into test cases with a single interface and test cases with a business process. The test case test object of the single interface is an interface and needs to include the test of the service logic and parameter specification of the interface; the testing of the business process needs to involve the mutual calling among all interfaces, and is prone to testing various normal and abnormal conditions of the business process. According to the definition of the requirements and the interfaces, when the test cases are written, each test case is required to be relatively independent from other test cases, the mutual calling and mutual dependency relationship does not exist, the requirement cases must contain normal conditions and abnormal conditions so as to improve the coverage rate of the cases to the requirements, and the purpose of comprehensively verifying the logic, input rules, abnormal operations and the like of the interfaces is achieved.
In any of the above embodiments, optionally, the step of automatically acquiring the configuration parameters specifically includes: and acquiring the configuration parameters in the configuration file in the server through the server address, and acquiring the parameter values from the configuration parameters according to the parameter names.
In this embodiment, the configuration parameters do not need to be configured manually, but the configuration parameters in the configuration file in the server are obtained through the server address, and the parameter values are obtained from the configuration parameters according to the parameter names. The automatic generation of the interface parameter values is realized, and the testing efficiency is improved. For example: establishing an object of a client through SSH (Secure Shell); establishing SSH connection according to the server address, the port number, the user name and the password; finding the position of a configuration file for project deployment on a server according to the project name, reading the configuration file and returning the content of the configuration file; and acquiring and storing parameter values in the returned content according to the parameter names.
In any of the above embodiments, optionally, the step of connecting the data source according to the configuration parameter specifically includes: connecting the data source server according to the data source server related information read from the configuration parameters; and executing a detection command on the data source server, detecting whether the data source is started or not, if the data source server is started, connecting the data source, and if the data source server is not started, starting the data source server and connecting the data source.
In the embodiment, the configuration parameters include a server address, a data source name, a user name and a password of the data source, the data source server is automatically connected according to the information, a detection command is executed on the data source server to detect whether the data source is started, if the data source is started, the data source connection is performed, and if the data source is not started, the data source is started and the data source connection is performed. And the data source connection is automatically carried out, so that the manual operation steps are reduced, and the test efficiency is improved.
In any of the above embodiments, optionally, the step of generating the interface parameter according to the parameter generation rule specifically includes: compiling a data source operation statement according to the parameter generation rule, and returning a data result; if the returned data result is empty, regenerating the data according to the parameter generation rule and the structural relationship between the data in the data source and inserting the data into the data source; if the returned data result is not null, the data result is formatted according to the input requirement of the interface and is recorded as the interface parameter.
In the embodiment, the generation rule of the parameter is derived from the definition document, the service requirement document and the case design (the case writing process) of the interface, the generated parameter can be ensured to accord with the service logic, the parameter which accords with the service logic is generated according to different service requirements and is used as the input of the interface, and the accuracy of the interface is judged according to the output of the interface. When the data source does not have data meeting the conditions (the returned data result is empty), the statement meeting the syntax of the data source is used for adding the business data meeting the logic according to the incidence relation and the specific business logic among the data in the database, then the data is extracted, the data is extracted and formatted, and then the data is input to the interface to be used as the interface parameter.
In any of the above embodiments, optionally, the step of determining whether the interface passes the test according to the correctness of the operation on the data source after the interface performs the call operation specifically includes: inquiring a corresponding data table in a data source before the interface carries out calling operation, inquiring the data table after the interface carries out calling operation, judging whether the adding, deleting and modifying operation of the interface to the data table before and after calling accords with a service requirement document, and if so, determining that the interface test is passed.
In the embodiment, the corresponding data table in the data source is inquired before the interface carries out calling operation, the data table is inquired after the interface carries out calling operation, whether the adding, deleting and modifying operation of the data table by the interface before and after calling meets the service requirement document is judged, the return value of the interface is further verified, and the testing accuracy is improved.
In any of the above embodiments, optionally, the step of determining whether the interface passes the test according to whether a return value after the interface performs the call operation conforms to the service logic includes: and inquiring data in the data source according to the service logic, comparing the inquired data with corresponding data in the return value, and determining that the interface test is passed if the comparison result is consistent.
In the embodiment, data is directly inquired in the data source according to the service logic, the inquired data is compared with corresponding data in the return value of the interface, whether the data in the return value accords with the service logic is further checked, and the test accuracy is improved.
Example two
As shown in fig. 2, an interface automation test method according to another embodiment of the present invention includes: the method comprises the following steps: adding a configuration editing interface; step two: compiling an interface definition; step three: designing a test case; step four: automatically generating parameters; step five: and generating a test report. The specific operation steps are as follows:
the method comprises the following steps: add configuration edit interface
The configuration editing interface only needs to comprise the address of the interface server and the specified test case to be executed. When the test environment changes, the address of the interface changes, the changed content is extracted into the configuration interface, corresponding configuration is carried out before the test is executed, so that different test requirements are met, different test environments can be adapted through simple configuration, the operation is simple and convenient, and the efficiency is high. According to the test requirements, if all test cases do not need to be executed each time, the test cases can be configured on the editing interface, the test cases to be executed are added, and after the test cases are added, all the added use cases or use case sets can be executed during the test execution, so that the function of self-defining the test range is achieved.
Step two: writing interface definitions
The definition of the interface is packaged to reduce the repeated definition of the interface because the same interface needs to be called for many times in different test cases. The definition of the interface comprises the name of the interface, the input of the interface, the path and process of interface calling, the output of the interface and the like, and provides good support for the method for calling the interface in the subsequent use cases.
Step three: design test case
The test case is designed according to requirements, written into an achievable code and stored, and selected through a configuration interface during execution, and the related test case to be executed is selected for testing. The use cases can be divided into test cases with a single interface and test cases with a business process. The test case test object of the single interface is an interface, and needs to include the test of the service logic and parameter specification of the interface; the testing of the business process needs to involve the mutual calling among all interfaces, and is prone to testing various normal and abnormal conditions of the business process. According to the requirements and the definition of the interface, the test cases are designed, each test case is required to be relatively independent from other test cases, the mutual calling and mutual dependency relationship does not exist, the cases are required to contain normal conditions and abnormal conditions so as to improve the coverage rate of the cases to the requirements, and the purpose of comprehensively verifying the logic, the input rules, the abnormal operation and the like of the interface is achieved.
Step four: automatic generation of parameters
The interface is called in the use case, the definition of the interface in the step one is used, because the test key points and the business logics to be tested of different use cases are different, the input parameters in different use cases are different, the parameters are not required to be generated manually and are automatically generated according to the business requirements and the design of the use cases without excessive manual intervention, and the generation process is as follows:
1. configuration parameters are automatically obtained.
Unlike other testing methods, the configuration parameters can be automatically obtained, not manually configured, and the method is to obtain the relevant configuration in the configuration file in the server through the server address, including but not limited to the configuration of the data source, and the implementation steps are as follows:
(1) establishing an SSH Clinet object;
(2) establishing ssh connection according to the server address, the port number, the user name and the password;
(3) finding the position of a configuration file for project deployment on a server according to the project name, reading the configuration file and returning the content of the configuration file;
(4) and acquiring and storing parameter values in the returned content according to the parameter names, wherein the parameters comprise but are not limited to information of a data source (data _ source), a city (city), a related interface (relationship _ interface) and the like according to service requirements.
2. Automatic data source connection.
(1) Connecting a data source server according to the server address of the data source data _ source obtained in the step 1, the data source name, the user name and the password;
(2) executing a detection command on a data source server to detect whether a data source is started;
(3) if the data source is started, the data source connection is carried out;
(4) if not, starting the data source and connecting the data source.
3. And (4) automatic parameter generation.
(1) Generating a rule para _ rule according to business requirements and case design compiling parameters;
(2) compiling a data source operation statement according to the para _ rule, and returning a data result data _ result;
(3) if the returned data _ result is empty, proceed to step (4) in step 3
(4) Regenerating data according to the rule in the step (1) in the step 3 and the structural relationship between the data in the data source, inserting the data into the data source, and continuing the step (2) in the step 3;
(5) and if the returned data _ result is not empty, formatting the data result according to the input requirement of the interface, and storing.
4. The desired result is automatically generated.
And (3) using the input parameters of the interface automatically generated in the step (3), calling the interface needing to be called in the use case, and recording the return value of the interface. The method is characterized in that an expected value exists in the output of each interface, the expected value is obtained according to business logic and case design, when each interface returns, the expected value is compared with an actual result value, if the actual return value of the interface meets the expected value, the interface test passes, otherwise, the interface test does not pass, and different from other test methods, the expected operation and the expected return value in the method do not need to be manually input, but are automatically generated according to the business. For the interface with non-inquiry function, the expected value may be the result of the keyword with success or failure mark, and some operations conforming to the service flow and specification are carried out on the data source; for the query class interface, keywords with success or failure flags are returned, and data results that conform to the business logic are returned. For the interface with the non-query function, firstly, whether the interface passes the test can be preliminarily determined by judging whether the return result contains expected keywords and whether the returned state code is correct, and further, whether the operations of adding, modifying and deleting the data source are correct needs to be determined, so that corresponding data tables in the data source need to be queried before and after the interface is called, whether the operations of adding, deleting, modifying and the like of the data source before and after the interface is called meet the service requirements is judged, and if the operations meet the service requirements, the interface can be further determined to pass the test; for the interface of the query class, firstly, whether the interface test is passed or not is preliminarily judged by judging whether the return result contains the expected keyword and whether the returned status code is correct or not, and furthermore, whether the returned query data meets the service requirement or not is further determined, so that the data needs to be queried in a data source according to the queried service logic, the queried data is compared with the returned data of the interface, and if the queried data is consistent with the returned data of the interface, the interface test is further determined to be passed.
Step five: generating test reports
And automatically generating a test report according to the test result, wherein the content of the test report needs to comprise the number of passed cases and the number of failed cases, and the detailed test result can be checked and needs to comprise case information, interface parameter information, interface return result information and the like. In summary, the automated testing method and system based on automatic parameter generation are generated, before the method is executed, an address of a testing environment, an address of a data source, and a test case or a test case set which is designated to be executed need to be configured on a configuration interface, and after the configuration is completed, a test can be executed, and after the execution is completed, a generated test report can be checked, and a test result can be analyzed according to the report.
EXAMPLE III
According to the automatic interface testing method provided by the second embodiment of the invention, the method is used in the test of the BOMS interface project based on the technical scheme provided by the second embodiment.
Item background introduction: the BOMS interface provides interface service between the BOMS platform and the basic service platform. The BOMS platform is a service platform facing users, users can carry out self-service broadband services on the platform, operations such as service handling and the like carried out on the platform by users need to carry out addition, modification, updating and the like of user related data on a basic service platform, and the operations are realized through a BOMS interface.
The procedure of the test is as follows:
compiling a test case design according to the interface document and the requirement document, extracting the configuration of the specified test case and the test server address according to the actual requirement, and setting through a configuration interface.
According to the interface document of BOMS interface and the requirement document of service, the interface test is divided into 3 single interface tests and 3 service flow tests.
Only one of the interfaces getAccountTypeListForOldCustomer is described as a test case of a single interface, and the interfaces are described as follows:
interface name: getACCOUNTTypeListForOldCustomer
Interface function: old user inquires billable basic account type when charging
Interface path: (ii) a/getAccountTypeListForOldCustomer
Interface parameters: as shown in the following table
| Parameter name | Definition of | Type 15 |
| city | City code | String |
| accountId | User ID | Long |
| classification | Account type | String |
| applicationStatusLIst | Account type adaptation mode | Iist<Map<String>> |
(1) Extracting configurable data from interface documents
Extracting variable contents from an interface document, wherein firstly, an interface path is known, but a server address of an interface is variable and needs to be set in a configuration interface; secondly, the specification of the interface requirement and the interface parameter needs to compile a test case and write the test case into a test script, and the test case to be specified to be executed can be added in a configuration interface during execution.
(2) Writing a test case:
the test case needs to consider test parameters and test requirements, for example, the parameter classification is divided into "basic" and "package", the application status list is divided into "online", "platform" and "mobile phone" whether to be available, and the like, and the normal case needs to contain combinations of different values of the parameters and also needs to contain abnormal cases.
(3) Automatic generation of parameters
(3.1) automatically acquiring parameter configuration:
in order to achieve automatic operation of the interface and reduce the parameter configuration process, the configurable part of the interface parameters is acquired by adopting an automatic acquisition mode in a configuration file. For example, in the interface of getaccounttypelistforoldclient, the "city" parameter is changeable, the value of the specific parameter may be read in a configuration file, and the name and path of the configuration file are generally known, so that the value of the parameter is obtained by the method of "1" in "step four" of "implementation" in the description, for example, the server address is "x", and the port number is "y".
And establishing SSH connection according to the server address x and the port y, reading the configuration file under the path of the known configuration file, acquiring the value of the parameter (here, the value of the city parameter) according to the name of the parameter in the configuration file, and acquiring information such as the server address, the user name, the password, the database name and the like of the data source according to the name of the data source (such as data _ source).
(3.2) automatically connecting data sources
According to the method of ' 3 ' in the fourth step ', the data source server is connected according to the server address, after the connection is successful, whether the data source is started or not is detected, and if the data source is started, the data source is connected through information such as a user name, a password, a database name and the like of the data source; if the remote operation database is not started, the remote operation database is started by a command, and the data source connection is carried out by using the same method after the remote operation database is started.
(3.3) automatic parameter Generation
And entering a step of automatically generating parameters after the database is successfully connected, and performing rule specification according to use cases, interface documents and the like to generate the parameters. Taking this example as an example, some use cases are described as follows (the use cases are only illustrative, and not all use cases):
the first case is as follows: the inquiry status is the user paying for the disconnected network, and the selected account type can be applicable to the condition of the basic account type of the platform.
Case two: and inquiring the user with the opened state to pay, wherein the selected account type can be suitable for the conditions of the package account types of the network and the platform.
And compiling a parameter which is required by query statement query and meets the condition according to the data relation of the use case and the data source, and formatting the parameter to be used as a parameter calling interface of the interface.
Taking the 'use case one' as an example, the account of a user needing to inquire a disconnected user through a user table is taken as the 'basic' account type classification parameter, the application stateful list parameter is a list of user applicable modes (only applicable to a platform), the parameter is formatted and then used as an interface input calling interface, and the return value of the interface is received.
When the data source does not have data meeting the conditions, if a user with a disconnected network cannot be inquired, the data is extracted and formatted according to the method after the business data meeting the logic is added by the statement meeting the grammar of the data source according to the incidence relation and the specific business logic among the data in the database, and then the return value of the interface is received.
(3.4) automatically generating expected results and judging whether the interface returns correctly
Firstly, judging whether a status code returned by an interface meets expectations or not, wherein generally, when the interface is successfully called and correctly returned, the status code is 200; and judging whether the return content of the interface contains expected keywords which mark success.
Secondly, whether the data value inquired by the interface meets the service requirement is judged. According to specific services, the inquired account types which can be renewed by the user should meet the following conditions:
the method conforms to a 'user chargeable account rule', the rule is closely related to the service and is a rule which needs to be followed by the user to carry out the charging on each platform;
the account type must be basic rather than package;
the account type is only applicable to platform charges.
And inquiring the qualified account type data in the data source according to the service rules, comparing the data with the account type data returned by the interface, judging that the interface test is passed if the returned data are the same, and otherwise, judging that the interface test is failed.
The method can also be used for testing complex business processes, one business process usually calls several interfaces or interfaces of multiple projects, and multiple testing environments may be involved, for example: testing a user who opens an account in the 'employee version', opening the account in the 'boms' platform, and calling the account opening in the 'employee version' firstly: the interface of the user opening of the 'boss' is called again, and whether the service flow test passes or not is determined through the insertion of user data in the data source, the change of the user state and the like. The method for automatically acquiring parameters in the invention is also applicable to the test process of the business process, wherein the methods of automatically acquiring parameter configuration, automatically connecting data sources, automatically generating parameters, automatically generating expected results and the like can be realized by the step four (method for automatically generating parameters) in the embodiment two.
(4) And finally generating and recording a test report by taking the use case as a unit.
Example four
As shown in fig. 3, an interface automation test apparatus 300 according to an embodiment of the present invention includes: a memory 302, a processor 304 and a program stored on the memory 302 and executable on the processor 304, the program, when executed by the processor 304, implementing the steps of the interface automation test method according to any of the embodiments described above. The interface automatic testing apparatus 300 includes all the advantages of the interface automatic testing method according to any of the above embodiments, and will not be described herein again.
EXAMPLE five
As shown in fig. 4, a terminal 400 according to an embodiment of the present invention includes: the interface automatic test device 300 according to the fourth embodiment. The terminal 400 can implement: automatically acquiring configuration parameters; connecting a data source according to the configuration parameters; determining a parameter generation rule according to a definition document, a service requirement document and a test case of an interface to be tested; generating interface parameters according to the parameter generation rule; calling an interface according to the interface parameters, and recording a return value of the interface; and determining whether the interface passes the test according to the return value. The terminal 400 includes all the advantages of the interface automatic testing method according to any of the above embodiments, which are not described herein again.
EXAMPLE six
According to an embodiment of the present invention, there is also provided a computer-readable storage medium, on which a computer program is stored, which when executed implements the interface automation testing method defined in any of the above embodiments.
The technical solution of the above embodiment can be implemented on a computer with a system, the system of the computer includes but is not limited to windows, linux, ios, etc., an IDE with a programming function is required to be installed on such a computer for programming, and the programming language includes but is not limited to python, java, c + +, c.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It should be noted that in the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means can be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various changes and modifications may be made therein without departing from the scope of the invention as defined in the appended claims and their equivalents, and it is intended that the invention encompass such changes and modifications as well.
Claims (12)
1. An automated interface testing method, comprising:
automatically acquiring configuration parameters;
connecting a data source according to the configuration parameters;
determining a parameter generation rule according to a definition document, a service requirement document and a test case of an interface to be tested;
generating interface parameters according to the parameter generation rule;
calling the interface according to the interface parameters, and recording a return value of the interface;
determining whether the interface passes the test according to the return value;
compiling a test case according to the service requirement document and the definition document of the interface;
determining the address of an interface server and a test case appointed to be executed;
and compiling the definition of the interface into a script with input parameters according to the definition document of the interface so as to be called by the test case.
2. The automated interface testing method of claim 1, further comprising:
automatically generating the output expected value of the interface according to the business logic and the test case,
wherein, for the interface of the non-query function, the output expected value comprises: carrying out operation according with the business logic on the data source by the keyword with the success mark or the keyword with the failure mark; for an interface of a query class, the output expected value includes: keywords with success flags or keywords with failure flags and returning data results that conform to the business logic.
3. The method for automatically testing an interface according to claim 2, wherein the step of determining whether the interface passes the test according to the return value specifically includes:
determining whether the interface passes the test according to the correctness of the operation on the data source after the interface carries out the calling operation; or
And determining whether the interface passes the test according to whether the return value accords with the service logic after the interface performs the calling operation.
4. The automated interface testing method of claim 1, further comprising:
recording the case information, the interface parameter information and the return value information of the interface, counting the number of cases passing the test and the number of cases failing the test, and generating a test report.
5. The automated interface testing method according to any one of claims 1 to 4, wherein the step of automatically acquiring the configuration parameters specifically includes:
and acquiring configuration parameters in a configuration file in the server through the server address, and acquiring parameter values from the configuration parameters according to the parameter names.
6. The automated interface testing method according to any one of claims 1 to 4, wherein the step of connecting a data source according to the configuration parameters specifically includes:
connecting the data source server according to the data source server related information read from the configuration parameters;
executing a detect command on the data source server, detecting whether the data source has been started,
and if the data source server is started, the data source connection is carried out, and if the data source server is not started, the data source server is started and the data source connection is carried out.
7. The method for automatically testing an interface according to any one of claims 1 to 4, wherein the step of generating interface parameters according to the parameter generation rule specifically includes:
compiling a data source operation statement according to the parameter generation rule, and returning a data result;
if the returned data result is empty, regenerating data according to the parameter generation rule and the structural relationship between the data in the data source and inserting the data into the data source;
and if the returned data result is not empty, formatting the data result according to the input requirement of the interface, and recording the data result as the interface parameter.
8. The method according to claim 3, wherein the step of determining whether the interface passes the test according to the correctness of the operation on the data source after the call operation is performed on the interface specifically includes:
inquiring a corresponding data table in the data source before the interface carries out calling operation, inquiring the data table after the interface carries out calling operation, judging whether the adding, deleting and modifying operation of the interface to the data table before and after calling meets the business requirement document, and if so, determining that the interface test is passed.
9. The method according to claim 3, wherein the step of determining whether the interface passes the test according to whether the return value conforms to the service logic after the call operation is performed on the interface specifically includes:
and querying data in the data source according to the service logic, comparing the queried data with corresponding data in the return value, and determining that the interface test is passed if the comparison result is consistent.
10. An automated interface testing device, comprising:
memory, processor and program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the interface automation test method of any one of claims 1 to 9.
11. A terminal, comprising:
the interface automated test equipment of claim 10.
12. A computer-readable storage medium, on which a computer program is stored, which, when executed, carries out the steps of the interface automation test method according to any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910710107.8A CN112306855B (en) | 2019-08-02 | 2019-08-02 | Interface automation test method, device, terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910710107.8A CN112306855B (en) | 2019-08-02 | 2019-08-02 | Interface automation test method, device, terminal and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112306855A CN112306855A (en) | 2021-02-02 |
| CN112306855B true CN112306855B (en) | 2022-06-17 |
Family
ID=74485514
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910710107.8A Active CN112306855B (en) | 2019-08-02 | 2019-08-02 | Interface automation test method, device, terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112306855B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113010413B (en) * | 2021-02-20 | 2023-04-25 | 烽火通信科技股份有限公司 | Automatic interface testing method and device |
| CN112948195B (en) * | 2021-03-31 | 2023-04-25 | 建信金融科技有限责任公司 | Interface testing method, device, electronic equipment and storage medium |
| CN113407445B (en) * | 2021-06-03 | 2022-11-22 | 拉扎斯网络科技（上海）有限公司 | End-to-end automatic testing method and device and electronic equipment |
| CN113535565B (en) * | 2021-07-19 | 2022-10-04 | 工银科技有限公司 | Interface use case generation method, device, equipment and medium |
| CN113740781B (en) * | 2021-08-30 | 2022-05-24 | 广州文远知行科技有限公司 | Interface looseness detection method and device, vehicle and storage medium |
| CN116578497A (en) * | 2023-07-11 | 2023-08-11 | 苏州浪潮智能科技有限公司 | Automatic interface testing method, system, computer equipment and storage medium |
| CN117171056B (en) * | 2023-11-02 | 2024-01-09 | 绿城科技产业服务集团有限公司 | Test method and device based on automatic interface |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105681126A (en) * | 2015-12-30 | 2016-06-15 | 合一网络技术(北京)有限公司 | Automatic test method and system based on protocol interface |
| CN108415846A (en) * | 2018-04-19 | 2018-08-17 | 挖财网络技术有限公司 | A kind of method and apparatus generating minimal automation test use cases |
| CN108897687A (en) * | 2018-06-29 | 2018-11-27 | 泰华智慧产业集团股份有限公司 | A kind of API automated testing method and system based on data-driven |
| CN109101415A (en) * | 2018-06-25 | 2018-12-28 | 平安科技（深圳）有限公司 | Interface test method, system, equipment and the storage medium compared based on database |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9959200B2 (en) * | 2012-09-06 | 2018-05-01 | Red Hat Israel, Ltd. | User interface for composing test scenarios |
-
2019
- 2019-08-02 CN CN201910710107.8A patent/CN112306855B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105681126A (en) * | 2015-12-30 | 2016-06-15 | 合一网络技术(北京)有限公司 | Automatic test method and system based on protocol interface |
| CN108415846A (en) * | 2018-04-19 | 2018-08-17 | 挖财网络技术有限公司 | A kind of method and apparatus generating minimal automation test use cases |
| CN109101415A (en) * | 2018-06-25 | 2018-12-28 | 平安科技（深圳）有限公司 | Interface test method, system, equipment and the storage medium compared based on database |
| CN108897687A (en) * | 2018-06-29 | 2018-11-27 | 泰华智慧产业集团股份有限公司 | A kind of API automated testing method and system based on data-driven |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112306855A (en) | 2021-02-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112306855B (en) | Interface automation test method, device, terminal and storage medium | |
| CN102831052B (en) | Test exemple automation generating apparatus and method | |
| CN107665171B (en) | Automatic regression testing method and device | |
| US8347267B2 (en) | Automated software testing and validation system | |
| CN100468356C (en) | Test case inheritance controlled via attributes | |
| CN107273286A (en) | For the scene automatic test platform and method of task application | |
| CN109783346B (en) | Keyword-driven automatic testing method and device and terminal equipment | |
| CN108710571B (en) | Method and device for generating automatic test code | |
| CN109408366B (en) | Data source configuration test method, system, computer equipment and storage medium | |
| CN115080398A (en) | Automatic interface test system and method | |
| CN112506807A (en) | Automatic test system for interface serving multiple systems | |
| CN112181854A (en) | Method, device, equipment and storage medium for generating flow automation script | |
| CN110750434A (en) | Interface testing method and device, electronic equipment and computer readable storage medium | |
| CN113220597B (en) | Test method, test device, electronic equipment and storage medium | |
| CN112905441A (en) | Test case generation method, test method, device and equipment | |
| CN107450909A (en) | The treating method and apparatus of validity check is integrated for SDK | |
| CN111221721A (en) | Automatic recording and executing method and device for unit test cases | |
| CN110147313B (en) | Log output method and device | |
| CN113326046B (en) | Method and device for acquiring compiling time length | |
| CN115987821A (en) | Gateway routing test method and device | |
| CN113704123A (en) | Interface test method, device, equipment and storage medium | |
| CN105955879A (en) | Method and device for testing two-dimensional code generating algorithm | |
| CN111143229A (en) | Software testing method and device, computer equipment and computer readable storage medium | |
| CN108446120A (en) | A kind of detection method, device and the terminal device of SDK accesses installation kit | |
| CN112905459B (en) | Service interface testing method and device, electronic equipment and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |