Service joint debugging test method and device

Abstract

The invention discloses a service joint debugging test method and device, and relates to the technical field of computers. A specific embodiment of the method comprises the following steps: in response to a service joint debugging test request, opening a sandbox environment and deploying a simulation service for providing a service processing flow in the sandbox environment; responding to a received service request sent by a user, and obtaining an access domain name corresponding to the service request; and under the condition that the access domain name is the domain name specified by the sandbox environment, forwarding the service request to a simulation service so as to perform a service joint debugging test through a service processing flow provided by the simulation service. According to the embodiment, the whole-process information of the business process is simulated through the controllable, extensible and user-customizable sandbox joint debugging tool, the risk of data clearing errors does not exist, the business docking speed is increased, and the test cost is reduced; and internal operation personnel of an enterprise do not need to participate, so that the labor cost is reduced, and data leakage is avoided.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular, to a method and apparatus for business joint debugging and testing. Background Art

[0002] In the process of the express delivery service of a logistics enterprise being opened to the outside world, usually, an API (Application Programming Interface) docking system provided by the logistics enterprise open platform is used to realize the automation of services such as express order placement and logistics information query. When a new customer docks with the system, the customer needs to conduct joint debugging and testing with the open platform to verify the entire process of the customer's logistics business. Currently, joint debugging and testing are mostly carried out by marking the customer account and business code and then conducting joint debugging and testing in the production environment, or by the customer or platform operator operating in the test environment.

[0003] In the process of implementing the present invention, the inventor found that there are at least the following problems in the prior art:

[0004] Conducting joint debugging and testing in the production environment requires deleting test data, which poses a risk of incorrect data clearing, and when the business process takes a long time, it will bring additional test costs; conducting joint debugging and testing in the test environment requires the participation of the customer or platform operator, resulting in high development and maintenance costs and easy data leakage. Summary of the Invention

[0005] In view of this, embodiments of the present invention provide a method and apparatus for business joint debugging and testing, which can introduce a sandbox tool to encapsulate the business process in the open platform management end to form a black box, where users cannot perceive the business process. They only need to make a business request on the open platform page to obtain the corresponding joint debugging and testing result. Through a controllable, extensible, and user-customizable sandbox joint debugging tool, the whole process information of the business process is simulated, there is no risk of incorrect data clearing, the business docking speed is improved, and the test cost is reduced; and the participation of enterprise internal operators is not required, reducing the labor cost and preventing data leakage.

[0006] To achieve the above object, according to one aspect of the embodiments of the present invention, a method for business joint debugging and testing is provided, including:

[0007] In response to a business joint debugging and testing request, open a sandbox environment and deploy a simulation service for providing a business processing process in the sandbox environment;

[0008] In response to receiving a business request sent by a user, obtain the access domain name corresponding to the business request;

[0009] When the accessed domain name is the domain name specified for the sandbox environment, forward the service request to the simulation service to perform service joint debugging tests through the service processing flow provided by the simulation service.

[0010] Optionally, the simulation service provides service processing flows corresponding to at least one service scenario; before receiving a service request sent by a user, it further includes: determining the service processing flow corresponding to this service joint debugging test according to the service scenario selected by the user.

[0011] Optionally, the service processing flow includes at least one process node, and the service request includes a current node identifier; performing service joint debugging tests through the service processing flow provided by the simulation service includes: obtaining the waybill status according to the current node identifier through the simulation service, obtaining the to-be-processed process node from the service processing flow according to the waybill status and the current node identifier, and obtaining the simulation test result corresponding to the to-be-processed process node to perform service joint debugging tests.

[0012] Optionally, it further includes: after obtaining the simulation test result corresponding to the to-be-processed process node, updating the waybill status.

[0013] Optionally, it further includes: before updating the waybill status, verifying whether the waybill status before and after this update is mutually exclusive.

[0014] Optionally, it further includes: when the service joint debugging test is completed or no service request is received after exceeding the set time, canceling the sandbox environment and releasing resources.

[0015] According to another aspect of the embodiments of the present invention, there is provided a device for service joint debugging tests, including:

[0016] An environment deployment module, configured to respond to a service joint debugging test request, open a sandbox environment and deploy a simulation service for providing a service processing flow in the sandbox environment;

[0017] A domain name acquisition module, configured to respond to receiving a service request sent by a user and acquire the access domain name corresponding to the service request;

[0018] A simulation test module, configured to forward the service request to the simulation service when the access domain name is the domain name specified for the sandbox environment, so as to perform service joint debugging tests through the service processing flow provided by the simulation service.

[0019] Optionally, the simulation service provides business processing flows corresponding to at least one business scenario; the device further includes a process determination module, configured to: before receiving a business request sent by a user, determine the business processing flow corresponding to this business joint debugging test according to the business scenario selected by the user.

[0020] According to another aspect of the embodiments of the present invention, there is provided an electronic device, including: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, enabling the one or more processors to implement the method for business joint debugging test provided by the embodiments of the present invention.

[0021] According to still another aspect of the embodiments of the present invention, there is provided a computer-readable medium, on which a computer program is stored, and when the program is executed by a processor, it implements the method for business joint debugging test provided by the embodiments of the present invention.

[0022] One embodiment of the above invention has the following advantages or beneficial effects: By responding to a business joint debugging test request, opening a sandbox environment and deploying a simulation service for providing business processing flows in the sandbox environment; in response to receiving a business request sent by a user, obtaining the access domain name corresponding to the business request; in the case where the access domain name is the domain name specified for the sandbox environment, forwarding the business request to the simulation service to perform business joint debugging test through the business processing flow provided by the simulation service. Through the technical solution of introducing a sandbox tool, encapsulating the business process in the open platform management end to form a black box, users cannot perceive the business process, and only need to make a business request on the open platform page to obtain the corresponding joint debugging test result. Through a controllable, extensible, and user-customizable sandbox joint debugging tool, simulating the whole process information of the business process, there will be no risk of data clearing errors, improving the business docking speed, reducing the test cost; and without the participation of enterprise internal operation personnel, reducing the labor cost and not causing data leakage.

[0023] The further effects of the above non-conventional optional manner will be described in combination with specific embodiments below. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The drawings are used to better understand the present invention and do not constitute an improper limitation to the present invention. Among them:

[0025] Figure 1 is a schematic diagram of the main steps of the method for business joint debugging test according to the embodiments of the present invention;

[0026] Figure 2 is a schematic diagram of the sandbox environment application process of an embodiment of the present invention;

[0027] Figure 3Schematic diagram of the state change process of the sandbox environment according to an embodiment of the present invention;

[0028] Figure 4 Schematic diagram of the implementation principle of the business joint debugging test according to an embodiment of the present invention;

[0029] Figure 5 Schematic diagram of the business joint debugging test process according to an embodiment of the present invention;

[0030] Figure 6 Schematic diagram of the main modules of the device for the business joint debugging test according to an embodiment of the present invention;

[0031] Figure 7 Exemplary system architecture diagram to which an embodiment of the present invention can be applied;

[0032] Figure 8 Schematic diagram of the structure of a computer system of a terminal device or a server suitable for implementing an embodiment of the present invention. Detailed implementation manners

[0033] The following describes exemplary embodiments of the present invention with reference to the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding. It should be considered that they are merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, descriptions of well-known functions and structures are omitted in the following.

[0034] It should be noted that in the technical solutions disclosed in the present invention, in terms of the collection, collection, update, analysis, processing, use, transmission, storage, etc. of user personal information, they all comply with the provisions of relevant laws and regulations, are used for legal purposes, and do not violate public order and good customs. Necessary measures are taken for user personal information to prevent illegal access to user personal information data, and to maintain the security of user personal information, network security, and national security.

[0035] In the process of the express delivery business of logistics enterprises being opened to the outside world, one of the most common opening methods is the API interface. Customers connect to the system through the express delivery API provided by the logistics enterprise open platform to automate business such as express order placement and logistics information query. When new customers connect to the system, they need to obtain the business node information of the waybill at different transportation stages of the express delivery enterprise for the customer to verify the entire process of the logistics business. For example, from order placement to pickup, sorting, distribution, and delivery. At present, there are the following three most common technical solutions for completing the transfer of express waybills in logistics enterprises during the joint debugging test stage:

[0036] 1. Use the production environment as the environment for business joint debugging. The open platform marks the customer's accounts and business codes. After the joint debugging test passes, the data generated during the test and joint debugging on the production environment is cleared.

[0037] 2. Provide an independent environment identical to the production environment on the open platform to simulate the operation processes of all links in the express delivery business. These simulated business nodes need to be exposed to external customers, and external customers operate these nodes on the page to achieve the closed-loop of the business process (for example, customers operate actions such as pickup completion, sorting and shipping, and delivery) to achieve the purpose of the express waybill flowing within the logistics enterprise.

[0038] 3. Provide an independent environment identical to the production environment (including APIs and enterprise operation systems), which is generally the test environment. Customers call the APIs in the test environment to complete the creation of corresponding documents, and the internal operation personnel of the enterprise complete the flow of express waybills in each business link in the test environment of the enterprise operation system to achieve the simulation of the operation process of the business in the real scenario and complete the full-scenario joint debugging of the customers.

[0039] However, several existing technical solutions have the following problems:

[0040] 1. In the existing solution 1, when using the production environment for joint debugging and marking the customer codes, due to the need to clear the business data generated during the joint debugging, there is a very high operation risk, such as deleting the wrong data, resulting in the permanent loss of data; if the customer has gone live and forgets to remove the sandbox mark, it will cause the problem of inability to clear the data, resulting in the chaos of the billing system.

[0041] 2. And for the existing solution 1, when conducting joint debugging tests in the production environment, business documents will flow to the enterprise's operation system, increasing the burden on front-line operations and wasting human resources; secondly, some operation processes of the enterprise have the characteristic of lag. For example, in the transportation link, to complete this link, the transportation vehicle needs to arrive at the station before it can be operated, which requires a long time of waiting and brings additional implementation costs to the project.

[0042] 3. In the existing solution 2, by exposing the enterprise's internal operation system to simulate the real operations of all business links, the enterprise's internal operation system will be exposed to external customers (or competitors), resulting in the leakage of enterprise secrets; secondly, the system needs to be continuously maintained, increasing the development and maintenance costs.

[0043] 4. In the existing solution 3, although it solves the problems of the existing solutions 1 and 2, it introduces new problems, that is, it requires the internal test personnel of the enterprise to simulate the operation according to the rhythm of the customers, directly increasing the access cost and joint debugging test cost.

[0044] Figure 1It is a schematic diagram of the main steps of the service joint debugging test method according to an embodiment of the present invention. As Figure 1 shown, the service joint debugging test method according to the embodiment of the present invention mainly includes the following steps S101 to S103.

[0045] Step S101: In response to a service joint debugging test request, open a sandbox environment and deploy a simulation service for providing a service processing flow in the sandbox environment. A sandbox is a virtual execution environment for network programming with high security and is generally used for operations such as program testing. In the embodiment of the present invention, when performing a service joint debugging test, the simulation service can be deployed in the sandbox environment, and request operations can be performed through sandbox tools.

[0046] Figure 2 It is a schematic diagram of the sandbox environment application process according to an embodiment of the present invention. As Figure 2 shown, when a user requests a service joint debugging test, a sandbox environment will be opened on the enterprise open platform. The customer logs in to the enterprise open platform to apply for using the sandbox tool. For example, the application can be sent through technical means such as Message Queue MQ and HTTP requests. The open platform will asynchronously open the sandbox environment, and then deploy a simulation service (i.e., MOCK service) through the device for deploying business services, that is, open the MOCK server. After that, services can be provided through the MOCK server.

[0047] After that, the MOCK server will initialize the node configuration and waybill status of each process node included in the service processing flow. The open platform page organizes an HTTP request, and passes the node identifier (such as node code) to the simulation service (i.e., MOCK service) deployed in the sandbox environment through the open platform API interface gateway. The MOCK service processes the HTTP service request according to the current status and node of the waybill, modifies the waybill status according to the configuration of the MOCK node, and returns the execution result to the open platform page for display to the user, automatically completing the joint debugging of a business scenario.

[0048] In order to distinguish between service requests sent by the sandbox tool and those sent by non-sandbox tools, the present invention can use a set of login information for the sandbox environment of the enterprise open platform specifically for the sandbox tool, for example, including three parameters: app_key, app_secret, and access_token, and use these three parameters for user signature and authentication. For requests initiated by the sandbox tool, the domain name corresponding to the HTTP request uses the domain name specified by the sandbox tool. After the API gateway receives the request, it distributes the traffic to the MOCK service through the domain name; for requests sent by non-sandbox tools, the API gateway normally distributes the traffic to each business system within the enterprise.

[0049] In an embodiment of the present invention, a state machine is used to record the state of the sandbox environment. Figure 3 It is a schematic diagram of the state change process of the sandbox environment in an embodiment of the present invention. As Figure 3 shown, when a user applies to use the sandbox tool, the state of the sandbox environment is: being opened; the MOCK service reads the user's account logged in to the open platform, initializes the node configuration and node state, and the state of the sandbox environment is: initializing; when the user starts to use the sandbox environment, the user's request is executed, and the state of the sandbox environment is: running; when the user actively ends the sandbox joint debugging or does not execute the next node for a long time, the sandbox environment is destroyed and resources are released.

[0050] Step S102: In response to receiving a service request sent by a user, obtain the access domain name corresponding to the service request. When receiving a service request sent by a user, the API gateway of the open platform distributes traffic to the simulation service or the online service system according to the domain name corresponding to the service request.

[0051] Step S103: When the access domain name is the domain name specified for the sandbox environment, forward the service request to the simulation service to perform service joint debugging tests through the service processing process provided by the simulation service.

[0052] According to an embodiment of the present invention, the simulation service provides service processing processes corresponding to at least one service scenario. And, before receiving a service request sent by a user, it further includes: determining the service processing process corresponding to this service joint debugging test according to the service scenario selected by the user. In an embodiment of the present invention, the complete process nodes of the express delivery service can be configured in the internal management end of the open platform. A node is a link in the enterprise operation process, such as the courier's collection completion, delivery, etc. In the internal management end of the platform, it is not necessary to actually execute each link, but to configure the result formed after each link is completed, which is reflected in the JSON data structure, that is, MOCK data (the same as the real data format). The MOCK data of these nodes is finally displayed to the user after being processed on the open platform page. At the same time, the user can call the relevant open APIs to query this data, such as querying logistics information, querying freight, etc.

[0053] According to the business processes corresponding to each business scenario, business nodes are combined into individual business processes. For example, the business process corresponding to the scenario of placing a downward express order is: customer places an order → order placed successfully / order placement fails → pickup task assignment → courier picks up →..., and the business process corresponding to the scenario of completing the return of goods by picking up at the door is: customer places an order → pickup task assignment → courier picks up → return of goods by picking up at the door is completed; the business process corresponding to the scenario of terminating the pickup is: customer places an order → pickup task assignment → pickup is terminated; and so on. Under the sandbox tool module of the open platform page, the business processes corresponding to each business scenario can be displayed by business module.

[0054] According to another embodiment of the present invention, the business processing flow includes not less than one process node, and the business request includes a current node identifier. Conducting business joint debugging tests through the business processing flow provided by the simulation service includes: obtaining the waybill status according to the current node identifier through the simulation service, obtaining the to-be-processed process node from the business processing flow according to the waybill status and the current node identifier, and obtaining the corresponding simulation test result of the to-be-processed process node to conduct business joint debugging tests. In the embodiments of the present invention, the waybill status can be saved through memory, files, databases, etc. When different nodes of the business processing flow are executed, the waybill status will change accordingly.

[0055] According to still another embodiment of the present invention, the method for the business joint debugging test further includes: after obtaining the simulation test result corresponding to the to-be-processed process node, updating the waybill status. And, before updating the waybill status, verifying whether the waybill status before and after this update is mutually exclusive.

[0056] Figure 4 It is a schematic diagram of the implementation principle of the business joint debugging test of an embodiment of the present invention. As Figure 4 shown, in an embodiment of the present invention, the implementation principles of the simulation service (i.e., MOCK service) and related components deployed in the sandbox environment are as follows:

[0057] 101 - MOCK service: According to the well - maintained business nodes (i.e., 103 - 107 in the figure), read the waybill status from the status storage 102, and determine the to - be - updated waybill status and the return result according to the configuration. Optionally, active or a scripting language can be used to achieve dynamic storage;

[0058] 102 - Status storage: Used to save the waybill status and the record of the user's application for the sandbox tool, to avoid being accidentally modified, and at the same time save the status modified by 101. Optionally, only the waybill status of the branch selected by the user can be saved, and memory, files, databases can be used for status storage;

[0059] 103 - Order Placement: The user calls the open express order - placing interface. If the parameters are correct, the express waybill number is returned. The API gateway binds the login name app_key for creating the waybill by calling the order - placing interface and the waybill number returned by the interface, and records the status of the waybill number as "initial", writing it into 102 - Status Storage;

[0060] 104 - Pick - up Task Assignment: A process node, target status: success; The customer operates on the waybill number returned by the 103 - order - placing interface in the sandbox tool of the logistics open platform, operates on 104 - pick - up task assignment, and writes it into the status storage device at the same time; It is represented in JSON data structure, and the sandbox tool of the open platform shows that the current waybill status is "pick - up task has been assigned". Other nodes or branch configurations are similar;

[0061] 105 - Door - to - door Pick - up: A process node with two branches, namely: pick - up completed and pick - up terminated;

[0062] 106 - Pick - up Completed: A branch result of the process node, target status: success; The customer operates on the waybill number returned by the 103 - order - placing interface in the sandbox tool of the logistics open platform, operates on 106 - pick - up completed, and writes it into the status storage device; It is represented in JSON data structure, and the sandbox tool of the open platform shows that the current waybill status is "already picked up". Other nodes or branch configurations are similar;

[0063] 107 - Pick - up Terminated: A branch result of the process node, target status: terminated; Mutually exclusive with 106 - pick - up completed; The customer operates on the waybill number returned by the 103 - order - placing interface in the sandbox tool of the logistics open platform, operates on 107 - pick - up terminated, and the MOCK server verifies whether the waybill status can be changed (mutual exclusion check or pre - process verification), and writes it into the status storage device after execution; It is represented in JSON data structure, and the sandbox tool of the open platform shows that the current waybill status is "pick - up cancelled". Other nodes or branch configurations are similar. Here, when performing the mutual exclusion check, it is mainly to verify whether there is a conflict between the current status of the waybill and the waybill status to be changed by the user operation. Taking sending an express as an example, it is obviously unreasonable and impossible for the courier to operate "pick - up completed" on the system and then the user operates to place an order. This is the waybill status conflict; The courier operates "pick - up terminated" and then operates "pick - up completed". These two waybill statuses are mutually exclusive and it is impossible to be both completed and terminated.

[0064] According to another embodiment of the present invention, the method for business joint - debugging test further includes: When the business joint - debugging test is completed or no business request is received after exceeding the set time, log off the sandbox environment and release resources. When the user actively ends the sandbox joint - debugging or does not execute the next node for a long time, the sandbox environment will be destroyed and resources will be released to reduce the server pressure.

[0065] Figure 5 It is a schematic diagram of the business joint debugging test process according to an embodiment of the present invention. As Figure 5 shown, in an embodiment of the present invention, the business joint debugging test process mainly includes the following steps:

[0066] Step 1: Configure complete process nodes of the express delivery business in the sandbox tool module of the enterprise open platform management system, such as the courier's collection completion, proper delivery, etc.; meanwhile, in the open platform management system, the returned simulation test results can also be configured for each process node and presented in the JSON data structure;

[0067] Step 2: Display the business scenarios maintained in the sandbox tool module on the enterprise open platform page; only the configuration in the initial stage is required for this Step 2 and Step 1;

[0068] Step 3: The user logs in to the enterprise open platform, applies to use the sandbox joint debugging tool, opens the sandbox environment, and deploys the MOCK service in the sandbox environment, initializing the process configuration and waybill status;

[0069] Step 4: The user selects the business scenario to be jointly debugged and tested to execute this business joint debugging test through the business process corresponding to the business scenario;

[0070] Step 5: After receiving the business request sent by the user through the sandbox tool, the enterprise open platform assembles the business request using an independent domain name, and the request message contains the current node code;

[0071] Step 6: After the traffic of this business request accesses the API gateway, the gateway performs login status authentication and shunts according to the domain name, and sends the authenticated business request with this independent domain name to the MOCK service;

[0072] Step 7: The MOCK service writes the waybill status from the status storage device;

[0073] Step 8: The MOCK service reads the waybill status from the status storage device;

[0074] Step 9: The MOCK service processes the request using the node according to the user account and the current waybill status, determines the to-be-processed node according to the process configuration, obtains the simulation test result of the to-be-processed node configured in advance and returns it, and modifies the waybill status;

[0075] Step 10: The user views the simulation test result on the open platform page.

[0076] Figure 6 It is a schematic diagram of the main modules of the device for business joint debugging test according to an embodiment of the present invention. As Figure 6 shown, the device 600 for business joint debugging test according to an embodiment of the present invention mainly includes:

[0077] An environment deployment module 601, configured to, in response to a business joint debugging test request, activate a sandbox environment and deploy a simulation service for providing a business processing flow in the sandbox environment;

[0078] A domain name acquisition module 602, configured to, in response to receiving a business request sent by a user, acquire an access domain name corresponding to the business request;

[0079] A simulation test module 603, configured to, when the access domain name is the domain name specified for the sandbox environment, forward the business request to the simulation service, so as to perform a business joint debugging test through the business processing flow provided by the simulation service.

[0080] According to an embodiment of the present invention, the simulation service provides business processing flows corresponding to at least one business scenario. The apparatus 600 further includes a process determination module (not shown in the figure), configured to: before receiving a business request sent by a user, determine a business processing flow corresponding to this business joint debugging test according to the business scenario selected by the user.

[0081] According to another embodiment of the present invention, the business processing flow includes at least one process node, and the business request includes a current node identifier; the simulation test module 603 may further be configured to: obtain a waybill status according to the current node identifier through the simulation service, obtain a to-be-processed process node from the business processing flow according to the waybill status and the current node identifier, and obtain a simulation test result corresponding to the to-be-processed process node, so as to perform a business joint debugging test.

[0082] According to still another embodiment of the present invention, the apparatus 600 further includes a status update module (not shown in the figure), configured to: after obtaining the simulation test result corresponding to the to-be-processed process node, update the waybill status.

[0083] According to still another embodiment of the present invention, the status update module (not shown in the figure) may further be configured to: before updating the waybill status, verify whether the waybill status before and after this update is mutually exclusive.

[0084] According to still another embodiment of the present invention, the apparatus 600 further includes an environment cancellation module (not shown in the figure), configured to: in the case of completing the business joint debugging test or not receiving a business request for more than a set time, cancel the sandbox environment and release resources.

[0085] According to the technical solution of the embodiment of the present invention, by responding to the business joint debugging test request, a sandbox environment is opened and a simulation service for providing a business processing flow is deployed in the sandbox environment; in response to receiving a business request sent by a user, the access domain name corresponding to the business request is obtained; in the case that the access domain name is the domain name specified for the sandbox environment, the business request is forwarded to the simulation service to perform a business joint debugging test through the business processing flow provided by the simulation service. By introducing a sandbox tool, the business process is encapsulated in the open platform management end to form a black box, and users cannot perceive the business process. They only need to make a business request on the open platform page to obtain the corresponding joint debugging test result. Through a controllable, extensible, and user-customizable sandbox joint debugging tool, the whole process information of the business process is simulated, there is no risk of data clearing errors, the business docking speed is improved, and the test cost is reduced; and it does not require the participation of enterprise internal operators, reducing the labor cost and not causing data leakage.

[0086] In addition, the present invention processes the business in a scenario-based manner, simulates the information of each node in the process of the business flowing in the physical world, visualizes the scenario of the business on the enterprise open platform page, and users only need to select the scenario to complete the transfer of the simulated business process information and complete the business joint debugging of the specified scenario. Through a controllable, extensible, and user-customizable sandbox joint debugging tool, the whole process information of the business process is simulated, the business docking speed is improved, and it does not require the participation of enterprise internal operations, reducing the labor cost.

[0087] Figure 7 An exemplary system architecture 700 is shown that can apply the method for business joint debugging test or the device for business joint debugging test of the embodiment of the present invention.

[0088] As Figure 7 shown, the system architecture 700 may include terminal devices 701, 702, 703, a network 704, and a server 705. The network 704 is used to provide a medium for a communication link between the terminal devices 701, 702, 703 and the server 705. The network 704 may include various connection types, such as wired, wireless communication links, or fiber optic cables, etc.

[0089] Users can use the terminal devices 701, 702, 703 to interact with the server 705 through the network 704 to receive or send messages, etc. Various communication client applications may be installed on the terminal devices 701, 702, 703, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only for example).

[0090] The terminal devices 701, 702, and 703 can be various electronic devices with a display screen and supporting web browsing, including but not limited to smartphones, tablet computers, laptop computers, desktop computers, and so on.

[0091] The server 705 can be a server that provides various services. For example, it can be a background management server (only for example) that supports the websites browsed by users using the terminal devices 701, 702, and 703. The background management server can respond to data such as service joint debugging test requests. In response to the service joint debugging test request, it can open a sandbox environment and deploy a simulation service for providing business processing procedures in the sandbox environment; in response to a service request sent by a user, it can obtain the access domain name corresponding to the service request; when the access domain name is the domain name specified for the sandbox environment, it can forward the service request to the simulation service to perform service joint debugging tests and other processing through the business processing procedures provided by the simulation service, and feedback the processing results (such as service joint debugging test results - only for example) to the terminal device.

[0092] It should be noted that the method for service joint debugging test provided by the embodiments of the present invention is generally executed by the server 705. Correspondingly, the device for service joint debugging test is generally set in the server 705.

[0093] It should be understood, Figure 7 The numbers of the terminal devices, networks, and servers in are merely illustrative. According to actual needs, there can be any number of terminal devices, networks, and servers.

[0094] Next, refer to Figure 8 , which shows a schematic structural diagram of a computer system 800 suitable for implementing the terminal device or server of the embodiments of the present invention. Figure 8 The terminal device or server shown is merely an example and should not impose any limitations on the functions and usage scope of the embodiments of the present invention.

[0095] As Figure 8 shown, the computer system 800 includes a central processing unit (CPU) 801, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 802 or the program loaded from the storage section 808 into the random access memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the system 800 are also stored. The CPU 801, ROM 802, and RAM 803 are connected to each other through a bus 804. The input / output (I / O) interface 805 is also connected to the bus 804.

[0096] The following components are connected to the I / O interface 805: an input section 806 including a keyboard, a mouse, etc.; an output section 807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc. and a speaker, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN card, a modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I / O interface 805 as required. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is mounted on the drive 810 as required so that a computer program read therefrom is installed into the storage section 808 as required.

[0097] Specifically, according to the embodiments disclosed by the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed by the present invention include a computer program product which includes a computer program carried on a computer-readable medium, and the computer program includes program codes for performing the methods shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 809, and / or installed from the removable medium 811. When the computer program is executed by a central processing unit (CPU) 801, the above-described functions defined in the system of the present invention are performed.

[0098] It should be noted that the computer-readable medium shown in the present invention can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of a computer-readable storage medium can include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium can be any tangible medium that contains or stores a program, and this program can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present invention, a computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, in which computer-readable program code is carried. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, and this computer-readable medium can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on a computer-readable medium can be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0099] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagram can represent a module, a program segment, or a part of code, and the above module, program segment, or part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks can occur in a different order from that marked in the accompanying drawings. For example, two consecutive blocks shown can actually be executed substantially in parallel, and they can sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, and the combination of blocks in the block diagram or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0100] The units or modules involved in the embodiments of the present invention can be implemented in software or in hardware. The described units or modules can also be provided in a processor. For example, it can be described as: a processor includes an environment deployment module, a domain name acquisition module, and a simulation test module. Among them, the names of these units or modules do not constitute a limitation on the units or modules themselves in some cases. For example, the environment deployment module can also be described as "a module for responding to a business joint debugging test request, opening a sandbox environment, and deploying a simulation service for providing a business processing flow in the sandbox environment".

[0101] As another aspect, the present invention also provides a computer-readable medium. The computer-readable medium can be included in the device described in the above embodiments; or it can exist alone without being assembled into the device. The above computer-readable medium carries one or more programs. When the one or more programs are executed by the device, the device includes: responding to a business joint debugging test request, opening a sandbox environment, and deploying a simulation service for providing a business processing flow in the sandbox environment; responding to a business request sent by a user, acquiring the access domain name corresponding to the business request; and when the access domain name is the domain name specified for the sandbox environment, forwarding the business request to the simulation service to perform business joint debugging test through the business processing flow provided by the simulation service.

[0102] According to the technical solution of the embodiments of the present invention, by responding to a business joint debugging test request, opening a sandbox environment, and deploying a simulation service for providing a business processing flow in the sandbox environment; responding to a business request sent by a user, acquiring the access domain name corresponding to the business request; and when the access domain name is the domain name specified for the sandbox environment, forwarding the business request to the simulation service to perform business joint debugging test through the business processing flow provided by the simulation service. By introducing a sandbox tool, encapsulating the business process in the open platform management end to form a black box, the user cannot perceive the business process. Only by making a business request on the open platform page can the corresponding joint debugging test result be obtained. Through a controllable, extensible, and user-customizable sandbox joint debugging tool, the whole process information of the business process is simulated, and there is no risk of data clearing error, which improves the business docking speed, reduces the test cost; and does not require the participation of enterprise internal operation personnel, reduces the labor cost, and does not cause data leakage.

[0103] The above specific embodiments do not constitute a limitation on the protection scope of the present invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for joint debugging and testing of services, characterized in that, Including: In response to a business joint debugging test request, open a sandbox environment and deploy a simulation service for providing a business processing flow in the sandbox environment; In response to receiving a business request sent by a user, obtain the access domain name corresponding to the business request; When the access domain name is the domain name specified for the sandbox environment, forward the business request to the simulation service to conduct a business joint debugging test through the business processing flow provided by the simulation service.

2. The method according to claim 1, characterized in that, The simulation service provides business processing flows corresponding to at least one business scenario; Before receiving a business request sent by a user, it further includes: According to the business scenario selected by the user, determine the business processing flow corresponding to this business joint debugging test.

3. The method according to claim 1 or 2, characterized in that, The business processing flow includes at least one process node, and the business request includes a current node identifier; Conducting a business joint debugging test through the business processing flow provided by the simulation service includes: Through the simulation service, obtain the waybill status according to the current node identifier, obtain the to-be-processed process node from the business processing flow according to the waybill status and the current node identifier, and obtain the corresponding simulation test result of the to-be-processed process node to conduct a business joint debugging test.

4. The method according to claim 3, characterized in that, It further includes: After obtaining the simulation test result corresponding to the to-be-processed process node, update the waybill status.

5. The method according to claim 4, characterized in that, It further includes: Before updating the waybill status, verify whether the waybill status before and after this update is mutually exclusive.

6. The method according to claim 1, characterized in that, It further includes: In the case of completing the business joint debugging test or not receiving a business request for more than a set time, cancel the sandbox environment and release resources.

7. A device for joint debugging and testing of services, characterized in that, Including: An environment deployment module, configured to open a sandbox environment and deploy a simulation service for providing a business processing flow in the sandbox environment in response to a business joint debugging test request; A domain name acquisition module, configured to obtain the access domain name corresponding to the business request in response to receiving a business request sent by a user; A simulation test module, configured to forward the business request to the simulation service when the access domain name is the domain name specified for the sandbox environment, so as to conduct a business joint debugging test through the business processing flow provided by the simulation service.

8. The device according to claim 7, characterized in that, The simulation service provides business processing flows corresponding to at least one business scenario; The device further includes a process determination module, configured to: before receiving a business request sent by a user, determine the business processing flow corresponding to this business joint debugging test according to the business scenario selected by the user.

9. An electronic device, characterized in that, Including: One or more processors; A storage device, configured to store one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 - 6.

10. A computer-readable medium, on which a computer program is stored, characterized in that, When the program is executed by the processor, it implements the method according to any one of claims 1 - 6.

Images