A mobile internet product client testing system and a client testing method

Abstract

The application discloses a mobile internet product client test system and a client test method, relates to the field of software testing, and discloses a mobile internet product client test system, which comprises a test mobile publishing module, a test mobile gateway and a simulated message generator. The test mobile gateway and the test mobile publishing module are used to completely isolate the joint debugging test environment from the local development environment of the client through a mobile publishing mechanism, the test mobile gateway and the simulated message generator are used to simulate the process of returning messages by the client after calling a background service, the client can realize local test without depending on the interface provided by the background, and the test efficiency is effectively improved.

Description

TECHNICAL FIELD

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

[0002] With the increasing number of online banking businesses, banks need to meet more and more complex customer business scenarios. In order to improve the security of business processing, the security mechanism design of the business verification logic of the online product background system is becoming more and more complex. In addition, the online product client page is designed to adapt to more user habits, and the user interaction design is more refined. Therefore, the development of the background system and the development of the client have great differences in emphasis.

[0003] However, due to the basic security requirement of zero trust on the client side and the prevention of business verification logic leakage, the security mechanism such as business verification logic is generally implemented in the background, and the client often only does the most basic verification, resulting in a serious lack of client test data in the development stage, and a long time is needed to call the background interface, which is low in test efficiency. SUMMARY

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

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

[0006] The test mobile publishing module is used for storing a local test offline package, the local test offline package includes a target product page resource to be tested, and is used for calling the simulated message generator for 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 includes a first interface corresponding to the target product page and used for requesting the simulated message generator, and in response to the simulated interface call request, the test mobile gateway calls the simulated message generator through the first interface;

[0009] The simulated message generator is used for generating a simulated message in response to the calling request of the test mobile gateway, and feeding back to the client through the test mobile gateway.

[0010] In a possible implementation, the test mobile publishing module is further configured to store a joint debugging offline package, the joint debugging offline package comprising target product page resources to be tested, and used to call a background service for joint debugging testing.

[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 comprises a second interface corresponding to the target product page and used to request 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 call 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 comprises:

[0015] An offline package generation module configured 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 package generation module is further configured 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 comprises:

[0019] An analog message management terminal configured to configure analog messages corresponding to the analog interface, generate interface documents, and send the interface documents to the analog message generator.

[0020] The analog message generator is configured to determine the analog interface corresponding to the call request of the test mobile gateway, parse the interface documents corresponding to the analog interface, and generate the analog message.

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

[0022] The synchronization module is configured to periodically check an interface configuration of a target product page to be tested on the test mobile gateway, and create an interface for calling the simulation message generator on the test mobile gateway 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.

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

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

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

[0026] The simulation message management terminal is configured 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 configured to determine the simulation interface corresponding to the calling request of the test mobile gateway, parse the interface document corresponding to the simulation interface, and generate the simulation message.

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

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

[0030] The test mobile gateway responds to the simulation interface calling request and calls the simulation message generator through a first interface.

[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 a joint debugging offline package from the test mobile publishing module, and runs the joint debugging offline package to send a background interface calling request to the test mobile gateway.

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

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

[0036] By the above technical solution, the mobile internet product client test system provided by the application comprises a test mobile publishing module, a test mobile gateway and a simulated message generator. The test mobile publishing mechanism of the test mobile gateway and the test mobile publishing module completely isolates the joint debugging test environment from the local development environment of the client. The process of the client calling the background service to return a message is simulated by the test mobile gateway and the simulated message generator. The client can realize local test without relying on the interface provided by the background, and the test efficiency is effectively improved. BRIEF DESCRIPTION OF DRAWINGS

[0037] The above and other features, advantages and aspects of the present disclosure will become more apparent by thoroughly examining the following detailed description, the accompanying drawings and the appended claims taken in conjunction with the accompanying drawings. Identical or similar reference numerals are used throughout the drawings to refer to identical or similar elements. It should be understood that the drawings are schematic and elements and features are not necessarily drawn to scale.

[0038] Figure 1 A client and background development work comparison schematic diagram is provided for the application;

[0039] Figure 2 A client code local debugging scheme schematic diagram is provided for the application;

[0040] Figure 3 A mobile internet product client test system architecture diagram is provided for the embodiment of the application;

[0041] Figure 4 Another mobile internet product client test system architecture diagram is provided for the embodiment of the application;

[0042] Figure 5 Another mobile internet product client test system architecture diagram is provided for the embodiment of the application;

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

[0044] Figure 7 Another mobile internet product client test system architecture diagram is provided for the embodiment of the application;

[0045] Figure 8 A client test method flowchart is provided for the embodiment of the application;

[0046] Figure 9 Another flowchart of a client testing method provided by an embodiment of the present application is shown in FIG. 3.

[0047] Figure 10 A flowchart of a client testing method provided by an embodiment of the present application is shown in FIG. 2. DETAILED DESCRIPTION

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

[0049] Client: The part of an Internet application that faces users, including the user interface (UI) and user interaction logic (UE). User operations will request the server through the interface, and the request result will be displayed to the user.

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

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

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

[0053] The embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application. The terms used in the implementation part 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 drawings. Those skilled in the art can know that as technology develops and new scenarios appear, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0055] The terms "first", "second", and the like in the description and in the claims of the present application and above-described drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or sequence. It should be understood that the terms so used are interchangeable under appropriate circumstances and are merely employed to distinguish one object from another. Furthermore, the terms "comprise", "comprising", "have", "having", "include", "including", "contain", "containing", and any variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, system, product, or apparatus that comprises a list of elements is not necessarily limited to those elements, but can include other elements not expressly listed or inherent to such process, method, system, product, or apparatus.

[0056] As shown in Figure 1 , there is a big difference between the background system development and the client development, and the client development work pays more attention to user interaction design, and the background development work pays more attention to the design of business verification logic and other security mechanisms. In order to meet the basic security requirements of zero trust of the client's upper message, and to prevent the leakage of business verification logic and other security mechanisms, the business verification logic and other security mechanisms are generally implemented in the background, and the client often only does the most basic verification, which leads to a serious lack of client test data in the development stage, and it will take a long time to call the background interface, and the test efficiency is low.

[0057] The current general client code local test scheme is realized by directly modifying the code. As shown in Figure 2 , when the client developer debugs the code of the product page project locally, the client developer will replace the real interface for requesting the server with a simulated interface for requesting the server in the code. The server developer will intercept the return message of the real interface, and directly return a simulated message to the client in the simulated interface. In this way, the client code can be debugged without requesting the background.

[0058] However, this client code local test scheme needs to modify the client and server code, which has high code invasiveness, increases the complexity of code version management, and also increases the production risk caused by introducing the simulated message control mechanism.

[0059] In order to solve the above problems, the embodiment of the present application provides a mobile Internet product client test system. The mobile Internet product client test system of the embodiment of the present application will be described in detail below in combination with the drawings.

[0060] Please refer to Figure 3 , Figure 4 The mobile Internet product client test system architecture provided by the embodiment of the present application is shown in Figure 4 , the mobile Internet product client test system provided by the embodiment of the present application includes a test mobile publishing module 301, a test mobile gateway 302, and a simulated message generator 303.

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

[0062] The test mobile publishing module 301 is configured 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 target product page resources to be tested, which include HTML, CSS, JavaScript, pictures, API interface files, and the like. The API interface file includes interface configuration data for calling the simulation message generator in the test mobile gateway.

[0063] During client-side local testing, the client downloads a local test offline package from the test mobile publishing module 301, unpacks and runs the local test offline package, displays the target product page to be tested, and sends a simulation 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. In response to the simulation interface call request sent by the client, the test mobile gateway 302 calls the simulation message generator 303 through the first interface.

[0065] The simulation message generator 303 is configured to generate a simulation message in response to a call request from the test mobile gateway 302 and feed back to the client through the test mobile gateway 302, thereby completing the client-side local testing.

[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.), and the like. The simulation message generator 303 analyzes 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 pre-configured interface document corresponding to the target interface and feeds 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 the embodiment completely isolates the joint debugging test environment from the local development environment of the client by testing the mobile gateway and the mobile publishing mechanism of the test mobile publishing module, and simulates the process of returning a message by the client after calling a background service by using the test mobile gateway and the simulated message generator. The client can realize local testing without relying on the interface provided by the background, and the test efficiency is effectively improved. Compared with the traditional message simulation technology by directly modifying the code, the embodiment does not need to configure the simulated message in the code, so that the code invasiveness is greatly reduced on the client and the server, the code maintainability is improved, the complexity of code version management is reduced, and the production risk caused by the simulated message is effectively avoided.

[0068] In addition Figure 2 In the client code local test scheme shown, since the simulated message is realized by modifying the code, multiple versions of the code cannot be run in the same environment without introducing new client and server running environments, that is, only one set of code can be run in one set of environment, and therefore the joint debugging test and the client local development cannot be simultaneously performed. The joint debugging test refers to testing the data interaction between the client and the background service.

[0069] To solve the above technical problems, the test mobile publishing module in the mobile internet product client test system provided by the embodiment is further used to store a joint debugging offline package. The joint debugging offline package includes target product page resources to be tested. Different from the local test offline package, the joint debugging offline package is used to call the background service for joint debugging test.

[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 calling request to the test mobile gateway.

[0071] The test mobile gateway includes a second interface corresponding to the target product page and used to request the background service. In response to the background interface calling 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 back the message to the client through the test mobile gateway.

[0073] To realize the above client local test and joint debugging test, like Figure 4The mobile Internet product client test system architecture diagram shown, the mobile Internet product client test system provided by the embodiment further includes an offline package generation module 304 configured to generate a local test offline package and a joint debugging offline package corresponding to a 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. That is, the local test offline package and the joint debugging offline package can correspond to the same target product page to be tested. The local test offline package is used to call the simulated message generator for local testing, and the joint debugging offline package is used to call the background service for joint debugging testing.

[0074] The embodiment provides a client code construction mechanism. The offline package generation module 304 identifies a network request code for requesting at least one background interface in the target product page to be tested, and automatically generates a piece of network request code for requesting an interface of the simulated message generator for each network request code for requesting the background interface. Then, the offline package generation module 304 packs target product page resources including the network request code for requesting the interface of the simulated message generator to generate a local test offline package, and packs target product page resources including the network request code for requesting the background interface to generate a joint debugging offline package. Finally, the offline package generation module 304 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 further configured to send an interface creation request to the test mobile gateway 302. The test mobile gateway 302 is further configured to create the first interface and / or the second interface in response to the interface creation request. That is, if the offline package generation module 304 generates only the local test offline package, the test mobile gateway 302 creates the first interface; if the offline package generation module 304 generates only the joint debugging offline package, the test mobile gateway 302 creates the second interface; and if the offline package generation module 304 generates both the local test offline package and the joint debugging offline package, the test mobile gateway 302 creates both the first interface and the second interface, that is, the target product page is configured to request the real background interface and the interface of the simulated message generator on the test mobile gateway.

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

[0077] This embodiment achieves complete isolation between the joint debugging and testing environment and the local development environment through a mobile gateway and a mobile publishing mechanism. This allows joint debugging and testing to proceed in parallel without interfering with local development, effectively improving development efficiency and shortening the product development cycle.

[0078] in addition Figure 2 In the local testing scheme of the client code shown, the message content needs to be manually configured, and the server needs to be restarted every time the message is modified. Therefore, configuring the simulated message is time-consuming and affects the efficiency of development and testing.

[0079] To solve the above technical problems, such as Figure 5 The mobile internet product client testing system architecture diagram shown in this embodiment further includes a simulated message management terminal 305, used to configure simulated messages corresponding to simulated interfaces, generate interface documents, and send the interface documents to a simulated message generator 303. After determining the simulated interface (i.e., the aforementioned first interface) corresponding to the call request of the test mobile gateway 302, the simulated message generator 303 generates simulated messages by parsing the interface documents corresponding to the simulated interface and publishes the simulated messages to the simulated interface corresponding to the test mobile gateway 302. In this embodiment, each modification to the message does not require restarting the server, effectively improving development and testing efficiency.

[0080] In addition to manually writing simulated messages for specific interfaces in the simulated message management terminal 305, users can also configure commonly used fields and different status values ​​for corresponding fields, such as... Figure 6 As shown, for field 'a', users can select different status values ​​1-n+1 to quickly configure the simulated message of the interface, effectively improving the development and testing of multi-branch structure code. After completing the simulated message configuration, the user can publish this configuration to the simulated message generator 303 through the simulated message management terminal 305, update the simulated message requested by the test mobile gateway 302 from the simulated message generator 303, and send the simulated message to the test mobile gateway 302. Thus, when the user accesses the local test offline package again through the client, the test mobile gateway 302 will intercept the request and return the updated simulated message.

[0081] Furthermore, such as Figure 7 The mobile internet product client testing system architecture diagram shown in this application embodiment further includes a synchronization module 306, which is used to periodically check the interface configuration of the target page to be tested on the test mobile gateway 302. For the target product page, if the test mobile gateway 302 includes an interface for calling the background service but does not include an interface for calling the simulated message generator 303, then an interface for calling the simulated message generator 303 is created on the test mobile gateway 302.

[0082] Further, the synchronization module 306 is further configured to configure the message fed back by the background service as the simulation message fed back by the simulation message generator 303, that is, to realize synchronization of message information.

[0083] Further, the synchronization module 306 is further configured to send field information in the message fed back by the background service to the simulation message management terminal 305, and the simulation message management terminal 305 generates an interface document according to 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 a simulation interface corresponding to the calling request of the test mobile gateway, parses the interface document corresponding to the simulation interface, generates the simulation message, and realizes synchronization of field information.

[0084] The mobile Internet product client test system provided in the embodiment can automatically configure the simulation message interface in the test mobile gateway through a background message synchronization mechanism, and can directly modify the field to a commonly used configuration value through the simulation message management terminal, thereby effectively reducing the configuration time of the simulation message.

[0085] The embodiment of the application further provides a client test method, as shown in Figure 8 The client test method provided in the embodiment of the application can include the following steps 801-803.

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

[0087] The local test offline package includes a target product page resource to be tested, and is used to call a simulation message generator for local testing.

[0088] 802: The test mobile gateway responds to the simulation interface calling request, and calls the simulation message generator through a first interface;

[0089] 803: 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.

[0090] In a possible implementation, as shown in Figure 9 The client test method provided in the embodiment of the application further includes the following steps 901-903.

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

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

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

[0094] Further, as shown in the client testing method, the client generates an offline package by using the 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 piece of network request code for requesting the corresponding interface of the simulation message generator for each background interface requested, and then packs 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, packs the target product page resources including the network request code for requesting the background interface to generate a joint debugging offline package, and then publishes the local test offline package and the joint debugging offline package to the test mobile publishing module. Figure 10

[0095] Meanwhile, the build script will configure two interfaces for each network request interface of the target product page, wherein the first interface is called by the offline package of the simulation interface, and the second interface is called by the offline package of the real background interface, as shown in the test mobile gateway including interface 1 for requesting the background service and interface 1 for requesting the simulation message generator, interface 2 for requesting the background service and interface 2 for requesting the simulation message generator, and so on. Figure 10

[0096] When performing client local 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 simulation interface calling request to the test mobile gateway when the interface calling function is triggered. The test mobile gateway responds to the simulation interface calling request sent by the client, calls the simulation message generator through the corresponding interface, the simulation message generator analyzes the calling request to determine the interface called by the test mobile gateway, and then generates a simulation message according to the pre-configured interface document, and feeds back to the client through the test mobile gateway. The interface document can be manually configured by the user in the simulation message management terminal, can be a real message generated by the background service through the message information synchronization mechanism, or can be an interface document automatically generated by the simulation message management terminal according to the field information synchronized from the real message generated by the background service through the field information synchronization mechanism.

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

[0098] In addition, it should be noted that the apparatus embodiments described above are merely illustrative, wherein the units described as separate components can or can not be physically separated, and the components displayed as units can or can not be physical units, i.e., can be located in one place, or can be distributed on multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the embodiment. In addition, in the apparatus embodiment provided in the present application, the connection relationship between the modules indicates that there is a communication connection between them, which can be implemented as one or more communication buses or signal lines.

[0099] Through the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software and 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. Generally, functions completed by computer programs can be easily implemented by corresponding hardware, and the specific hardware structure for implementing 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 embodiment. Based on this understanding, the technical solutions of the present application can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer's floppy disk, U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk, etc., including a plurality of instructions to make a computer device (which can be a personal computer, training device, or network device, etc.) execute the methods described in various embodiments of the present application.

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

[0101] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can 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 can be transmitted from one website, computer, training device or data center to another website, computer, training device or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be stored by the computer or a data storage device such as a training device, a data center, etc. integrated with one or more available media sets. The available media can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)), etc.

Claims

1. A mobile Internet product client test system, characterized in that, The mobile Internet product client test system comprises: a test mobile publishing module, a test mobile gateway and a simulation message generator; the test mobile publishing module is configured to store a local test offline package, the local test offline package comprising target product page resources to be tested, and to call the simulation message generator for local testing; a client downloads the 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 test mobile gateway comprises a first interface corresponding to the target product page and configured to request the simulation message generator, and the test mobile gateway calls the simulation message generator through the first interface in response to the simulation interface call request; the simulation message generator is configured to generate a simulation message in response to the call request of the test mobile gateway and feed back the simulation message to the client through the test mobile gateway; the test mobile publishing module is further configured to store a joint debugging offline package, the joint debugging offline package comprising target product page resources to be tested, and to call a background service for joint debugging testing; 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 comprises a second interface corresponding to the target product page and configured to request the background service, and the test mobile gateway calls the background service through the second interface in response to the background interface call request; the background service generates a corresponding message in response to the call request of the test mobile gateway and feeds back the corresponding message to the client through the test mobile gateway; the mobile Internet product client test system further comprises: a synchronization module configured to periodically check interface configurations of target product pages to be tested on the test mobile gateway, and create an interface for calling the simulation message generator on the test mobile gateway for a target product page if the test mobile gateway comprises an interface for calling the background service but does not comprise an interface for calling the simulation message generator.

2. The mobile Internet product client test system of claim 1, wherein, the mobile Internet product client test system further comprises: an offline package generation module configured to generate the local test offline package and the joint debugging offline package corresponding to target product pages to be tested, and publish the local test offline package and the joint debugging offline package to the test mobile publishing module.

3. The mobile Internet product client test system of claim 2, wherein, the offline package generation module is further configured 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.

4. The mobile Internet product client test system of claim 1, wherein, the mobile Internet product client test system further comprises: a simulation message management terminal configured to configure simulation messages corresponding to the simulation interface, generate interface documents, and send the interface documents to the simulation message generator; the simulation message generator is configured to determine the simulation interface corresponding to the call request of the test mobile gateway, parse the interface documents corresponding to the simulation interface, and generate the simulation message.

5. The mobile Internet product client test system of claim 1, wherein, The synchronization module is further configured to configure the message fed back by the background service as the simulation message fed back by the simulation message generator. 6.The mobile Internet product client test system of claim 1, wherein, The mobile internet product client test system further comprises a simulation message management terminal; The synchronization module is further configured to send field information in the message fed back by the background service to the simulation message management terminal; The simulation message management terminal is configured 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 configured to determine the simulation interface corresponding to the calling request of the test mobile gateway, parse the interface document corresponding to the simulation interface, and generate the simulation message.

7. A client testing method, characterized by, Comprise: 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 calling request to the test mobile gateway, the local test offline package comprising target product page resources to be tested, and being used to call the simulation message generator for local testing; The test mobile gateway calls the simulation message generator through a 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; The client test method further comprises: The client downloads a joint debugging offline package from the test mobile publishing module, and runs the joint debugging offline package to send a background interface calling request to the test mobile gateway; The test mobile gateway calls a background service through a second interface in response to the background interface calling request; The background service generates a corresponding message in response to the calling request of the test mobile gateway, and feeds back the corresponding message to the client through the test mobile gateway; The synchronization module periodically checks interface configuration of a target product page to be tested in the test mobile gateway, and creates an interface for calling the simulation message generator in the test mobile gateway for the target product page if the test mobile gateway comprises an interface for calling the background service but does not comprise an interface for calling the simulation message generator.

Images