Mobile internet product client test system and client test method

Abstract

The invention discloses a mobile internet product client test system and a client test method, and relates to the field of software testing, the mobile internet product client test system comprises a test mobile release module, a test mobile gateway and a simulation message generator, a joint debugging test environment is completely isolated from a local development environment of a client through a mobile publishing mechanism of a test mobile gateway and a test mobile publishing module, and the test mobile gateway and a simulation message generator are used for simulating the process that the client calls a background service to return a message. And the client can realize local testing without depending on an interface provided by a background, so that the testing efficiency is effectively improved.

Description

Technical Field

[0001] The present application relates to the field of software testing technology, and in particular to a mobile Internet product client testing system and client testing method. Background Art

[0002] As the number of online banking services continues to increase, banks need to meet increasingly complex customer business scenarios. In order to improve the security of business processing, the design of security mechanisms such as business verification logic in the backend system of online banking products is becoming more and more complex. In addition, in order to adapt to more diverse user habits, the user interaction design of online product client pages is also more refined. Therefore, there are significant differences in the focus of backend system development and client development.

[0003] However, due to the basic security requirement of zero trust in messages sent by the client and to prevent the leakage of business verification logic, security mechanisms such as business verification logic are generally implemented in the background. The client often only performs the most basic verification, resulting in a serious lack of client test data during the development phase. It also takes a long time to call the background interface, resulting in low testing efficiency. Summary of the invention

[0004] In view of the above problems, this application provides a mobile Internet product client testing system and client testing method, which can realize local testing without relying on the interface provided by the backend, effectively improving the testing efficiency. The specific solution is as follows:

[0005] The first aspect of the present application provides a mobile Internet product client test system, including: a test mobile publishing module, a test mobile gateway and a simulation message generator;

[0006] The test mobile publishing module is used to store a local test offline package, which includes a target product page resource to be tested and is used to call a simulation message generator to perform local testing;

[0007] The client downloads the local test offline package from the test mobile publishing module, and runs the local test offline package to send a simulated interface call request to the test mobile gateway;

[0008] The test mobile gateway comprises a first interface corresponding to the target product page for requesting the simulation message generator, and in response to the simulation interface call request, the test mobile gateway calls the simulation message generator through the first interface;

[0009] The simulation message generator is used to generate a simulation message in response to the calling request of the test mobile gateway, and feed it back to the client through the test mobile gateway.

[0010] In a possible implementation, the test mobile publishing module is further used to store a joint debugging offline package, where the joint debugging offline package includes a target product page resource to be tested and is used to call a background service to perform a joint debugging test;

[0011] The client downloads the joint debugging offline package from the test mobile publishing module, and runs the joint debugging offline package to send a background interface call request to the test mobile gateway;

[0012] The test mobile gateway includes a second interface corresponding to the target product page for requesting the background service, and in response to the background interface call request, the test mobile gateway calls the background service through the second interface;

[0013] The background service generates a corresponding message in response to the calling request of the test mobile gateway, and feeds back the message to the client through the test mobile gateway.

[0014] In a possible implementation, the mobile Internet product client testing system further includes:

[0015] The offline package generation module is used to generate the local test offline package and the joint debugging offline package corresponding to the target product page to be tested, and publish the local test offline package and the joint debugging offline package to the test mobile publishing module.

[0016] In a possible implementation, the offline packet generation module is further used to send an interface creation request to the test mobile gateway;

[0017] The test mobile gateway is further configured to create the first interface and / or the second interface in response to the interface creation request.

[0018] In a possible implementation, the mobile Internet product client testing system further includes:

[0019] A simulation message management terminal, used for configuring the simulation message corresponding to the simulation interface, generating an interface document, and sending the interface document to the simulation message generator;

[0020] The simulation message generator is used to determine the simulation interface corresponding to the call request of the test mobile gateway, parse the interface document corresponding to the simulation interface, and generate the simulation message.

[0021] In a possible implementation, the mobile Internet product client testing system further includes:

[0022] A synchronization module is used to periodically check the interface configuration of the target product page to be tested in the test mobile gateway. For the target product page, if the test mobile gateway includes an interface for calling the background service but does not include an interface for calling the simulation message generator, an interface for calling the simulation message generator is created in the test mobile gateway.

[0023] In a possible implementation, the synchronization module is further used to configure the message fed back by the background service as the simulated message fed back by the simulated message generator.

[0024] In a possible implementation, the mobile Internet product client test system further includes a simulation message management terminal;

[0025] The synchronization module is further used to send the field information in the message fed back by the background service to the simulation message management terminal;

[0026] The simulation message management terminal is used to generate an interface document according to the field information in the message fed back by the background service sent by the synchronization module, and send the interface document to the simulation message generator;

[0027] The simulation message generator is used to determine the simulation interface corresponding to the call request of the test mobile gateway, parse the interface document corresponding to the simulation interface, and generate the simulation message.

[0028] A second aspect of the present application provides a client testing method, comprising:

[0029] The client downloads a local test offline package from the test mobile publishing module, and runs the local test offline package to send a simulation interface call request to the test mobile gateway. The local test offline package includes the target product page resource to be tested and is used to call the simulation message generator for local testing.

[0030] The test mobile gateway calls the simulation message generator through the first interface in response to the simulation interface calling request;

[0031] The simulation message generator generates a simulation message in response to the calling request of the test mobile gateway, and feeds back the simulation message to the client through the test mobile gateway.

[0032] In a possible implementation, the client testing method further includes:

[0033] The client downloads the joint debugging offline package from the test mobile publishing module, and runs the joint debugging offline package to send a background interface call request to the test mobile gateway;

[0034] The test mobile gateway responds to the background interface calling request and calls the background service through the second interface;

[0035] The background service generates a corresponding message in response to the calling request of the test mobile gateway, and feeds back the message to the client through the test mobile gateway.

[0036] With the help of the above technical scheme, a mobile Internet product client testing system provided by the present application includes: a test mobile publishing module, a test mobile gateway and a simulation message generator. The joint debugging test environment is completely isolated from the local development environment of the client through the mobile publishing mechanism of the test mobile gateway and the test mobile publishing module. The test mobile gateway and the simulation message generator are used to simulate the process of the client calling the background service to return the message. The client can realize local testing without relying on the interface provided by the background, which effectively improves the testing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale.

[0038] Figure 1 A schematic diagram comparing the client and backend development work provided for this application;

[0039] Figure 2 A schematic diagram of a client code local debugging solution provided for this application;

[0040] Figure 3 A mobile Internet product client test system architecture diagram provided in an embodiment of the present application;

[0041] Figure 4 Another mobile Internet product client test system architecture diagram provided in an embodiment of the present application;

[0042] Figure 5 Another mobile Internet product client test system architecture diagram provided in an embodiment of the present application;

[0043] Figure 6 A schematic diagram of multi-branch code debugging for a simulated message management terminal provided in an embodiment of the present application;

[0044] Figure 7 Another mobile Internet product client test system architecture diagram provided in an embodiment of the present application;

[0045] Figure 8 A schematic diagram of a client testing method provided in an embodiment of the present application;

[0046] Fig. 9 A flowchart of another client testing method provided in an embodiment of the present application;

[0047] Fig.10 A schematic diagram of a client testing method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0048] In the following explanation, in order to ensure the accuracy of the citation and the fluency of reading, the key technical terms involved in the article are summarized and explained as follows:

[0049] Client: The user-facing part of an Internet application, including the user interface (UI) and user interaction logic (UE). User operations request the server through the interface, and the request results are displayed to the user.

[0050] Backend: The part of an Internet application that is responsible for specific business logic. This part provides a request interface for the client, performs corresponding business logic after receiving the request, and returns the processing results to the client.

[0051] Interface: The interaction method agreed upon by the backend client, including the request address (URL), request method, message format, and the meaning of the return result fields.

[0052] Mobile Gateway: A network request middle layer between the client and the backend, used to isolate the backend from the Internet environment. The client cannot directly request the backend, and is only allowed to request the pre-configured backend interface through the mobile gateway.

[0053] The following describes the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. The terms used in the implementation method section of the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application.

[0054] The embodiments of the present application are described below in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0055] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and need not be used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, which is only to describe the distinction mode adopted by the objects of the same attributes when describing in the embodiments of the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0056] like Figure 1 As shown in the figure, there are significant differences in the focus of backend system development and client development. Client development focuses more on user interaction design, while backend development focuses more on the design of security mechanisms such as business verification logic. Due to the basic security requirement of zero trust in messages sent by the client and to prevent the leakage of business verification logic, security mechanisms such as business verification logic are generally implemented in the background. The client often only performs the most basic verification, resulting in a serious lack of client test data during the development stage, and it will take a long time to call the backend interface, resulting in low test efficiency.

[0057] At present, the common client code local testing solution is implemented by directly modifying the code. Figure 2 As shown in the figure, when the client developer debugs the code of the product page project locally, he will replace the real interface of the request server with the simulated interface of the request server in the code. The server developer will intercept the return message of the real interface and directly return the simulated message to the client in the simulated interface. In this way, the client code can be debugged without requesting the backend.

[0058] However, this client code local testing solution requires modifying the client and server code, which is highly invasive and increases the complexity of code version management. It also increases the production risk caused by introducing a simulated message control mechanism.

[0059] In order to solve the above problems, the embodiment of the present application provides a mobile Internet product client testing system. The mobile Internet product client testing system of the embodiment of the present application is described in detail below with reference to the accompanying drawings.

[0060] See also Figure 3 , Figure 4 A mobile Internet product client test system architecture diagram provided in an embodiment of the present application, such as Figure 4 As shown, a mobile Internet product client test system provided in an embodiment of the present application includes a test mobile publishing module 301, a test mobile gateway 302 and a simulation message generator 303.

[0061] The test mobile publishing module 301, the test mobile gateway 302 and the simulation message generator 303 may be deployed on the same server or on different servers.

[0062] The test mobile publishing module 301 is used to store local test offline packages. The number of local test offline packages can be one or more. Each local test offline package corresponds to a target product page to be tested. The local test offline package includes the target product page resources to be tested. The target product page resources include HTML, CSS, JavaScript, pictures, API interface files, etc., wherein the API interface file includes the interface configuration data used to call the simulation message generator in the test mobile gateway.

[0063] When performing local client testing, the client downloads the local test offline package from the test mobile publishing module 301, runs the local test offline package after unpacking, displays the target product page to be tested, and sends a simulated interface call request to the test mobile gateway 302 when the interface call function is triggered.

[0064] The test mobile gateway 302 includes a first interface corresponding to the target product page for requesting the simulation message generator 303, and in response to the above simulation interface call request sent by the client, calls the simulation message generator 303 through the first interface.

[0065] The simulation message generator 303 is used to generate a simulation message in response to the call request of the test mobile gateway 302, and feed it back to the client through the test mobile gateway 302 to complete the client local test.

[0066] Specifically, the call request sent by the test mobile gateway 302 carries an interface identifier (interface name or interface identifier, etc.), a request type (GET, POST, etc.), etc. The simulation message generator 303 parses the call request to determine the target interface called by the test mobile gateway 302, and then generates a corresponding simulation message according to the interface document corresponding to the pre-configured target interface, and feeds it back to the client through the test mobile gateway 302.

[0067] It can be seen that the mobile Internet product client test system disclosed in this embodiment completely isolates the joint debugging test environment from the local development environment of the client through the mobile publishing mechanism of the test mobile gateway and the test mobile publishing module, and uses the test mobile gateway and the simulation message generator to simulate the process of the client calling the background service to return the message. The client can also implement local testing without relying on the interface provided by the background, which effectively improves the test efficiency. Compared with the traditional message simulation technology that directly modifies the code, this embodiment does not need to configure the simulation message in the code, which greatly reduces the code intrusiveness on both the client and the server, improves the code maintainability, reduces the complexity of code version management, and effectively avoids the production risks caused by the simulation message.

[0068] in addition Figure 2 In the client code local test solution shown, since the simulation message is implemented by modifying the code, multiple versions of the code cannot be run in the same environment without introducing a new client and server operating environment. That is, one environment can only run one set of code at the same time. Therefore, joint debugging testing and client local development cannot be performed at the same time. Among them, joint debugging testing refers to testing the data interaction between the client and the background service.

[0069] In order to solve the above technical problems, the test mobile publishing module in the mobile Internet product client testing system provided in this embodiment is also used to store the joint debugging offline package, which includes the target product page resources to be tested. Unlike the local test offline package, the joint debugging offline package is used to call the background service for joint debugging testing.

[0070] The client downloads the joint debugging offline package from the test mobile publishing module, and runs the joint debugging offline package to send a background interface call request to the test mobile gateway.

[0071] The test mobile gateway includes a second interface corresponding to the target product page for requesting a background service. In response to the background interface call request, the test mobile gateway calls the background service through the second interface.

[0072] The background service generates a corresponding message in response to the calling request of the test mobile gateway, and feeds it back to the client through the test mobile gateway.

[0073] In order to implement the above client local test and joint debugging test, Figure 4As shown in the mobile Internet product client test system architecture diagram, the mobile Internet product client test system provided in this embodiment also includes an offline package generation module 304, which is used to generate a local test offline package and a joint debugging offline package corresponding to the target product page to be tested, and publish the local test offline package and the joint debugging offline package to the test mobile publishing module 301. In other words, the same target product page to be tested can correspond to a local test offline package and a joint debugging offline package, the local test offline package is used to call the simulation message generator for local testing, and the joint debugging offline package is used to call the background service for joint debugging testing.

[0074] This embodiment provides a client code construction mechanism, in which the offline package generation module 304 identifies the network request code for requesting at least one background interface in the target product page to be tested, and automatically generates a network request code for requesting the corresponding interface of the simulation message generator for each background interface requested, and then packages the target product page resources including the network request code for requesting the corresponding interface of the simulation message generator to generate a local test offline package, and packages the target product page resources including the network request code for requesting the background interface to generate a joint debugging offline package, and finally publishes the local test offline package and the joint debugging offline package to the test mobile publishing module 301.

[0075] Based on the client code construction mechanism, the offline package generation module 304 is also used to send an interface creation request to the test mobile gateway 302. The test mobile gateway 302 is also used to create the above-mentioned first interface and / or second interface in response to the interface creation request, that is, if the offline package generation module 304 only generates a local test offline package, the test mobile gateway 302 creates the above-mentioned first interface; if the offline package generation module 304 only generates a joint debugging offline package, the test mobile gateway 302 creates the above-mentioned second interface; if the offline package generation module 304 generates a local test offline package and a joint debugging offline package, the test mobile gateway 302 creates the above-mentioned first interface and second interface, that is, configure the interface for requesting the real background interface and the interface for requesting the simulation message generator on the test mobile gateway for the target product page.

[0076] It can be seen that for each network request interface of the target product page, two will be configured in the test mobile gateway. Among them, the first interface is called by the offline package requesting the simulated interface, and the second interface is called by the offline package requesting the real background interface. In this way, the offline package requesting the simulated message can call the simulated message generator to obtain the simulated message, and the offline package requesting the real background service can call the real background service to obtain the real message, thereby achieving complete isolation between requesting the real background service and requesting the simulated message generator, and the client can request two different interfaces through the same code, so that the client does not need to adapt separately.

[0077] This embodiment achieves complete isolation of the joint debugging and testing environment from the local development environment through the mobile gateway and mobile publishing mechanism, so that the joint debugging and testing work and the local development work can be carried out in parallel without interfering with each other, effectively improving the development efficiency and shortening the product development cycle.

[0078] in addition Figure 2 In the client code local test solution shown, since the message content needs to be manually configured and the server needs to be restarted each time the message is modified, it is time-consuming to configure the simulated message, which affects the development and testing efficiency.

[0079] In order to solve the above technical problems, Figure 5 As shown in the mobile Internet product client test system architecture diagram, the mobile Internet product client test system provided in this embodiment also includes a simulation message management terminal 305, which is used to configure the simulation message corresponding to the simulation interface, generate an interface document, and send the interface document to the simulation message generator 303. After determining the simulation interface (i.e., the first interface) corresponding to the call request of the test mobile gateway 302, the simulation message generator 303 parses the interface document corresponding to the simulation interface, generates a simulation message, and publishes the simulation message to the simulation interface corresponding to the test mobile gateway 302. In this embodiment, each modification of the message does not require the server to be restarted, which effectively improves the development and testing efficiency.

[0080] In addition to manually writing a simulated message for a specific interface at the simulated message management terminal 305, the user can also configure different status values ​​of common fields and corresponding fields, such as Figure 6 As shown, for field a, the user can select different state values ​​1-n+1 to quickly configure the simulation message of the interface, effectively improving the development and testing of the multi-branch structure code. After completing the simulation message configuration, the user can publish the configuration to the simulation message generator 303 through the simulation message management terminal 306, update the simulation message of the test mobile gateway 302 request simulation message generator 303, and send the simulation message to the test mobile gateway 302. In this way, when the user accesses the local test offline package through the client next time, the test mobile gateway 302 will intercept the request and return the updated simulation message.

[0081] Further, if Figure 7 As shown in the architecture diagram of the mobile Internet product client test system, the mobile Internet product client test system provided by the embodiment of the present application also includes a synchronization module 306, which is used to regularly check the interface configuration of the target page to be tested in the test mobile gateway 302. For the target product page, if the test mobile gateway 302 includes an interface for calling the background service and does not include an interface for calling the simulation message generator 303, then an interface for calling the simulation message generator 303 is created in the test mobile gateway 302.

[0082] Furthermore, the synchronization module 306 is further used to configure the message fed back by the background service as the simulated message fed back by the simulated message generator 303, that is, to achieve message information synchronization.

[0083] Furthermore, the synchronization module 306 is also used to send the field information in the message fed back by the background service to the simulation message management terminal 305. The simulation message management terminal 305 generates an interface document based on the field information in the message fed back by the background service sent by the synchronization module 306, and sends the interface document to the simulation message generator 303, so that the simulation message generator 303 determines the simulation interface corresponding to the call request of the test mobile gateway, parses the interface document corresponding to the simulation interface, generates the simulation message, and realizes field information synchronization.

[0084] The mobile Internet product client test system provided in this embodiment automatically configures the simulation message interface in the test mobile gateway through the background message synchronization mechanism, and can directly modify the fields to common configuration values ​​through the simulation message management terminal, effectively reducing the configuration time of the simulation message.

[0085] The present application also provides a client testing method, such as Figure 8 As shown, a client testing method provided in an embodiment of the present application may include the following steps 801-803:

[0086] 801: the client downloads a local test offline package from the test mobile publishing module, and runs the local test offline package to send a simulated interface call request to the test mobile gateway;

[0087] The local test offline package includes the target product page resources to be tested, which is used to call the simulation message generator for local testing;

[0088] 802: the test mobile gateway calls the simulation message generator through the first interface in response to the simulation interface call request;

[0089] 803: The simulation message generator generates a simulation message in response to the calling request of the test mobile gateway, and feeds it back to the client through the test mobile gateway.

[0090] In one possible implementation, Fig. 9 As shown, a client testing method provided in an embodiment of the present application also includes the following steps 901-903:

[0091] 901: the client downloads the joint debugging offline package from the test mobile publishing module, runs the joint debugging offline package and sends a background interface call request to the test mobile gateway;

[0092] 902: the test mobile gateway responds to the background interface calling request and calls the background service through the second interface;

[0093] 903: The background service generates a corresponding message in response to the calling request of the test mobile gateway, and feeds it back to the client through the test mobile gateway.

[0094] Further, if Fig.10 In the client testing method shown, the client generates an offline package by using a build script. Specifically, the build script identifies the network request code of each background interface requested in the target product page to be tested, and automatically generates a network request code for each background interface requested for a corresponding interface of the simulation message generator. The target product page resources including the network request code for requesting the corresponding interface of the simulation message generator are then packaged to generate a local test offline package, the target product page resources including the network request code for requesting the background interface are packaged to generate a joint debugging offline package, and the local test offline package and the joint debugging offline package are then published to the test mobile publishing module.

[0095] At the same time, the build script configures two network request interfaces for each target product page in the test mobile gateway. The first interface is called by the offline package requesting the simulated interface, and the second interface is called by the offline package requesting the real background interface, such as Fig.10 The test mobile gateway shown includes an interface 1 for requesting background services and an interface 1 for requesting a simulation message generator, an interface 2 for requesting background services and an interface 2 for requesting a simulation message generator, and so on.

[0096] When conducting local client testing, the client downloads the local test offline package from the test mobile publishing module, runs the local test offline package to display the target product page to be tested, and sends a simulated interface call request to the test mobile gateway when the interface call function is triggered. The test mobile gateway responds to the simulated interface call request sent by the client, calls the simulated message generator through the corresponding interface, and the simulated message generator parses the call request to determine the interface called by the test mobile gateway, and then generates a simulated message according to the pre-configured corresponding interface document, and feeds it back to the client through the test mobile gateway. Among them, the interface document can be manually configured by the user at the simulated message management end, or it can be a real message generated by the background service synchronized through the message information synchronization mechanism, and it can also be an interface document automatically generated by the simulated message management end according to the synchronized field information by synchronizing the field information in the real message generated by the background service to the simulated message management end through the field information synchronization mechanism.

[0097] When conducting joint debugging tests, the client downloads the joint debugging offline package from the test mobile publishing module, runs the joint debugging offline package to display the target product page to be tested, and sends a background interface call request to the test mobile gateway when the interface call function is triggered. The test mobile gateway responds to the background interface call request sent by the client, calls the background service through the corresponding interface, and the background service generates a corresponding real message in response to the call request of the test mobile gateway, and feeds it back to the client through the test mobile gateway.

[0098] It should also be noted that the device embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed over multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, in the drawings of the device embodiments provided by the present application, the connection relationship between the modules indicates that there is a communication connection between them, which may be specifically implemented as one or more communication buses or signal lines.

[0099] Through the description of the above implementation mode, the technicians in the field can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course, it can also be implemented by special hardware including special integrated circuits, special CPUs, special memories, special components, etc. In general, all functions completed by computer programs can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be various, such as analog circuits, digital circuits or special circuits. However, for the present application, software program implementation is a better implementation mode in more cases. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer floppy disk, a U disk, a mobile hard disk, a ROM, a RAM, a disk or an optical disk, etc., including a number of instructions to enable a computer device (which can be a personal computer, a training device, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0100] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0101] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, a computer, a training device, or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, training device, or data center. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a training device, a data center, etc. that includes one or more available media integrations. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)), etc.

Claims

1. A mobile Internet product client testing system, characterized in that: include: Test mobile publishing module, test mobile gateway and simulated message generator; The test mobile publishing module is used to store a local test offline package, which includes a target product page resource to be tested and is used to call a simulation message generator to perform local testing; The client downloads the local test offline package from the test mobile publishing module, and runs the local test offline package to send a simulated interface call request to the test mobile gateway; The test mobile gateway comprises a first interface corresponding to the target product page for requesting the simulation message generator, and in response to the simulation interface call request, the test mobile gateway calls the simulation message generator through the first interface; The simulation message generator is used to generate a simulation message in response to the calling request of the test mobile gateway, and feed it back to the client through the test mobile gateway.

2. The mobile Internet product client testing system according to claim 1, characterized in that: The test mobile publishing module is also used to store a joint debugging offline package, which includes a target product page resource to be tested and is used to call a backend service to perform a joint debugging test; The client downloads the joint debugging offline package from the test mobile publishing module, and runs the joint debugging offline package to send a background interface call request to the test mobile gateway; The test mobile gateway includes a second interface corresponding to the target product page for requesting the background service, and in response to the background interface call request, the test mobile gateway calls the background service through the second interface; The background service generates a corresponding message in response to the calling request of the test mobile gateway, and feeds back the message to the client through the test mobile gateway.

3. The mobile Internet product client testing system according to claim 2, characterized in that: The mobile Internet product client testing system also includes: The offline package generation module is used to generate the local test offline package and the joint debugging offline package corresponding to the target product page to be tested, and publish the local test offline package and the joint debugging offline package to the test mobile publishing module.

4. The mobile Internet product client testing system according to claim 3, characterized in that: The offline package generation module is further used to send an interface creation request to the test mobile gateway; The test mobile gateway is further configured to create the first interface and / or the second interface in response to the interface creation request.

5. The mobile Internet product client testing system according to claim 1, characterized in that: The mobile Internet product client testing system also includes: A simulation message management terminal, used for configuring the simulation message corresponding to the simulation interface, generating an interface document, and sending the interface document to the simulation message generator; The simulation message generator is used to determine the simulation interface corresponding to the call request of the test mobile gateway, parse the interface document corresponding to the simulation interface, and generate the simulation message.

6. The mobile Internet product client testing system according to claim 2, characterized in that: The mobile Internet product client testing system also includes: A synchronization module is used to periodically check the interface configuration of the target product page to be tested in the test mobile gateway. For the target product page, if the test mobile gateway includes an interface for calling the background service but does not include an interface for calling the simulation message generator, an interface for calling the simulation message generator is created in the test mobile gateway.

7. The mobile Internet product client testing system according to claim 6, characterized in that: The synchronization module is further used to configure the message fed back by the background service as the simulated message fed back by the simulated message generator.

8. The mobile Internet product client testing system according to claim 6, characterized in that: The mobile Internet product client testing system also includes a simulated message management terminal; The synchronization module is further used to send the field information in the message fed back by the background service to the simulation message management terminal; The simulation message management terminal is used to generate an interface document according to the field information in the message fed back by the background service sent by the synchronization module, and send the interface document to the simulation message generator; The simulation message generator is used to determine the simulation interface corresponding to the call request of the test mobile gateway, parse the interface document corresponding to the simulation interface, and generate the simulation message.

9. A client testing method, characterized in that: include: The client downloads a local test offline package from the test mobile publishing module, and runs the local test offline package to send a simulation interface call request to the test mobile gateway. The local test offline package includes the target product page resource to be tested and is used to call the simulation message generator for local testing. The test mobile gateway calls the simulation message generator through the first interface in response to the simulation interface calling request; The simulation message generator generates a simulation message in response to the calling request of the test mobile gateway, and feeds back the simulation message to the client through the test mobile gateway.

10. The client testing method according to claim 9, characterized in that: The client testing method further includes: The client downloads the joint debugging offline package from the test mobile publishing module, and runs the joint debugging offline package to send a background interface call request to the test mobile gateway; The test mobile gateway responds to the background interface calling request and calls the background service through the second interface; The background service generates a corresponding message in response to the calling request of the test mobile gateway, and feeds back the message to the client through the test mobile gateway.

Images