Application test method, device, system, electronic device and storage medium

Abstract

The application provides an application test method, device, system, electronic equipment and computer readable storage medium, including: obtaining a to-be-collected interface identifier of a to-be-collected application, and determining a to-be-collected interface according to the to-be-collected interface identifier; collecting interface calling information of the to-be-collected interface, wherein the interface calling information includes external calling information and internal calling information; and sending the interface calling information to a test end, so that the test end tests a to-be-tested application according to the interface calling information. The application can collect interface calling information of a to-be-collected application during running of the to-be-collected application, and test a to-be-tested application according to the interface calling information of the to-be-collected application, without requiring a test personnel to manually prepare test data for the to-be-tested application, thereby improving the efficiency of application testing. The collected interface calling information includes interface external calling information and interface internal calling information, thereby improving the effect of application testing.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of software testing, and particularly relate to an application testing method, device, system, electronic device, and computer readable storage medium. BACKGROUND

[0002] At present, with the rapid development of the computer application industry, the requirement for application quality is continuously improved. Before an application is put online, the application needs to be tested, and errors of the application are repaired according to a test result, so that the application can normally provide services when the application is put online.

[0003] In the related art, before testing an application, a tester usually needs to design test data according to a service that can be provided by the application to be tested, the test data including input data and a correct result that should be output by the application to be tested for the input data.

[0004] However, in actual application, because the structure of the application is relatively complex, and the application covers a relatively large range of services and a relatively large number of service types, the amount of test data required for testing the application is relatively large, and the tester needs to consume a large amount of energy and time cost to prepare the test data for the application to be tested, which will result in a relatively low efficiency of application testing. SUMMARY

[0005] Embodiments of the present application provide an application testing method, device, system, electronic device, and computer readable storage medium to solve the problem of low efficiency of application testing in the related art.

[0006] In a first aspect, embodiments of the present application provide an application testing method applied to a collection end, the method comprising:

[0007] obtaining a to-be-collected interface identifier of a to-be-collected application, and determining a to-be-collected interface according to the to-be-collected interface identifier, wherein the to-be-collected interface identifier includes an external calling interface identifier and an internal calling interface identifier;

[0008] collecting interface calling information of the to-be-collected interface, wherein the interface calling information includes interface external calling information and interface internal calling information;

[0009] sending the interface calling information to a test end, so that the test end tests a to-be-tested application according to the interface calling information.

[0010] In a second aspect, embodiments of the present application provide an application testing method applied to a test end, the method comprising:

[0011] obtaining interface calling information collected from a to-be-collected application, wherein the interface calling information includes interface external calling information and interface internal calling information;

[0012] test the to-be-tested application according to the interface calling information, to obtain test output results of the to-be-tested application;

[0013] send the test output results to a server, so that the server generates an application test report according to the test output results and the interface calling information.

[0014] In a third aspect, an application test method is provided, and the method is applied to a server and includes the following steps.

[0015] obtaining interface calling information collected from a to-be-collected application, wherein the interface calling information includes interface external calling information and interface internal calling information;

[0016] obtaining test output results collected from a to-be-tested application, wherein the test output results are obtained by a test end by testing the to-be-tested application according to the interface calling information;

[0017] generating an application test report according to the interface calling information and the test output results.

[0018] In a fourth aspect, an application test device is provided, and the device includes the following steps.

[0019] an obtaining module, configured to obtain a to-be-collected interface identifier of a to-be-collected application, and determine a to-be-collected interface according to the to-be-collected interface identifier, wherein the to-be-collected interface identifier includes an external calling interface identifier and an internal calling interface identifier;

[0020] a collecting module, configured to collect interface calling information of the to-be-collected interface, wherein the interface calling information includes interface external calling information and interface internal calling information;

[0021] a sending module, configured to send the interface calling information to a test end, so that the test end tests a to-be-tested application according to the interface calling information.

[0022] In a fifth aspect, an application test device is provided, and the device includes the following steps.

[0023] an obtaining module, configured to obtain interface calling information collected from a to-be-collected application, wherein the interface calling information includes interface external calling information and interface internal calling information;

[0024] a testing module, configured to test a to-be-tested application according to the interface calling information, to obtain test output results of the to-be-tested application;

[0025] The sending module is configured to send the test output result to a server, so that the server generates an application test report according to the test output result and the interface calling information.

[0026] In a sixth aspect, an embodiment of the present application provides an application test method, applied to a server, and the method comprises the following steps:

[0027] The first obtaining module is configured to obtain interface calling information collected from the application to be collected, wherein the interface calling information comprises interface external calling information and interface internal calling information.

[0028] The second obtaining module is configured to obtain test output result collected from the application to be tested, wherein the test output result is obtained by testing the application to be tested by a test terminal according to the interface calling information.

[0029] The generating module is configured to generate an application test report according to the interface calling information and the test output result.

[0030] In a seventh aspect, an embodiment of the present application further provides an application test system, and the system comprises:

[0031] The collecting terminal is configured to obtain a to-be-collected interface identifier of an application to be collected, and determine a to-be-collected interface according to the to-be-collected interface identifier; collect interface calling information of the to-be-collected interface; and send the interface calling information to a test terminal, so that the test terminal tests an application to be tested according to the interface calling information; wherein the to-be-collected interface identifier comprises an external calling interface identifier and an internal calling interface identifier, and the interface calling information comprises interface external calling information and interface internal calling information.

[0032] The test terminal is configured to obtain interface calling information collected from the application to be collected; test the application to be tested according to the interface calling information, to obtain test output result of the application to be tested; and send the test output result to a server, so that the server generates an application test report according to the test output result and the interface calling information.

[0033] The server is configured to obtain interface calling information collected from the application to be collected; obtain test output result collected from the application to be tested; and generate an application test report according to the interface calling information and the test output result; wherein the interface calling information comprises interface external calling information and interface internal calling information, and the test output result is obtained by testing the application to be tested by a test terminal according to the interface calling information.

[0034] In an eighth aspect, the embodiments of the present application further provide an electronic device, comprising: a processor; and a memory for storing instructions executable by the processor, wherein the processor is configured to execute the instructions to implement the application testing method.

[0035] In a ninth aspect, the embodiments of the present application further provide a computer-readable storage medium, when instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform the application testing method.

[0036] In the embodiments of the present application, the following steps are included: obtaining a to-be-collected interface identifier of a to-be-collected application, and determining a to-be-collected interface according to the to-be-collected interface identifier, wherein the to-be-collected interface identifier comprises an external calling interface identifier and an internal calling interface identifier; collecting interface calling information of the to-be-collected interface, wherein the interface calling information comprises external calling information and internal calling information; and sending the interface calling information to a testing end, so that the testing end tests the to-be-tested application according to the interface calling information. The application can collect interface calling information of a to-be-collected application during running of the to-be-collected application, and test a to-be-tested application according to the interface calling information of the to-be-collected application, without requiring a tester to manually prepare test data for the to-be-tested application, thereby improving the efficiency of application testing. Moreover, since the collected interface calling information comprises interface external calling information and interface internal calling information, not only the external interface of the to-be-tested application can be tested, but also the internal interface of the to-be-tested application can be tested, thereby improving the effect of application testing. In the case that the to-be-collected application and the to-be-tested application are different, even if they do not have the same external interface, the same internal interface can be tested through the interface internal calling information, so that the present application can implement cross-application interface testing tasks, which helps to reduce the massive testing workload in large application reconstruction and migration. In addition, part of the interface calling information can be ignored during testing, so that the ignored interface calling information does not participate in the testing process of the to-be-tested application, which helps to improve the testing efficiency. Moreover, after obtaining the test results corresponding to the interface calling information, part of the test results are ignored, thereby improving the speed of generating a final test report.

[0037] The above description is only a summary of the technical solutions of the present application. In order to more clearly understand the technical means of the present application, the embodiments of the present application can be implemented according to the content of the description, and in order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the following specific embodiments of the present application are described. BRIEF DESCRIPTION OF DRAWINGS

[0038] Various other advantages and benefits will become apparent to those of ordinary skill in the art, upon reading the following detailed description of the preferred embodiment. The accompanying drawings are included to provide a better understanding of the preferred embodiment, and are not intended to constrain the application. Moreover, like reference numerals denote similar parts throughout the present drawings. In the drawings:

[0039] Figure 1 is a step flow chart of an application testing method provided by an embodiment of the present application;

[0040] Figure 2 is a step flow chart of another application testing method provided by an embodiment of the present application;

[0041] Figure 3 is a step flow chart of still another application testing method provided by an embodiment of the present application;

[0042] Figure 4 is a structure diagram of an application testing device provided by an embodiment of the present application;

[0043] Figure 5 is a structure diagram of another application testing device provided by an embodiment of the present application;

[0044] Figure 6 is a structure diagram of still another application testing device provided by an embodiment of the present application;

[0045] Figure 7 is a logic block diagram of an electronic device of an embodiment of the present application;

[0046] Figure 8 is a logic block diagram of an electronic device of another embodiment of the present application. DETAILED DESCRIPTION

[0047] Exemplary embodiments of the present application will be described herein below with reference to the accompanying drawings. Although exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete, and will fully convey the scope of the application to those skilled in the art.

[0048] Figure 1 is a step flow chart of an application testing method provided by an embodiment of the present application, as shown in Figure 1 the method comprises:

[0049] In step 101, a to-be-collected interface identifier of a to-be-collected application is acquired, and a to-be-collected interface is determined according to the to-be-collected interface identifier, wherein the to-be-collected interface identifier comprises an external calling interface identifier and an internal calling interface identifier.

[0050] In the embodiments of the present application, the collection end can be a terminal device running the application to be collected, or can be another terminal device other than the terminal device running the application to be collected. In the case where the collection end is the terminal device running the application to be collected, a test subprogram can be embedded in the application to be collected, the embedded subprogram is started synchronously with the application to be collected when the application to be collected is running, and the collection end obtains the interface identifier to be collected of the application to be collected from the server, or reads the preset interface identifier to be collected of the application to be collected. In the case where the collection end is another terminal device other than the terminal device running the application to be collected, the terminal device running the application to be collected can send a start instruction to the collection end when the application to be collected is started, so that the collection end obtains the interface identifier to be collected of the application to be collected, and monitors the interface of the application to be collected according to the interface identifier to be collected.

[0051] The interface identifier to be collected refers to the identifier of an interface that needs to be monitored and the interface call information of which needs to be collected by the collection end among all interfaces that can be called by the application to be collected. According to the interface identifier to be collected, the collection end can determine the interface to be collected in the application to be collected that needs to be monitored. The interface to be collected can include an HTTP interface, a dubbo interface, or any type of interface. If the interface identifier to be collected includes the identifier of the HTTP interface of the application to be collected, the collection end can identify the HTTP interface call request for calling the HTTP interface of the application to be collected according to the identifier of the HTTP interface, so as to monitor the HTTP interface of the application to be collected by monitoring the HTTP interface call request sent to the application to be collected.

[0052] It should be noted that, in the embodiments of the present application, monitoring a certain interface of the application to be collected is essentially achieved by monitoring the call request for calling the interface, and the call request can include an external call request and an internal call request. Therefore, the call interface identifier can include an external call interface identifier and an internal call interface identifier, the external call of the interface of the application to be collected can be monitored according to the external call interface identifier, and the internal call of the interface of the application to be collected can be monitored according to the internal call interface identifier.

[0053] When the external calling request calls the interface outside the application to be collected, the external calling request can cause other interface calling requests inside the application program. For example, if the application to be collected is a shopping application, an external calling request for obtaining product information calls the HTTP interface of the application to be collected. In order to respond to the external calling request for obtaining product information, the application to be collected needs to generate an interface calling request for obtaining the remaining quantity of the product, an interface calling request for obtaining the product image, an interface calling request for obtaining the product price, and the like inside the application program. The above-mentioned interface calling requests for obtaining the remaining quantity of the product, the product image, and the product price are interface internal calls.

[0054] Further, the interface internal call can also include multi-level interface internal calls. The interface internal call directly caused by the interface external call can be a first-level interface internal call, the interface internal call directly caused by the first-level interface internal call can be a second-level interface internal call, and so on. Continuing the above example, the interface calling request for obtaining the product price can be a first-level interface calling request, and the interface calling caused by the first-level interface calling request can be a first-level interface internal call. After the first-level interface calling request is triggered, a second-level interface internal call for obtaining the original price of the product and a second-level interface internal call for obtaining the current price of the product can also be triggered.

[0055] Optionally, step 101 comprises:

[0056] Sub-step 1011, sending a configuration information loading request to the server.

[0057] In the embodiment of the present application, a configuration information loading request can be sent to the server to determine the application to be collected, the interface to be collected, the terminal device running the application to be collected, and the like.

[0058] Sub-step 1012, receiving the configuration information sent by the server and obtaining the interface to be collected of the application to be collected from the configuration information.

[0059] Step 102, collecting the interface calling information of the interface to be collected, wherein the interface calling information comprises interface external calling information and interface internal calling information.

[0060] Since the interface calling of the application to be collected comprises interface external calling and interface internal calling caused by the interface external calling, in the embodiment of the present application, the interface calling information to be collected comprises not only the interface external calling information of the application to be collected, but also the interface internal calling information of the application to be collected.

[0061] It should be noted that the interface internal call information can include multiple levels of interface internal call information, such as first-level interface internal call information triggered by an interface external call, second-level interface call information triggered by the first-level interface internal call, and the like. In this way, for each external call of the to-be-collected application, full call information triggered by the external call can be obtained.

[0062] Optionally, step 102 comprises:

[0063] Sub-step 1021: collecting interface external call information generated when the external call request calls the to-be-collected interface.

[0064] In the embodiment of the present application, all external call requests for the to-be-collected application can be monitored, the interface call address of each external call request for the to-be-collected application can be obtained, and the interface call address of the external call request is compared with the to-be-collected interface identifier to determine whether the interface called by the external call request is the to-be-collected interface.

[0065] For example, if the to-be-collected interface includes an HTTP interface, the HTTP interface identifier of the to-be-collected application is “ / riskService” (i.e., the call path of the HTTP interface of the to-be-collected application), and the call address of a certain external call request is “https: / / xx.xx.xx.xx / riskService”, the external call request is a call request for calling the HTTP interface of the to-be-collected application. Wherein “xx.xx.xx.xx” represents the identifier or address of the terminal device running the to-be-collected application.

[0066] The interface external call information can include call input parameters and interface external call results. If it is determined that the interface called by a certain external call request is the to-be-collected interface, the call input parameters of the external call request are obtained, and the interface external call results output by the to-be-collected interface called by the external call request are obtained.

[0067] For example, the call input parameters of a certain external call request for the to-be-collected interface of the to-be-collected application can be a product identifier, and the interface external call results output by the to-be-collected interface called by the external call request can be product information of the product corresponding to the product identifier.

[0068] Optionally, sub-step 1021 comprises:

[0069] Sub-step A1: determining the interface external call program triggered when the to-be-collected interface is called by the external call request.

[0070] When the interface to be collected application is called, the interface to be collected application will certainly respond and process the call through some programs (such as classes, methods, functions, etc.) in the interface to be collected application. Therefore, in the embodiment of the application, in order to obtain more complete call information, the program triggered by the interface to be collected application in response to the call of the interface to be collected can be directly monitored to obtain more complete interface call information. Therefore, in the embodiment of the application, the external call information can include an interface external call program, an interface external call input parameter and an interface external call result.

[0071] In the interface to be collected application, different programs are needed to process and respond to the calls of different interfaces. Therefore, a correspondence between the interface external call program triggered when each interface to be collected is called by an external call request and the interface to be collected can be set in advance, and when the external call request is obtained, the interface external call program corresponding to the interface to be collected called by the external call request is directly monitored.

[0072] In the embodiment of the application, the interface external call program can be monitored through the ByteBuddy technology. ByteBuddy is a code generation and operation library for creating and modifying Java programs (classes, methods, functions, etc.) at runtime of a Java application without the help of a compiler. Through ByteBuddy, the classes, methods, functions, etc. being run in the interface to be collected application can be monitored during the running of the interface to be collected application.

[0073] It should be noted that the correspondence between the interface external call program triggered when each interface to be collected is called by an external call request and the interface to be collected can be stored in the collection end in advance, or can be obtained from the server when the collection task is started by the collection end, and the application does not specifically limit the obtaining mode of the correspondence.

[0074] Substep A2: determining the interface external call input parameter according to the input of the interface external call program.

[0075] In the embodiment of the application, a corresponding monitoring subprogram can be set for each interface to be collected, and each monitoring subprogram can monitor the interface external call program of the corresponding interface to be collected. When the interface to be collected is called by an external call request, the input of the interface external call program is obtained, and the input is determined as the interface external call input parameter corresponding to the external call request.

[0076] It should be noted that each interface to be collected can correspond to more than one interface external call program, and therefore, each external call request can correspond to more than one interface external call input parameter.

[0077] Sub-step A3, determining the interface external call result according to the output of the interface external call program.

[0078] In the embodiment of the present application, a corresponding monitoring sub-program can be set for each interface to be collected, each monitoring sub-program can monitor the interface external call program of the corresponding interface to be collected, when the interface to be collected is called by an external call request, the output of the interface external call program is obtained, and the output is determined as the interface external call result corresponding to the external call request.

[0079] It should be noted that each interface to be collected can correspond to more than one interface external call program, therefore, each external call request can correspond to more than one interface external call result.

[0080] Sub-step 1022, collecting the interface internal call information generated when the internal call request generated by the external call request calls the interface to be collected.

[0081] In the embodiment of the present application, the internal call request triggered by the external call request can be monitored, the interface call address of each internal call request is obtained, and the interface call address of the internal call request is compared with the interface to be collected to determine whether the interface called by the internal call request is the interface to be collected.

[0082] The interface internal call information can include the call input parameter and the interface internal call result, if it is determined that the interface called by a certain internal call request is the interface to be collected, the call input parameter of the internal call request is obtained, and the interface internal call result output by the interface to be collected called by the internal call request is obtained.

[0083] Sub-step B1, collecting the interface internal call program triggered when the interface to be collected is called by the internal call request.

[0084] In the embodiment of the present application, for the internal call request generated by the external call request, the interface call information can be collected by monitoring the corresponding interface internal call program.

[0085] When the interface of the application to be collected is called, the application to be collected must be implemented through some programs (such as classes, methods, functions, etc.) in the application to be collected in order to respond and process the call. Therefore, in the embodiment of the present application, in order to obtain more complete call information, the program triggered by the application to be collected in response to the call to the interface to be collected can be directly monitored to obtain more complete interface call information. Therefore, in the embodiment of the present application, the external call information can include the interface external call program, the interface external call input parameter and the interface external call result.

[0086] In the application to be collected, different interface calls need to be processed and responded by different programs. Therefore, the correspondence between the interface internal call program triggered when each interface to be collected is called by an internal call request and the interface to be collected can be set in advance. When the internal call request is obtained, the interface internal call program corresponding to the interface to be collected called by the internal call request is directly monitored.

[0087] In the embodiment of the present application, the interface internal call program can be monitored by ByteBuddy technology.

[0088] It should be noted that the correspondence between the interface internal call program triggered when each interface to be collected is called by an internal call request and the interface to be collected can be stored in the collection end in advance, or can be obtained from the server when the collection end starts the collection task. The present application does not specifically limit the acquisition method of the above correspondence.

[0089] Substep B2: determining the interface internal call input according to the input of the interface internal call program.

[0090] In the embodiment of the present application, a corresponding monitoring subprogram can be set for each interface to be collected. Each monitoring subprogram can monitor the interface internal call program of the corresponding interface to be collected. When the interface to be collected is called by an internal call request, the input of the interface internal call program is obtained, and the input is determined as the interface internal call input corresponding to the internal call request.

[0091] It should be noted that each interface to be collected can correspond to more than one interface internal call program. Therefore, each internal call request can correspond to more than one interface internal call input.

[0092] Substep B3: determining the interface internal call result according to the output of the interface internal call program.

[0093] In the embodiment of the present application, a corresponding monitoring subprogram can be set for each interface to be collected. Each monitoring subprogram can monitor the interface internal call program of the corresponding interface to be collected. When the interface to be collected is called by an internal call request, the output of the interface internal call program is obtained, and the output is determined as the interface internal call result corresponding to the internal call request.

[0094] It should be noted that each interface to be collected can correspond to more than one interface internal call program. Therefore, each internal call request can correspond to more than one interface internal call result.

[0095] Step 103: sending the interface call information to the test end, so that the test end tests the application to be tested according to the interface call information.

[0096] In the embodiment of the present application, the collection end can collect the calling information of the to-be-collected interface of the to-be-collected application. After the interface calling information is collected, the interface calling information can be sent to the test end, so that the test end tests the to-be-tested application according to the interface calling information.

[0097] Specifically, the interface calling information can be directly sent to the test end after each interface calling information is collected. Alternatively, all the interface calling information collected in the collection task can be packaged and sent to the test end after each collection task is completed.

[0098] Optionally, step 103 comprises:

[0099] The interface calling information is sent to the message middleware, so that the message middleware asynchronously transmits the calling information to the test end.

[0100] In the embodiment of the present application, the message middleware can be further provided, which can be used to forward the interface calling information sent by the collection end to the test end. After each interface calling information is collected, the collection end can directly send the interface calling information to the message middleware. The message middleware establishes a connection with the test end and selects a suitable sending mode to send the message middleware to the test end, so as to realize the asynchronous sending of the interface calling information. The collection end does not need to send the next interface calling information after receiving the delivery reminder of the test end, and does not need to consider whether the interface calling information is delivered to the test end. Each interface calling information is directly sent to the message middleware, so as to avoid the accumulation of interface calling information in the collection end and affect the collection efficiency and collection effect of the collection end. The message middleware can use the Apache Kafka system. Kafka is a high-throughput distributed publish / subscribe message system, which can process all action stream data of consumers in a website.

[0101] In summary, the application testing method provided in this application includes: obtaining the interface identifier of the application to be tested, and determining the interface to be tested based on the interface identifier, wherein the interface identifier includes an external call interface identifier and an internal call interface identifier; collecting the interface call information of the interface to be tested, wherein the interface call information includes external call information and internal call information; and sending the interface call information to the test terminal so that the test terminal can test the application to be tested based on the interface call information. This application can collect the interface call information of the application to be tested during the application's operation and test the application to be tested based on the interface call information, eliminating the need for testers to manually prepare test data for the application to be tested, thus improving the efficiency of application testing. Furthermore, since the collected interface call information includes both external and internal interface call information, it can test not only the external interfaces of the application to be tested but also the internal interfaces, improving the effectiveness of application testing.

[0102] Figure 2 This is a flowchart of another application testing method provided in this application embodiment, applied to the testing end, such as... Figure 2 As shown, the method includes:

[0103] Step 201: Obtain interface call information collected from the application to be collected, wherein the interface call information includes external interface call information and internal interface call information.

[0104] In this embodiment, the test terminal can be a terminal device running the application under test, or it can be a terminal device other than the one running the application under test. When the test terminal is a terminal device running the application under test, a test subroutine can be embedded within the application under test. This subroutine can be run when testing is required, and it starts synchronously with the application under test. The embedded subroutine receives interface call information sent from the acquisition terminal, enabling the test terminal to obtain the interface call information used to test the application under test. When the test terminal is a terminal device other than the one running the application under test, the test terminal can send a start command to the terminal device running the application under test upon receiving a test instruction for the application under test, and receive interface call information sent from the acquisition terminal, thereby testing the application under test using the interface call information.

[0105] Optionally, step 201 includes:

[0106] Sub-step 2011: Obtain the interface call information of the application to be collected from the message middleware, and delete the interface call information from the message middleware, wherein the interface call information is sent to the message middleware by the collection end.

[0107] In the embodiment of the present application, in order to enable the interface call information to be transmitted asynchronously between the collection end and the test end, the interface call information sent by the collection end can be received by the message middleware, and the test end can obtain the interface call information of the application to be collected from the message middleware.

[0108] Further, in order to save the storage space of the message middleware and avoid the performance of the message middleware from being degraded due to more and more interface call information stored, after the test end obtains the interface call information from the message middleware, the interface call information can be deleted from the message middleware.

[0109] Sub-step 2012, storing the interface call information into the target storage.

[0110] Since the test process can be performed multiple times, the interface call information deleted from the message middleware can be stored into the target storage again, so as to persistently save the interface call information deleted from the message middleware and facilitate subsequent use.

[0111] Step 202, testing the application to be tested according to the interface call information, to obtain the test output result of the application to be tested.

[0112] Since each interface call information contains a call request, after the interface call information is obtained, the call request in the interface call information can be sent to the application to be tested, so as to test the interface corresponding to the call request in the application to be tested, and obtain the test output result output by the interface in response to the call request.

[0113] In the embodiment of the present application, after each interface call request is used to test the application to be tested, the test output result corresponding to the interface call request can be obtained.

[0114] Optionally, step 202 includes:

[0115] Sub-step 2021, obtaining the simulation test result corresponding to the white list call information.

[0116] For a complex external call, its internal call may involve a very large number of internal calls, for example, a certain business of an application exposes an HTTP interface to the outside, and the business can be implemented by external calling the HTTP interface, but in the internal business logic of the HTTP interface, a plurality of internal calls (such as querying an HTTP interface, querying a DUBBO interface, querying a mysql database, querying a hbase database, querying an es database, and then writing an es database, writing an hbase database, etc.) may need to be performed. The external call request for executing the business generates an interface external call information and a plurality of interface internal call information, and some interface call information in the interface call information may not be suitable for direct testing in the application to be tested. Therefore, these interfaces that are not suitable for direct calling can be stored in the test whitelist, and when testing the interfaces in the test whitelist, a calling request can not be sent to the interface of the application to be tested, but the interface call result in the interface call information can be directly obtained as the test output result of the interface in the test whitelist.

[0117] For example, a certain dubbo interface can be a paid interface, and the fee is charged according to the number of calls. If the interface call information collected by the collection end contains the interface call information of the dubbo interface, the test end can not be suitable for direct testing of the interface call information, and the dubbo interface can be stored in the test whitelist. When testing the dubbo interface in the application to be tested, a calling request can not be sent to the dubbo interface of the application to be tested, but the interface call result in the interface call information can be directly obtained as the test output result of the dubbo interface.

[0118] For example, in some cases, the collection end and the test end are not completely data isolated, and there can be a common database. Since the collection end is generally a normally running production environment, and the application to be collected directly provides services to users, and the test end is a test environment of the application, if the test end performs a write operation on the database, the data of the production environment can be affected, and errors can occur in the downstream business. Therefore, for some interfaces that write data to the database, the interfaces can also be placed in the interface whitelist to avoid affecting the production environment by writing content in the database during the testing process of the test end.

[0119] Substep 2022, in the case where the interface call information matches the whitelist call information, the simulation test result corresponding to the whitelist call information is determined as the test output result corresponding to the interface call information.

[0120] In the embodiment of the present application, the interfaces in the interface white list can be tested through mock testing. Mock testing is an application testing method in which a virtual object is created to test some objects that are not easy to construct or obtain during testing. The skilled in the art can pre-set the interface white list and send the interface white list to the collection end in the stage of collecting configuration information. When the collection end collects the interface information of the interfaces in the interface white list, the collection end can generate mock data corresponding to the interface according to the interface calling result of the interface and send the mock data to the testing end. The testing end can match the interface calling information according to the interface white list, determine the interface calling information corresponding to the interfaces in the interface white list as white list calling information, and directly use the mock data corresponding to the white list calling information as the test output result when testing the application to be tested through the white list calling information.

[0121] In the case where the interface calling information contains the interface calling result of the application to be collected, the interface calling result in the white list calling information can be directly used as the test output result corresponding to the white list calling information.

[0122] Sub-step 2023: In the case where the interface calling information does not match the white list calling information, testing the application to be tested according to the interface calling information to obtain the test output result of the application to be tested.

[0123] Optionally, sub-step 2023 includes:

[0124] Sub-step C1: obtaining an interface calling request from the interface calling information, wherein the interface calling request includes an interface internal calling request and an interface external calling request.

[0125] Sub-step C2: sending the interface calling request to the application to be tested to obtain the test output result generated by the application to be tested.

[0126] In the embodiment of the present application, the interface calling request can include two types of interface internal calling request and interface external calling request. In the testing process, the interface corresponding to the interface external calling request can be tested externally, that is, the interface external calling request is sent to the interface exposed by the application to be tested, and the output result of the application to be tested to the outside is obtained as the test output result of the interface external calling request. The interface corresponding to the interface internal calling request can be tested internally, that is, the interface internal calling request is sent to the interface of the application to be tested, and the test output result corresponding to the interface internal calling request is obtained.

[0127] Optionally, sub-step C2 includes:

[0128] Sub-step c1, obtaining an interface calling program identifier and interface calling input parameters from the interface calling information, wherein the interface calling program identifier comprises an interface external calling program identifier and an interface internal calling program identifier, and the interface calling input parameters comprise interface external calling input parameters and interface internal calling input parameters.

[0129] In the embodiment of the present application, since the collection end can monitor the interface calling program of the application to be collected, and obtain the identifier and input parameters of the interface calling program corresponding to the interface when the interface is called, the interface calling information received by the test end can further contain the identifier of the interface calling program used to execute the calling request in the application to be collected, and the interface calling input parameters corresponding to the interface calling program.

[0130] It should be noted that the interface calling program identifier can comprise a multi-level program identifier. For example, in the case of a method, the interface calling program identifier can contain the method identifier of the method, and can also contain the class identifier of the class to which the method belongs. The interface calling input parameters can not only contain parameter values, but also contain the input type of the parameter values, such as int type, char type, etc.

[0131] For example, if a certain calling request activates the following method in the application to be collected:

[0132] package com.java4all.grouth.designmode.template;

[0133] public class Basketball extends Game{

[0134] public String test(String username, Integer age){

[0135] return userName + “:” + age;}

[0136] Wherein, test is the method name activated;

[0137] test(String, Integer) is the identifier of the method;

[0138] com.java4all.grouth.designmode.template is the package name of the class to which the method belongs;

[0139] Basketball is the class name of the class to which the method belongs;

[0140] com.java4all.grouth.designmode.template.Basketball is the identifier of the class.

[0141] The interface call information of the calling request can include the class identifier com.java4all.grouth.designmode.template.Basketball and the method identifier test(String, Integer). The interface call input parameter of the calling request can include the parameter value of the userName input into the test method and the parameter type corresponding to the parameter value.

[0142] In sub-step c2, the interface call input parameter is input into the interface call program of the application to be tested, and the test output result output by the interface call program of the application to be tested is obtained.

[0143] In the test process, after the interface call program identifier is obtained from the interface call information, the interface call input parameter corresponding to the interface call program identifier can be directly input into the program corresponding to the interface call program identifier in the application to be tested, and the output result of the program is obtained as the test output result of the interface call information.

[0144] In this way, even if the application to be collected and the application to be tested are different, in the case that the application to be tested cannot respond to the interface call request that can be responded by the application to be collected, as long as the same program (such as a function, a class, a method, etc.) exists in the application to be collected and the application to be tested, the interface call information collected from the application to be collected can be used to complete the test of the application to be tested, and the application range of the application test method is improved.

[0145] In step 203, the test output result is sent to the server, so that the server generates an application test report according to the test output result and the interface call information.

[0146] After the test end tests the application to be tested according to the interface call information, the test output result corresponding to each interface call request output by the application to be tested is obtained. In an embodiment, the test end can directly compare the test output result of the corresponding application to be tested with the interface call result of the application to be collected, and generate an application test report of the application to be tested. If the test output result and the interface call result of the same interface call request are different, it indicates that the response process of the same interface call request of the application to be collected and the application to be tested is different, that is, the corresponding interface of the application to be tested may have a problem and needs to be further processed.

[0147] In another real-time manner, the test end can not output a final application test report at the local end after obtaining the test output result of each interface call request, but can send the test output result to the service end, the service end compares the test output result with the interface call result of the application to be collected, and generates an application test report.

[0148] Optionally, step 203 comprises:

[0149] The test output result is sent to the message middleware, so that the message middleware transmits the test output result to the service end asynchronously.

[0150] Specifically, the message middleware can be further provided, which can be used to forward the test output result sent by the test end to the service end. After collecting each interface call information, the collection end can directly send the test output result to the message middleware, the message middleware establishes a connection with the service end, and selects an appropriate sending mode to send the message middleware to the service end, so as to realize the asynchronous sending of the test output result. The test end does not need to send the next test output result after receiving the delivery reminder of the service end, and does not need to consider whether the test output result is delivered to the service end. Each test output result is directly sent to the message middleware, so as to avoid the accumulation of test output results in the test end, and to affect the test efficiency and test effect of the test end. The message middleware can use Apache Kafka system. Kafka is a high-throughput distributed publish / subscribe message system, which can process all action stream data of consumers in the website.

[0151] It should be noted that the collection end or the test end can also send the interface call result to the service end, so that the service end compares the interface call result with the test output result to generate an application test report.

[0152] In summary, another application test method provided by the embodiment of the application comprises: obtaining interface call information collected from an application to be collected, wherein the interface call information comprises interface external call information and interface internal call information; testing the application to be tested according to the interface call information to obtain test output result of the application to be tested; and sending the test output result to the service end, so that the service end generates an application test report according to the test output result and the interface call information. The application can collect the interface call information of the application to be collected during the running of the application to be collected, and test the application to be tested according to the interface call information of the application to be collected. The test personnel do not need to manually prepare test data for the application to be tested, which improves the efficiency of application testing. Moreover, since the collected interface call information comprises interface external call information and interface internal call information, the external interface of the application to be tested can be tested, and the internal interface of the application to be tested can also be tested, which improves the effect of application testing.

[0153] Figure 3 is another step flowchart of an application test method provided by an embodiment of the present application, applied to a service end, as shown in the figure, the method comprises: Figure 3

[0154] Step 301, obtaining interface call information collected from a to-be-collected application, wherein the interface call information comprises interface external call information and interface internal call information.

[0155] In the embodiment of the present application, in order to enable the interface call information to be transmitted asynchronously between the collection end and the service end, the interface call information sent by the collection end can be received by the message middleware, and then the interface call information of the to-be-collected application is obtained from the message middleware by the service end.

[0156] Further, in order to save the storage space of the message middleware and avoid the performance degradation of the message middleware due to the increasing storage of the interface call information, the interface call information can be deleted from the message middleware after the service end obtains the interface call information from the message middleware.

[0157] Since the test process may need to be performed multiple times, the interface call information deleted from the message middleware can be stored in a target storage again, so as to persistently save the interface call information deleted from the message middleware, facilitating subsequent use.

[0158] Step 302, obtaining test output results collected from a to-be-tested application, wherein the test output results are obtained by the test end by testing the to-be-tested application through the interface call information.

[0159] In the embodiment of the present application, in order to enable the test output results to be transmitted asynchronously between the test end and the service end, the test output results sent by the test end can be received by the message middleware, and then the test output results are obtained from the message middleware by the service end.

[0160] Further, in order to save the storage space of the message middleware and avoid the performance degradation of the message middleware due to the increasing storage of the test output results, the test output results can be deleted from the message middleware after the service end obtains the test output results from the message middleware.

[0161] Since the test process may need to be performed multiple times, the test output results deleted from the message middleware can be stored in a target storage again, so as to persistently save the test output results deleted from the message middleware, facilitating subsequent use.

[0162] Step 303, generating an application test report according to the interface call information and the test output results.​

[0163] In the embodiment of the present application, the server can directly splice, combine, or process the interface calling information and the test output result to obtain a test report containing the interface calling information and the test output result, so that the technician can analyze the test according to the test report and further adjust the application to be tested.

[0164] In addition, the server can generate an application test report after processing the interface calling information and the test output result. For example, the server can determine the interface identifier of the result of the application to be tested that has a problem, the identifier of the program that has a problem, the difference between the interface calling result and the test output result, and the like according to the interface calling information and the test output result.

[0165] It should be noted that the server can analyze the interface calling information and the test output result based on the analysis method and analysis rule set by the technician to determine the similarities and differences between the application to be tested and the application to be collected and generate a test report.

[0166] Optionally, step 303 comprises:

[0167] Sub-step 3031, obtaining the interface calling result from the interface calling information and the interface calling request corresponding to the interface calling result.

[0168] In the embodiment of the present application, the collection end will contain the interface calling request and the interface calling result generated by the corresponding interface after the corresponding interface is called in each piece of interface calling information when collecting the interface calling information. Therefore, the interface calling result can be obtained from the interface calling information, and the interface calling request corresponding to the interface calling result can be obtained.

[0169] Sub-step 3032, comparing the interface calling result corresponding to the interface calling request with the test output result corresponding to the interface calling request, and generating an application test report according to the comparison result.

[0170] In the embodiment of the present application, the test end can also send the interface calling request corresponding to the test output result when sending the test output result to the server. The interface calling request corresponding to the test output result is used to describe the interface calling request responded by the application to be tested to output the test output result. Therefore, after obtaining the interface calling result and the interface calling request corresponding to the interface calling result, the test output result corresponding to the interface calling request corresponding to the interface calling result can also be matched according to the corresponding relationship between the test output result and the interface calling request according to the interface calling request corresponding to the interface calling result, that is, the interface calling result corresponding to the interface calling request and the test output result corresponding to the interface calling request are determined, so that the interface calling result corresponding to the interface calling request and the test output result corresponding to the interface calling request can be compared subsequently.

[0171] Further, in the embodiments of the present application, the application to be collected can be different from the application to be tested, and the codes of the two can be different. Therefore, the interface call request to which the application to be collected can respond can not be normally responded by the application to be tested. Therefore, in addition to testing the application to be tested through the interface call request, the application to be tested can also be tested through the interface call input parameter and the interface call program. In this case, the interface call input parameter refers to the parameter input by the application to be collected to one or more interface call programs in order to respond to an interface call request, and the interface call result refers to the result output by the one or more interface call programs according to the interface call input parameter. The interface call program can include an interface external call program and an interface internal call program, and the interface call input parameter can include an interface external call input parameter and an interface internal call input parameter.

[0172] In the case where the application to be collected is different from the application to be tested, the test output result refers to the output of the interface call program after the interface call input parameter is input into the interface call program of the application to be tested. Therefore, the interface call program and the interface call result corresponding to the interface call program can be obtained from the interface call information, and the test output result corresponding to the same interface call program can be determined based on the correspondence between the interface call program and the test output result, so as to obtain the interface call result and the test output result corresponding to the same interface call program. The interface call result and the test output result corresponding to the same interface call program are compared in the subsequent process, and the application test report is obtained.

[0173] Optionally, the sub-step 3032 comprises:

[0174] Sub-step D1, obtaining the comparison rule of the interface call result corresponding to the interface call request.

[0175] Since the data structure and data content of the interface call result and the test output result are usually complex, for example, the interface call result and the test output result can be complex json objects or json strings, each comparison of the two requires a large amount of calculation, and when a large number of interface call results and test output results are compared, the efficiency is low.

[0176] Therefore, in the embodiment of the present application, for the interface call result corresponding to each interface call, a corresponding comparison rule can be set, in which the data structure that needs to be compared in the interface call result can be limited to eliminate the content in the interface call result that does not need to be compared, so as to achieve the effect of fast comparison. It should be noted that, since the interface call result and the test output result have the same data structure, for the test output result corresponding to the interface call result, the same comparison rule can also be used to limit the data structure that needs to be compared in the test output result, so as to eliminate the content in the test output result that does not need to be compared, thereby improving the comparison efficiency.

[0177] For example, when the interface B of the application to be collected is called by the interface call request A at the collection end, the interface call result C is collected, and the data structure of the interface call result C is as follows:

[0178]

[0179] When the interface B of the application to be tested is called by the interface call request A at the test end, the test output result D is obtained, and the data structure of the test output result D is as follows:

[0180]

[0181] Therefore, in the comparison rule corresponding to the interface call result C, only the value of a.b.c (i.e. "zhangsan") in the interface call result C can be specified to participate in comparison, and the values of a.b.d, a.b.e and a.i are ignored. Similarly, when the comparison rule is applied to the test output result D, only the value of a.b.c (i.e. "niumen") in the test output result D can be specified to participate in comparison, and the values of a.b.d, a.b.e and a.i are ignored.

[0182] In sub-step D2, first comparison content is determined from the interface call result based on the comparison rule, and second comparison content is determined from the test output result corresponding to the interface call request based on the comparison rule, wherein the first comparison content is part of the interface call result, and the second comparison content is part of the test output result.

[0183] According to the comparison rule corresponding to the interface call result, the first comparison content that needs to be compared can be extracted from the interface call result, and according to the comparison rule corresponding to the interface call result, the second comparison content that needs to be compared can be extracted from the test output result corresponding to the interface call result, so that the first comparison content with less content and the second comparison content with less content are compared, thereby avoiding comparing the entire interface call result and the test output result, reducing the consumption of operation resources, improving the comparison efficiency, and thereby improving the speed of generating the application test report.

[0184] Continuing with the example in the above sub-step D1, the first comparison content obtained by extracting the interface call result C according to the comparison rule corresponding to the interface call result C is zhangsan, and the second comparison content obtained by extracting the test output result D according to the comparison rule is niumen, so when comparing the interface call result C and the test output result D, only "zhangsan" and "niu men" need to be compared.

[0185] Sub-step D3, comparing the first comparison content and the second comparison content.

[0186] After obtaining the first comparison content and the second comparison content, the first comparison content and the second comparison content can be compared to obtain a comparison result, and a test report can be generated according to the comparison result.

[0187] Further, in the embodiment of the present application, after obtaining the comparison result, a comparison result management page can be provided to the user, and the comparison result management page can include consistent comparison results and inconsistent comparison results. The user can ignore the comparison results in the comparison result management page to discard the comparison results that the user is not interested in, thereby improving the efficiency of generating the test report.

[0188] In summary, another application test method provided by the embodiment of the present application includes: obtaining interface call information collected from a to-be-collected application, wherein the interface call information includes interface external call information and interface internal call information; obtaining test output results collected from a to-be-tested application, wherein the test output results are obtained by a test end by testing the to-be-tested application according to the interface call information; and generating an application test report according to the interface call information and the test output results. The present application can collect the interface call information of the to-be-collected application during the running process of the to-be-collected application, and test the to-be-tested application according to the interface call information of the to-be-collected application to obtain an application test report. The present application does not need a test personnel to manually prepare test data for the to-be-tested application, thereby improving the efficiency of application testing. Moreover, since the collected interface call information includes interface external call information and interface internal call information, the to-be-tested application can be tested not only from the external interface but also from the internal interface, thereby improving the effect of application testing.

[0189] Corresponding to the method provided by the application test method embodiment of the present application, referring to Figure 4 The present application also provides an application test device structure diagram. In the embodiment, the device includes:

[0190] The acquisition module 401 is configured to acquire a to-be-acquired interface identifier of a to-be-acquired application, and determine a to-be-acquired interface according to the to-be-acquired interface identifier, wherein the to-be-acquired interface identifier comprises an external calling interface identifier and an internal calling interface identifier.

[0191] The acquisition module 402 is configured to acquire interface calling information of the to-be-acquired interface, wherein the interface calling information comprises interface external calling information and interface internal calling information.

[0192] The sending module 403 is configured to send the interface calling information to a test end, so that the test end tests a to-be-tested application according to the interface calling information.

[0193] In an optional implementation, the acquisition module comprises:

[0194] The first acquisition submodule is configured to acquire interface external calling information generated when an external calling request calls the to-be-acquired interface.

[0195] The internal calling request submodule is configured to acquire an internal calling request generated by the external calling request.

[0196] The second acquisition submodule is configured to acquire interface internal calling information generated when the internal calling request generated by the external calling request calls the to-be-acquired interface.

[0197] In an optional implementation, the interface external calling information comprises an interface external calling program, interface external calling input parameters and interface external calling results, and the apparatus further comprises:

[0198] The external calling program module is configured to determine an interface external calling program triggered when the to-be-acquired interface is called by the external calling request.

[0199] The external calling input parameter module is configured to determine the interface external calling input parameters according to input of the interface external calling program.

[0200] The external calling result module is configured to determine the interface external calling results according to output of the interface external calling program.

[0201] In an optional implementation, the interface internal calling information comprises an interface internal calling program, interface internal calling input parameters and interface internal calling results, and the method further comprises:

[0202] The internal calling program module is configured to acquire an interface internal calling program triggered when the to-be-acquired interface is called by the internal calling request.

[0203] The internal call input parameter module is configured to determine the interface internal call input parameter according to an input of the interface internal call program.

[0204] The internal call result module is configured to determine the interface internal call result according to an output of the interface internal call program.

[0205] In an optional implementation, the obtaining module comprises:

[0206] The request sub-module is configured to send a configuration information loading request to the server.

[0207] The configuration sub-module is configured to receive the configuration information sent by the server, and obtain the to-be-collected interface identifier of the to-be-collected application from the configuration information.

[0208] In an optional implementation, the sending module comprises:

[0209] The sending sub-module is configured to send the interface call information to the message middleware, so that the message middleware asynchronously transmits the call information to the test end.

[0210] In summary, the application embodiment provides an application testing device, which comprises: an obtaining module, configured to obtain a to-be-collected interface identifier of a to-be-collected application, and determine a to-be-collected interface according to the to-be-collected interface identifier, wherein the to-be-collected interface identifier comprises an external call interface identifier and an internal call interface identifier; a collecting module, configured to collect interface call information of the to-be-collected interface, wherein the interface call information comprises interface external call information and interface internal call information; and a sending module, configured to send the interface call information to a test end, so that the test end tests a to-be-tested application according to the interface call information. The interface call information of the to-be-collected application can be collected during running of the to-be-collected application, and the to-be-tested application is tested according to the interface call information of the to-be-collected application, so that a tester does not need to manually prepare test data for the to-be-tested application, the efficiency of application testing is improved, and since the collected interface call information comprises the interface external call information and the interface internal call information, not only the external interface of the to-be-tested application can be tested, but also the internal interface of the to-be-tested application can be tested, so that the effect of application testing is improved.

[0211] Corresponding to the method provided by the application testing method embodiment of the application, referring to Figure 5 the application further provides another application testing device structure diagram, in this embodiment, the device comprises:

[0212] An obtaining module 411 is configured to obtain interface call information collected from a to-be-collected application, wherein the interface call information comprises interface external call information and interface internal call information.

[0213] The test module 412 is configured to test the application to be tested according to the interface calling information, to obtain a test output result of the application to be tested.

[0214] The sending module 413 is configured to send the test output result to a server, so that the server generates an application test report according to the test output result and the interface calling information.

[0215] In an optional implementation, the test module includes:

[0216] The first obtaining sub-module is configured to obtain an interface calling request from the interface calling information, wherein the interface calling request includes an internal interface calling request and an external interface calling request.

[0217] The first test sub-module is configured to send the interface calling request to the application to be tested, and obtain a test output result generated by the application to be tested.

[0218] In an optional implementation, the test module includes:

[0219] The second obtaining sub-module is configured to obtain an interface calling program identifier and an interface calling input parameter from the interface calling information, wherein the interface calling program identifier includes an internal interface calling program identifier and an external interface calling program identifier, and the interface calling input parameter includes an internal interface calling input parameter and an external interface calling input parameter.

[0220] The second test sub-module is configured to input the interface calling input parameter into an interface calling program of the application to be tested, and obtain a test output result output by the interface calling program of the application to be tested.

[0221] In an optional implementation, the test module includes:

[0222] The simulation test result sub-module is configured to obtain a simulation test result corresponding to the white list calling information.

[0223] The simulation test sub-module is configured to, in a case where the interface calling information matches the white list calling information, determine the simulation test result corresponding to the white list calling information as a test output result corresponding to the interface calling information.

[0224] The test sub-module is configured to, in a case where the interface calling information does not match the white list calling information, test the application to be tested according to the interface calling information, to obtain a test output result of the application to be tested.

[0225] In an optional implementation, the obtaining module includes:

[0226] The acquisition sub-module is configured to acquire interface calling information of the application to be collected from the message middleware, and delete the interface calling information from the message middleware, wherein the interface calling information is sent to the message middleware by the collection end.

[0227] The storage sub-module is configured to store the interface calling information into a target storage.

[0228] In an optional embodiment, the sending module comprises:

[0229] The sending sub-module is configured to send the test output result to the message middleware, so that the message middleware transmits the test output result to the service end asynchronously.

[0230] In summary, another application testing device provided by the embodiment of the application comprises: an acquisition module configured to acquire interface calling information collected from an application to be collected, wherein the interface calling information comprises interface external calling information and interface internal calling information; a testing module configured to test an application to be tested according to the interface calling information, and obtain a test output result of the application to be tested; and a sending module configured to send the test output result to a service end, so that the service end generates an application testing report according to the test output result and the interface calling information. The interface calling information of the application to be collected can be collected during the running of the application to be collected, and the application to be tested can be tested according to the interface calling information of the application to be collected. Therefore, the test personnel do not need to manually prepare test data for the application to be tested, the efficiency of application testing is improved, and the interface external calling information and the interface internal calling information are included in the collected interface calling information. Therefore, not only the external interface of the application to be tested can be tested, but also the internal interface of the application to be tested can be tested, and the effect of application testing is improved.

[0231] Corresponding to the method provided by the application testing method embodiment of the application, referring to Figure 6 The application further provides another application testing device structure diagram. In this embodiment, the device comprises:

[0232] The first acquisition module 421 is configured to acquire interface calling information collected from an application to be collected, wherein the interface calling information comprises interface external calling information and interface internal calling information.

[0233] The second acquisition module 422 is configured to acquire a test output result collected from an application to be tested, wherein the test output result is obtained by testing the application to be tested by a testing end through the interface calling information.

[0234] The generation module 423 is configured to generate an application testing report according to the interface calling information and the test output result.

[0235] In an optional implementation, the generating module comprises:

[0236] a first obtaining sub-module, configured to obtain an interface calling result and an interface calling request corresponding to the interface calling result from the interface calling information;

[0237] a comparing sub-module, configured to compare the interface calling result corresponding to the interface calling request with a test output result corresponding to the interface calling request, and generate an application test report according to a comparison result.

[0238] In an optional implementation, the comparing sub-module comprises:

[0239] a second obtaining sub-module, configured to obtain a comparison rule of the interface calling result corresponding to the interface calling request;

[0240] a comparison content sub-module, configured to determine first comparison content from the interface calling result based on the comparison rule, and determine second comparison content from the test output result corresponding to the interface calling request based on the comparison rule, wherein the first comparison content is part of the interface calling result, and the second comparison content is part of the test output result;

[0241] a content comparing sub-module, configured to compare the first comparison content with the second comparison content.

[0242] In summary, another application test device provided by the embodiment of the application comprises: a first obtaining module, configured to obtain interface calling information collected from a to-be-collected application, wherein the interface calling information comprises interface external calling information and interface internal calling information; a second obtaining module, configured to obtain a test output result collected from a to-be-tested application, wherein the test output result is obtained by a test end by testing the to-be-tested application through the interface calling information; and a generating module, configured to generate an application test report according to the interface calling information and the test output result. The application can collect interface calling information of a to-be-collected application during running of the to-be-collected application, and test a to-be-tested application according to the interface calling information of the to-be-collected application to obtain an application test report, without requiring a test personnel to manually prepare test data for the to-be-tested application, thereby improving the efficiency of application testing, and because the collected interface calling information comprises interface external calling information and interface internal calling information, not only the external interface of the to-be-tested application can be tested, but also the internal interface of the to-be-tested application can be tested, thereby improving the effect of application testing.

[0243] Corresponding to the method provided by the application test method embodiment of the application, the application further provides an application test system. In the embodiment, the system comprises:

[0244] The collection end is configured to acquire a to-be-collected interface identifier of a to-be-collected application, determine a to-be-collected interface according to the to-be-collected interface identifier, collect interface call information of the to-be-collected interface, and send the interface call information to the test end, so that the test end tests a to-be-tested application according to the interface call information. The to-be-collected interface identifier includes an external call interface identifier and an internal call interface identifier, and the interface call information includes interface external call information and interface internal call information.

[0245] The test end is configured to acquire the interface call information collected from the to-be-collected application, test the to-be-tested application according to the interface call information, obtain a test output result of the to-be-tested application, and send the test output result to the service end, so that the service end generates an application test report according to the test output result and the interface call information.

[0246] The service end is configured to acquire the interface call information collected from the to-be-collected application, acquire a test output result collected from the to-be-tested application, and generate an application test report according to the interface call information and the test output result. The interface call information includes interface external call information and interface internal call information, and the test output result is obtained by the test end testing the to-be-tested application according to the interface call information.

[0247] In an optional implementation, the collection of the interface call information of the to-be-collected interface includes:

[0248] The interface external call information generated when the external call request calls the to-be-collected interface is collected, the internal call request generated by the external call request is acquired, and the interface internal call information generated when the internal call request generated by the external call request calls the to-be-collected interface is collected.

[0249] In an optional implementation, the interface external call information includes an interface external call program, interface external call input parameters, and interface external call results. The collection end is further configured to determine the interface external call program triggered when the to-be-collected interface is called by the external call request, determine the interface external call input parameters according to the input of the interface external call program, and determine the interface external call results according to the output of the interface external call program.

[0250] In an optional implementation, the interface internal call information comprises an interface internal call program, an interface internal call input parameter and an interface internal call result, and the collection end is further configured to collect the interface internal call program triggered when the to-be-collected interface is called by the internal call request; determine the interface internal call input parameter according to the input of the interface internal call program; and determine the interface internal call result according to the output of the interface internal call program.

[0251] In an optional implementation, the to-be-collected interface identifier of the to-be-collected application is obtained by:

[0252] sending a configuration information loading request to the server end; receiving the configuration information sent by the server end; and obtaining the to-be-collected interface identifier of the to-be-collected application from the configuration information.

[0253] In an optional implementation, the interface call information is sent to the test end by:

[0254] the interface call information is sent to the message middleware, so that the message middleware asynchronously transmits the call information to the test end.

[0255] In an optional implementation, the to-be-tested application is tested according to the interface call information, and a test output result of the to-be-tested application is obtained by:

[0256] an interface call request is obtained from the interface call information, wherein the interface call request comprises an interface internal call request and an interface external call request; the interface call request is sent to the to-be-tested application, and a test output result generated by the to-be-tested application is obtained.

[0257] In an optional implementation, the to-be-tested application is tested according to the interface call information, and a test output result of the to-be-tested application is obtained by:

[0258] an interface call program identifier and an interface call input parameter are obtained from the interface call information; the interface call input parameter is input into an interface call program of the to-be-tested application, and a test output result output by the interface call program of the to-be-tested application is obtained, wherein the interface call program identifier comprises an interface external call program identifier and an interface internal call program identifier, and the interface call input parameter comprises an interface external call input parameter and an interface internal call input parameter.

[0259] In an optional implementation, the to-be-tested application is tested according to the interface call information, and a test output result of the to-be-tested application is obtained by:

[0260] acquire a simulation test result corresponding to the white list calling information; in a case where the interface calling information matches the white list calling information, determine the simulation test result corresponding to the white list calling information as a test output result corresponding to the interface calling information; in a case where the interface calling information does not match the white list calling information, test the to-be-tested application according to the interface calling information to obtain a test output result of the to-be-tested application.

[0261] In an optional implementation, the acquiring the interface calling information collected from the to-be-collected application comprises:

[0262] acquiring the interface calling information of the to-be-collected application from the message middleware and deleting the interface calling information from the message middleware; and storing the interface calling information into a target storage, wherein the interface calling information is sent to the message middleware by a collection end.

[0263] In an optional implementation, the sending the test output result to the server comprises:

[0264] sending the test output result to the message middleware, so that the message middleware asynchronously transmits the test output result to the server.

[0265] In an optional implementation, the generating an application test report according to the interface calling information and the test output result comprises:

[0266] acquiring an interface calling result and an interface calling request corresponding to the interface calling result from the interface calling information; comparing the interface calling result corresponding to the interface calling request with a test output result corresponding to the interface calling request, and generating an application test report according to a comparison result.

[0267] In an optional implementation, the comparing the interface calling result corresponding to the interface calling request with the test output result corresponding to the interface calling request comprises:

[0268] acquiring a comparison rule of the interface calling result corresponding to the interface calling request; determining first comparison content from the interface calling result based on the comparison rule and determining second comparison content from the test output result corresponding to the interface calling request based on the comparison rule; and comparing the first comparison content with the second comparison content, wherein the first comparison content is part of the interface calling result, and the second comparison content is part of the test output result.

[0269] In conclusion, the application embodiment provides the application test system, which can collect the interface calling information of the application to be collected during the running of the application to be collected, test the application to be tested according to the interface calling information of the application to be collected, and obtain the application test report, without the test personnel manually preparing the test data for the application to be tested, thereby improving the efficiency of the application test, and since the collected interface calling information includes the interface external calling information and the interface internal calling information, the external interface of the application to be tested can be tested, and the internal interface of the application to be tested can also be tested, thereby improving the effect of the application test.

[0270] Figure 7 FIG. 6 is a logic flow diagram of an example of an electronic device 600 in accordance with one or more aspects of the disclosure. The electronic device 600 can be, for example, a mobile phone, a computer, a digital broadcast terminal, a messaging device, a gaming console, a tablet device, a medical device, a fitness device, a personal digital assistant, or the like.

[0271] Referring to Figure 7 The electronic device 600 can include one or more of the following components: a processing component 602, a memory 604, a power supply component 606, a multimedia component 608, an audio component 610, an input / output (I / O) interface 612, a sensor component 614, and a communication component 616.

[0272] The processing component 602 usually controls overall operations of the electronic device 600, such as operations associated with displaying, making phone calls, data communications, camera operations, and recording operations. The processing component 602 can include one or more processors 620 to execute instructions to complete all or part of steps of the methods described above. In addition, the processing component 602 can include one or more modules to facilitate the interaction between the processing component 602 and other components. For example, the processing component 602 can include a multimedia module to facilitate the interaction between the multimedia component 608 and the processing component 602.

[0273] The memory 604 is used to store various types of data to support operations of the electronic device 600. Examples of these data include instructions for any application or method operating on the electronic device 600, contact data, phonebook data, messages, pictures, videos, and the like. The memory 604 can be implemented by any type of volatile or non-volatile storage devices or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0274] The power component 606 provides power to the various components of the electronic device 600. The power component 606 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the electronic device 600.

[0275] The multimedia component 608 includes a screen providing an output interface between the electronic device 600 and a user. In some embodiments, the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, swiping, and gestures on the touch panel. The touch sensors can not only sense a boundary of a touching or swiping action, but also detect duration and pressure related to the touching or swiping action. In some embodiments, the multimedia component 608 includes a front camera and / or a rear camera. When the electronic device 600 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each of the front camera and the rear camera can be a fixed optical lens system or have a focal length and optical zoom capability.

[0276] The audio component 610 is configured to output and / or input audio signals. For example, the audio component 610 includes a microphone (MIC) to receive an external audio signal when the electronic device 600 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal can be further stored in the memory 604 or transmitted via the communication component 616. In some embodiments, the audio component 610 also includes a speaker to output audio signals.

[0277] The I / O interface 612 provides an interface between the processing component 602 and peripheral interface modules, which can be a keyboard, a click wheel, buttons, and the like. The buttons can include, but are not limited to, a home button, a volume button, a start button, and a lock button.

[0278] The sensor component 614 includes one or more sensors for providing status assessments for various aspects of the electronic device 600. For example, the sensor component 614 can detect an open / closed position of the electronic device 600, relative positioning of components of the electronic device 600, such as a display and a keypad of the electronic device 600, a change in position of the electronic device 600 or a component of the electronic device 600, presence or absence of user contact with the electronic device 600, orientation or acceleration / deceleration / g-force and temperature changes of the electronic device 600. The sensor component 614 can include a proximity sensor configured to detect presence of nearby objects without any physical touch. The sensor component 614 can also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor component 614 can also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0279] The communication component 616 is configured to facilitate wired or wireless communication between the electronic device 600 and other devices. The electronic device 600 can access a wireless network based on a communication standard, such as WiFi, a cellular network standard (such as 2G, 3G, 4G, or 5G), or a combination thereof. In an example embodiment, the communication component 616 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In an example embodiment, the communication component 616 can further include a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on Radio Frequency Identification (RFID) techniques, infrared data association (IrDA) techniques, ultra-wideband (UWB) techniques, Bluetooth (BT) techniques, and other techniques.

[0280] In an example embodiment, the electronic device 600 can be implemented with one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, micro-controllers, microprocessors, or other electronic elements to implement a method for testing an application provided by the embodiments.

[0281] In an example embodiment, a non-transitory computer-readable storage medium including instructions, such as the memory 604 including instructions, is also provided. The instructions can be executed by the processor 620 of the electronic device 600 to complete the above-described method. For example, the non-transitory storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device, etc.

[0282] Figure 8FIG. 7 is a logic flow diagram of an electronic device 700 according to another embodiment of the present application. For example, the electronic device 700 can be provided as a server. Referring to FIG. 7, the electronic device 700 includes a processing component 722, which is further composed of one or more processors, and a memory resource represented by a memory 732 for storing instructions, such as an application program, executable by the processing component 722. The application program stored in the memory 732 can include one or more than one module each corresponding to a set of instructions. In addition, the processing component 722 is configured to execute the instructions to perform an application testing method according to an embodiment of the present application. Figure 8 The electronic device 700 further includes a power component 726 configured to perform power management of the electronic device 700, a wired or wireless network interface 750 configured to connect the electronic device 700 to a network, and an input / output (I / O) interface 758. The electronic device 700 can operate based on an operating system stored in the memory 732, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or the like.

[0283] The electronic device 700 further includes a power component 726 configured to perform power management of the electronic device 700, a wired or wireless network interface 750 configured to connect the electronic device 700 to a network, and an input / output (I / O) interface 758. The electronic device 700 can operate based on an operating system stored in the memory 732, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or the like.

[0284] An embodiment of the present application further provides a computer program product, including a computer program, which, when executed by a processor, implements the application testing method.

[0285] Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. It is intended that the present application cover any and all variations of the application that come within the scope of the claims and their equivalents. It is intended that the specification and examples be considered exemplary only, with the true scope and spirit of the application indicated by the following claims.

[0286] It is understood that the present application is not limited to the exact construction and arrangement of parts described and illustrated herein and that various modifications and changes can be made without departing from the scope thereof. The scope of the application is indicated by the following claims.

Claims

1. An application testing method, characterized in that, Applied to the acquisition end, the method includes: Obtain the interface identifier of the application to be collected, and determine the interface to be collected based on the interface identifier. The interface identifier includes an external call interface identifier and an internal call interface identifier. Collect the interface call information of the interface to be collected, wherein the interface call information includes external interface call information and internal interface call information; The interface call information is sent to the test terminal so that the test terminal can test the application under test based on the interface call information; the collection of the interface call information of the interface to be collected includes: When an external call request invokes the interface to be collected, the external call information generated is collected. Obtain the internal call request generated by the external call request; Collect all internal call information of the interface to be collected when the internal call request generated by the external call request calls the interface to be collected; Sending the interface call information to the test terminal includes: The interface call information is sent to the message middleware so that the message middleware asynchronously transmits the call information to the test end.

2. The method according to claim 1, characterized in that, The external interface call information includes the external interface call program, the external interface call input parameters, and the external interface call result. The method further includes: When the interface to be collected is invoked by the external call request, the interface external call program is triggered. The input parameters of the external call to the interface are determined based on the input of the external call program to the interface. The result of the external call to the interface is determined based on the output of the external call program.

3. The method according to claim 2, characterized in that, The internal call information of the interface includes the internal call program, the internal call parameters, and the internal call result. The method further includes: The internal interface call program is triggered when the interface to be collected is invoked by the internal call request; The input parameters of the internal call to the interface are determined based on the input of the internal calling program of the interface; The result of the internal call to the interface is determined based on the output of the program that calls the interface.

4. The method according to claim 1, characterized in that, The step of obtaining the interface identifier of the application to be collected includes: Send a configuration information loading request to the server; The system receives configuration information sent by the server and obtains the interface identifier of the application to be collected from the configuration information.

5. An application testing method, characterized in that, Applied to the testing end, the method includes: Obtain interface call information collected from the application to be collected, wherein the interface call information includes external interface call information and internal interface call information, wherein the internal interface call information includes: all internal interface call information generated when the internal call request generated by the external call request calls the interface to be collected; The application under test is tested based on the interface call information to obtain the test output results of the application under test; The test output results are sent to the server so that the server can generate an application test report based on the test output results and the interface call information; the step of testing the application under test based on the interface call information to obtain the test output results of the application under test includes: Obtain the interface call request from the interface call information, wherein the interface call request includes internal interface call request and external interface call request; Send the interface call request to the application under test and obtain the test output results generated by the application under test; Sending the test output results to the server includes: The test output results are sent to the message middleware, so that the message middleware asynchronously transmits the test output results to the server.

6. The method according to claim 5, characterized in that, The step of testing the application under test based on the interface call information and obtaining the test output results of the application under test includes: The interface caller identifier and interface call input parameters are obtained from the interface call information, wherein the interface caller identifier includes an external interface caller identifier and an internal interface caller identifier, and the interface call input parameters include external interface call input parameters and internal interface call input parameters; Input the interface call parameters into the interface call program of the application under test, and obtain the test output results output by the interface call program of the application under test.

7. The method according to claim 5, characterized in that, The step of testing the application under test based on the interface call information and obtaining the test output results of the application under test includes: Retrieve the simulation test results corresponding to the whitelist call information; If the interface call information matches the whitelist call information, the simulated test result corresponding to the whitelist call information is determined as the test output result corresponding to the interface call information. If the interface call information does not match the whitelist call information, the application to be tested is tested according to the interface call information to obtain the test output results of the application to be tested.

8. The method according to claim 5, characterized in that, The process of obtaining interface call information collected from the application to be collected includes: Obtain the interface call information of the application to be collected from the message middleware, and delete the interface call information from the message middleware, wherein the interface call information is sent to the message middleware by the collection end; The interface call information is stored in the target memory.

9. An application testing method, characterized in that, Applied to the server side, the method includes: The interface call information collected from the application to be collected is obtained and forwarded through a message middleware. The interface call information includes external interface call information and internal interface call information. The test output results collected from the application under test are obtained and forwarded through a message middleware. The test output results are obtained by the test end testing the application under test through the interface call information. An application test report is generated based on the interface call information and the test output results. The internal call information of the interface includes: all internal call information of the interface generated when the internal call request generated by the external call request calls the interface to be collected.

10. The method according to claim 9, characterized in that, The step of generating an application test report based on the interface call information and the test output results includes: Obtain the interface call result and the corresponding interface call request from the interface call information; The interface call result corresponding to the interface call request is compared with the test output result corresponding to the interface call request, and an application test report is generated based on the comparison result.

11. The method according to claim 10, characterized in that, The step of comparing the interface call result corresponding to the interface call request with the test output result corresponding to the interface call request includes: Obtain the comparison rules for the interface call results corresponding to the interface call request; Based on the comparison rules, a first comparison content is determined from the interface call result, and a second comparison content is determined from the test output result corresponding to the interface call request based on the comparison rules, wherein the first comparison content is a part of the interface call result, and the second comparison content is a part of the test output result; The first comparison content is compared with the second comparison content.

12. An application testing device, characterized in that, The device includes: The acquisition module is used to acquire the interface identifier of the application to be collected and determine the interface to be collected based on the interface identifier. The interface identifier includes an external call interface identifier and an internal call interface identifier. The acquisition module is used to acquire the interface call information of the interface to be acquired, wherein the interface call information includes external interface call information and internal interface call information; The sending module is used to send the interface call information to the test terminal, so that the test terminal can test the application to be tested according to the interface call information; Sending the interface call information to the test terminal includes: The interface call information is sent to the message middleware so that the message middleware asynchronously transmits the call information to the test end; The process of collecting the interface call information of the interface to be collected includes: When an external call request invokes the interface to be collected, the external call information generated is collected. Obtain the internal call request generated by the external call request; Collect all internal call information generated when the internal call request generated by the external call request calls the interface to be collected.

13. An application testing device, characterized in that, The device includes: The acquisition module is used to acquire interface call information collected from the application to be collected. The interface call information includes external interface call information and internal interface call information. The internal interface call information includes all internal interface call information generated when the internal call request generated by the external call request calls the interface to be collected. The testing module is used to test the application under test according to the interface call information and obtain the test output results of the application under test. The sending module is used to send the test output results to the server so that the server can generate an application test report based on the test output results and the interface call information. Sending the test output results to the server includes: The test output results are sent to the message middleware, so that the message middleware asynchronously transmits the test output results to the server. The step of testing the application under test based on the interface call information and obtaining the test output results of the application under test includes: Obtain the interface call request from the interface call information, wherein the interface call request includes internal interface call request and external interface call request; Send the interface call request to the application under test and obtain the test output results generated by the application under test.

14. An application testing device, characterized in that, The device includes: The first acquisition module is used to acquire interface call information collected from the application to be collected. The interface call information is forwarded through a message middleware. The interface call information includes external interface call information and internal interface call information. The internal interface call information includes all internal interface call information generated when an internal call request generated by an external call request calls the interface to be collected. The second acquisition module is used to acquire test output results collected from the application under test. The test output results are forwarded through a message middleware. The test output results are obtained by the test end testing the application under test through the interface call information. The generation module is used to generate an application test report based on the interface call information and the test output results.

15. An application testing system, characterized in that, The system includes: The data acquisition end is used to obtain the interface identifier of the application to be acquired and to determine the interface to be acquired based on the interface identifier, wherein the interface identifier includes an external call interface identifier and an internal call interface identifier; to acquire the interface call information of the interface to be acquired; and to send the interface call information to the test end so that the test end can test the application to be tested based on the interface call information; wherein the interface call information includes external interface call information and internal interface call information. Sending the interface call information to the test terminal includes: The interface call information is sent to the message middleware so that the message middleware asynchronously transmits the call information to the test end; The testing end is used to acquire interface call information collected from the application to be tested; to test the application to be tested based on the interface call information, and to obtain the test output results of the application to be tested; and to send the test output results to the server so that the server can generate an application test report based on the test output results and the interface call information. Sending the test output results to the server includes: The test output results are sent to the message middleware, so that the message middleware asynchronously transmits the test output results to the server. The server-side is used to acquire interface call information collected from the application to be tested. This interface call information is forwarded via a message middleware. The interface call information includes external interface call information and internal interface call information. The server-side also acquires test output results collected from the application to be tested. These test output results are forwarded via the message middleware. Finally, the server-side generates an application test report based on the interface call information and the test output results. The test output results are obtained by the testing end testing the application to be tested using the interface call information. The process of collecting the interface call information of the interface to be collected includes: When an external call request invokes the interface to be collected, the external call information generated is collected. Obtain the internal call request generated by the external call request; Collect all internal call information generated when the internal call request generated by the external call request calls the interface to be collected. The step of testing the application under test based on the interface call information and obtaining the test output results of the application under test includes: Obtain the interface call request from the interface call information, wherein the interface call request includes internal interface call request and external interface call request; Send the interface call request to the application under test and obtain the test output results generated by the application under test.

16. An electronic device, characterized in that, include: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the method as described in any one of claims 1 to 11.

17. A computer-readable storage medium, characterized in that, When the instructions in the computer-readable storage medium are executed by the processor of the electronic device, the electronic device is enabled to perform the method as described in any one of claims 1 to 11.

Images