Sandbox joint debugging method, device and equipment and computer readable storage medium
Through the sandbox joint commissioning method, the logistics distribution process is simulated in the logistics system, and the problem of time-consuming and wasteful resources in the existing technology is solved, and efficient logistics docking is achieved.
Patent Information
- Application Number
- CN202310666962.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-06-06
- Publication Date
- 2024-12-06
AI Technical Summary
The existing logistics system cannot effectively simulate the real ordering process during the joint commissioning process, which leads to a long time and a waste of human resources, reducing the efficiency of logistics docking.
The sandbox joint debugging method is used to simulate the logistics distribution process through sandbox tools and gateways, and business process operation information is received and sent until the last business process joint debugging result is passed, and the logistics distribution joint debugging task is completed.
The normal order placing process can be simulated without real ordering, which improves the safety of order circulation and the integrity of logistics testing, saves human resources, and improves logistics docking efficiency.
Smart Images

Figure CN119088668A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a sandbox joint debugging method, apparatus, device and computer-readable storage medium. Background Art
[0002] With the rapid development of logistics platforms, some platforms have built large-scale logistics systems. Most of the express merchants currently connected to the platform have the need for joint debugging of the distribution link. Joint debugging refers to a series of debugging processes used by the interface caller (merchant) to confirm the validity of the program after the interface caller (merchant) completes the development of the relevant program according to the interface document.
[0003] The production system in the relevant technology does not support test joint debugging. After the program developed by the merchant is completed, it will ask whether there is a test environment for joint debugging. The implementation will inform that there is no test environment and that orders can only be placed using the production environment interface. The test process is to mark the order as [test order] and cancel it in time after placing the order. If you want to verify the entire process of the order, you need to actually ship it. You need to wait for the courier to pick it up at the door, and the logistics system will deliver the package. After the consumer receives the package, you can query the complete logistics information, and the merchant can confirm that the joint debugging is completed.
[0004] The debugging process in related technologies will produce an actual execution process, call the real deployment of the logistics system, and judge the program operation status based on the feedback from the logistics system, so as to judge whether the developed program meets expectations. The entire joint debugging process is time-consuming and wastes human and material resources, reducing the efficiency of logistics docking. Summary of the invention
[0005] The embodiments of the present application provide a sandbox joint debugging method, device, equipment and computer-readable storage medium, which improve the efficiency of logistics docking.
[0006] The technical solution of the embodiment of the present application is implemented as follows:
[0007] In the first aspect, an embodiment of the present application provides a sandbox joint debugging method, which is applied to a logistics scenario. The method includes: when the result of the order interface call is characterized as passed, based on the sandbox tool and the obtained test order number, each operation information of each business process for the logistics distribution joint debugging task is received in sequence; each operation information is sent to each business interface corresponding to the each business process in the business system through the gateway in sequence; each business process joint debugging result is received by the business system based on the each operation information, until the last business process joint debugging result is characterized as passed, thereby completing the sandbox joint debugging process of the logistics distribution joint debugging task.
[0008] In the second aspect, an embodiment of the present application provides a sandbox joint debugging device, which includes: a receiving module, which is used to receive, based on the sandbox tool and the obtained test order number, each operation information of each business process for the logistics distribution joint debugging task in sequence when the result of the order interface call is characterized as passed; a sending module, which is used to send each operation information to each business interface corresponding to the each business process in the business system through the gateway in sequence; the receiving module is also used to receive each business process joint debugging result returned by the business system based on the each operation information, until the last business process joint debugging result is characterized as passed, thereby completing the sandbox joint debugging process of the logistics distribution joint debugging task.
[0009] In a third aspect, an embodiment of the present application provides a sandbox joint debugging device, the device comprising: a memory for storing an executable computer program; and a processor for implementing the sandbox joint debugging method described in the first aspect when executing the executable computer program stored in the memory.
[0010] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program for implementing the sandbox joint debugging method described in the first aspect when executed by a processor.
[0011] The embodiment of the present application provides a sandbox joint debugging method, device, equipment and computer-readable storage medium. According to the scheme provided by the embodiment of the present application, the method includes: when the result of the order interface call is characterized as passed, based on the sandbox tool and the obtained test order number, each operation information of each business process for the logistics distribution joint debugging task is received in sequence; each business interface corresponding to each business process in the business system is sent through the gateway in sequence; each business process joint debugging result returned by the business system based on each operation information is received, until the last business process joint debugging result is characterized as passed, and the sandbox joint debugging process of the logistics distribution joint debugging task is completed. The sandbox joint debugging method can be applied to logistics scenarios. The logistics service initiator does not need to place an order in real time. When the result of the order interface call is characterized as passed, it means that a normal ordering process can be simulated, and the logistics distribution joint debugging process can be started, which improves the security of order flow. Then, the interface of the business system is sequentially debugged through the network, which is a related program for processing the logistics distribution process in the real logistics scenario. By calling the relevant interface, each business process is completed in sequence, and the entire logistics distribution test process can be completed, which improves the integrity of the entire flow process in the logistics test phase and improves the efficiency of logistics docking. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] Figure 1 A flowchart of optional steps of a sandbox joint debugging method provided in an embodiment of the present application;
[0013] Figure 2An optional step flow chart of another sandbox joint debugging method provided in an embodiment of the present application;
[0014] Figure 3 An optional schematic diagram of a sandbox joint debugging page of a sandbox tool provided in an embodiment of the present application;
[0015] Figure 4 An optional schematic diagram of development test information of a sandbox tool provided in an embodiment of the present application;
[0016] Figure 5 An optional schematic diagram of the principle structure of a sandbox joint debugging system provided in an embodiment of the present application;
[0017] Figure 6 An optional schematic diagram of a service node of a sandbox tool provided in an embodiment of the present application;
[0018] Figure 7 An optional schematic diagram of a service node of another sandbox tool provided in an embodiment of the present application;
[0019] Figure 8 An optional flow chart of a sandbox joint debugging process provided in an embodiment of the present application;
[0020] Fig. 9 A flowchart of optional steps of another sandbox joint debugging method provided in an embodiment of the present application;
[0021] Fig.10 An optional schematic diagram of a service node of another sandbox tool provided in an embodiment of the present application;
[0022] Fig.11 An optional structural diagram of a sandbox joint debugging device provided in an embodiment of the present application;
[0023] Fig.12 A schematic diagram of the structure of a sandbox joint debugging device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0024] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. It should be understood that some of the embodiments described here are only used to explain the technical solutions of the present application and are not used to limit the technical scope of the present application.
[0025] In order to better understand the sandbox joint debugging method provided in the embodiment of the present application, before introducing the technical solution of the embodiment of the present application, the application background and related technologies are first explained.
[0026] In related technologies, if you want to verify the entire order process, you need to execute the normal complete delivery process, through real delivery, waiting for the courier to pick up the package, the logistics system to deliver the package, until the consumer receives the package, and then query the complete logistics information to determine the program operation status. For merchants, orders in the test phase cannot be reimbursed, which reduces the logistics access experience and reduces the efficiency of business docking.
[0027] The business joint debugging test mode in related technologies will also bring the following technical problems: (1) It affects the normal operation of the site. The test order will also enter the production. The courier will find out that it is a test after picking up the order. In addition, if the merchant does not cancel the order in time, abnormal data of the site will be generated, affecting the site assessment indicators. (2) The merchant cannot verify the delivery scenario in the development and testing phase. If the order is canceled immediately after placing the order, the logistics information of the order cannot be queried. If verification is required, the actual delivery can only be carried out, but it is affected by the logistics fulfillment time (the actual logistics delivery process takes time), which increases the docking cycle. At the same time, using the production environment to verify the delivery scenario will generate billing, and the merchant cannot report it, which reduces the logistics access experience. (3) After the business is connected, the merchant places a real order, but the courier will mistakenly think that the merchant is still testing and has not picked up the item at the door, which causes the merchant to think that the logistics is not timely for collection, which reduces the logistics access experience. (4) Using the production environment to verify the entire business process requires the implementation of linkage sales and operation colleagues (for example, couriers, site staff, etc.) to cooperate in the operation, which increases the communication cost. As all express delivery merchants switch to the logistics open platform, the current joint debugging mode has increased the labor cost of operation and maintenance. 1. It is impossible to serve multiple merchants at the same time, which reduces the quality of logistics services. For scenarios where two or more merchants place [test orders] at the same time, the same courier can only pick up one [test order] at the same time, that is, it is impossible to serve multiple merchants at the same time. (5) Merchants cannot test and verify abnormal scenarios and can only solve them after they are generated during the online trial operation phase, which involves a certain amount of code rework. For C-end users (for example, self-developed merchants), C-end users cannot directly use the logistics open platform and need to access the logistics open platform through their own coding code. Before officially accessing the logistics open platform, it is necessary to run the code written by themselves to test the feasibility of the code. In related technologies, it is necessary to directly go online for trial operation. After discovering problems, the code needs to be reworked, which increases labor costs.
[0028] The present application embodiment provides a sandbox joint debugging method, which is applied to logistics scenarios, such as Figure 1 As shown, Figure 1 A flow chart of a sandbox joint debugging method provided in an embodiment of the present application, the sandbox joint debugging method comprises the following steps:
[0029] S101. When the result of the order interface call is characterized as passed, based on the sandbox tool and the obtained test order number, each operation information of each business process for the logistics distribution joint debugging task is received in sequence.
[0030] In an embodiment of the present application, the logistics joint debugging method provided in the embodiment of the present application is applied to an open platform. After the logistics service initiator completes the program development on the open platform (i.e., locally), it prepares for joint debugging to test whether the developed program can be implemented. An order request is initiated to the gateway through the local development test interface, and the order interface of the business system is first called. The business system returns the order interface call result and the test order number. When the order interface call result characterizes passing, it means that the normal simulation order process can be performed. Based on the sandbox tool in the open platform, the logistics service initiator performs interface operations for the first business process (order process) according to the test order number returned by the business system, that is, enters the waybill number. The entered waybill number must be consistent with the test order number in order to successfully debug the first business process. Then the logistics service initiator performs interface operations on the second business process, and so on. The sandbox tool in the open platform receives various operation information for each business process in turn.
[0031] In an embodiment of the present application, the logistics service initiator inputs the corresponding waybill number for the first business process (order process) based on the sandbox tool and the returned test order number, that is, the logistics service initiator inputs the test order number returned by the business system in the sandbox tool of the open platform. Then, the business interface corresponding to the waybill number in the business system is called through the gateway, and the waybill number is sent to it. The business interface matches the relevant program for processing the waybill number in the real logistics scenario, and can return the execution result (i.e., the first business process joint debugging result) based on the waybill number.
[0032] In the embodiment of the present application, the logistics distribution joint debugging task includes at least two business processes, including but not limited to: collection, site delivery, sorting receipt, sorting delivery, site delivery, courier delivery, courier delivery, etc. Each business process simulates the real logistics flow process and corresponds to the real logistics process. The logistics service initiator does not need to place a real order. Based on the business processes in the sandbox tool that simulate the real logistics flow process, the logistics distribution joint debugging process can be started, which improves the security of order flow.
[0033] S102 . Sending various operation information to various business interfaces corresponding to various business processes in the business system through the gateway in sequence.
[0034] In an embodiment of the present application, the logistics service provider inputs operation information on the current business interface corresponding to a current business process, and then sends the operation information to the business interface corresponding to the business process in the business system through the gateway. Then receive the business process coordination result generated by the business system based on the operation information. If the business process coordination result indicates a pass, jump from the current business interface to the next business process coordination interface, and then the logistics service provider inputs operation information on the next business interface corresponding to the next business process, and sends the operation information to the business interface corresponding to the business process in the business system through the gateway. And so on, the development platform sends each operation information to each business interface corresponding to each business process in the business system through the gateway.
[0035] In the embodiment of the present application, the business system is responsible for the normal logistics flow, and has relevant programs for processing the logistics distribution process in the real logistics scene. The business system has interfaces related to logistics distribution (each business process corresponds to at least one interface). Since the interface corresponding to the program developed on the open platform adopts the HyperText Transfer Protocol (HTTP), and the interface related to logistics distribution in the business system adopts the JSF interface protocol, where JSF is a user interface component framework of a Java-based Web application server. These two interfaces cannot be called directly, that is, local development cannot directly call the business system, and it is necessary to call the interface related to logistics distribution in the business system through the gateway. The application programming interface (Application ProgramInterface, API) defined in the gateway is pre-developed and used by the actual business system. The gateway can be understood as a communication bridge between the open platform (local development program) and the logistics system.
[0036] S103, receiving the joint debugging results of each business process returned by the business system based on each operation information, until the last business process joint debugging result representation is passed, and completing the sandbox joint debugging process of the logistics distribution joint debugging task.
[0037] In an embodiment of the present application, the logistics distribution joint debugging task includes at least two business processes. When the order can be placed normally (the result of the order interface call is passed), the logistics service initiator inputs the corresponding operation information (i.e., the waybill number) for the first business process (order process), and calls the business interface corresponding to the waybill number in the business system through the gateway, and sends the waybill number to it. The business interface matches the relevant program for processing the waybill number in the real logistics scenario, and can return the execution result (i.e., the first business process joint debugging result) based on the waybill number. When the result of the first business process joint debugging is passed, the logistics service initiator inputs the corresponding operation information (i.e., the collection information, including the package size, weight, item type, etc.) for the second business process (collection process), and calls the business interface corresponding to the collection information in the business system through the gateway, and sends the collection information to it. The business interface matches the relevant program for processing the collection information in the real logistics scenario, and can return the execution result (i.e., the second business process joint debugging result) based on the collection information. When the result of the joint debugging of the second business process is represented as passed, the logistics service initiator operates on the third business process, and so on, until the result of the joint debugging of the last business process is represented as passed, thus completing the sandbox joint debugging process.
[0038] The sandbox joint debugging method provided in the embodiment of the present application is for the merchants corresponding to the open platform (corresponding to the logistics service initiator). The merchants can operate the steps of each business process on the open platform by themselves and complete the sandbox joint debugging process without actually placing an order. The sandbox joint debugging method provided in the embodiment of the present application does not affect the actual operation of the site by separating the merchant joint debugging test from the production system operation process. Through the simulation tool (corresponding to the sandbox tool), the merchant can independently verify the business process and complete the interface test without the intervention of the logistics system, which improves the docking efficiency and saves human resources. The entire joint debugging process completely simulates the business system. By standardizing the merchant docking test and business launch process, the merchant can find problems during the test joint debugging process, and make changes to its locally developed program to complete the program testing process, so that it can operate normally after the real connection to the business system, reducing the probability of accidents after going online.
[0039] According to the scheme provided by the embodiment of the present application, the method includes: when the result of the order interface call is characterized as passed, based on the sandbox tool and the obtained test order number, each operation information of each business process for the logistics distribution joint debugging task is received in sequence; each operation information is sent to each business interface corresponding to each business process in the business system through the gateway in sequence; each business process joint debugging result returned by the business system based on each operation information is received, until the last business process joint debugging result is characterized as passed, and the sandbox joint debugging process of the logistics distribution joint debugging task is completed. The logistics service initiator does not need to place a real order. When the result of the order interface call is characterized as passed, it means that the normal order process can be simulated, and the logistics distribution joint debugging process can be started, which improves the security of the order flow. Then, the interface of the network association business system is sequentially used to debug the relevant program for processing the logistics distribution process in the real logistics scenario. By calling the relevant interface, each business process is completed in sequence, and the entire logistics distribution test process can be completed, which improves the integrity of the entire flow process in the logistics test phase and improves the efficiency of logistics docking.
[0040] In some embodiments, in the above Figure 1 Before S101, the sandbox joint debugging method also includes S201-S204. Figure 2 As shown, Figure 2 A flowchart of the steps of another sandbox joint debugging method provided in an embodiment of the present application.
[0041] S201. Based on the selected logistics distribution joint debugging task scenario in the sandbox tool, the sandbox test application information used to replace the sandbox environment parameters is displayed.
[0042] In the embodiment of the present application, the open platform is for logistics service providers (for example, merchants). After the development of the logistics service provider is completed, the developer will accurately coordinate and select the scene to be coordinated. For the sandbox coordination method provided in the embodiment of the present application, the coordination scene is the logistics forward distribution coordination task scene. The interface of the open platform displays the sandbox test application information and the business coordination process. The sandbox test application information is the information used to successfully call the interface of the business system. The developer of the logistics service provider needs to configure the sandbox tool based on the sandbox test application information to complete the accurate work of the sandbox coordination. The sandbox test application information can be understood as the configuration information that can successfully call the business system, which can include application information and call information, wherein the application information includes but is not limited to the public key (appkey), password (appsecret), and the call information includes but is not limited to the sandbox environment call address, access token (access token) and customer code (customer code). The developer of the logistics service provider needs to replace the sandbox environment parameters with the sandbox test application information so that the sandbox tool can realize the logistics distribution coordination function.
[0043] In the embodiment of the present application, the logistics service initiator needs to sign a contract with the business system and obtain the customer code. After the logistics service initiator selects the logistics distribution joint debugging task scenario, the open platform provides the logistics service initiator with sandbox test application information based on the customer code, so that the logistics service initiator can configure the sandbox tool, so that the open platform where the logistics service initiator is located can call the corresponding interface in the business system through the gateway.
[0044] In the embodiment of the present application, the above Figure 2 Select the scene to be debugged in Figure 3 As shown, Figure 3 An optional schematic diagram of a sandbox joint debugging page of a sandbox tool provided in an embodiment of the present application, Figure 3 The sandbox joint debugging tool (i.e. sandbox tool) shown in the figure is a simulation tool that assists developers in interface development and joint debugging of major functions. It can intuitively see the call results of its own system and logistics system. After completing the joint debugging, it is also necessary to create a production environment application in [Development Management] and conduct a complete functional acceptance test. Developers can view the joint debugging tasks under the current team on the open platform-sandbox joint debugging page. Each joint debugging scenario corresponds to a joint debugging task. Figure 3 The left column of the sandbox tool shown in the figure includes development management (application management and sandbox joint debugging), personal center and message center. The right column of the sandbox tool is the interface corresponding to the sandbox joint debugging. Figure 3 Three joint debugging scenarios are shown in the figure, including express B2C forward order, express B2C reverse order and logistics cloud printing. Among them, express B2C forward order refers to the process in which the merchant places an order through the open platform and delivers the package to the consumer through the logistics distribution process. It is used to verify the process from order placement to courier collection, site sorting and receipt, site sorting and delivery, courier delivery, customer receipt, etc.; express B2C reverse order refers to the process in which the package needs to be delivered to the merchant through the logistics distribution process after the consumer refuses to accept the package or the consumer returns the package. It is used to verify the process from consumer refusal, return to return to the merchant. The corresponding scenario description of logistics cloud printing is to test express delivery order printing. For these three joint debugging scenarios, merchants can perform the operations of "enter joint debugging" and "view documents".
[0045] In the embodiment of the present application, the above Figure 2 The middle interface displays the sandbox test application information and business joint debugging process. Figure 4 As shown, Figure 4 An optional schematic diagram of development and testing information of a sandbox tool provided in an embodiment of the present application, wherein the open platform provides a sandbox environment, business accounts, and sandbox applications with isolated production data for developers to quickly access and debug business processes. Figure 4The following shows an overview of the sandbox debugging in the development platform, based on the selected Figure 3 The "Express B2C Order" in the document is used to verify the process from express order placement to courier collection. The open platform interface displays development information (i.e. sandbox test application information) and business joint debugging. Among them, development information is the development information provided and displayed by the open platform after the logistics service provider selects the scenario to be joint debugged. The logistics service provider needs to use this development information to conduct joint debugging of the business system. Development information can be understood as the token parameters provided by the business system to the development platform. With these token parameters, the development platform can access or call the corresponding interface in the business system. Figure 4 The development information in the includes application information and test information. The application information includes but is not limited to the public key (appkey) and password (appsecret). Figure 4 In the code, 123abc represents appkey and **** represents appsecret. The call information includes but is not limited to the sandbox environment call address, access token, customer code, and docking solution code. Figure 4 In the sandbox environment, http: / / test-api is used to represent the sandbox environment call address, 78H is used to represent the customer code, 456efg is used to represent the access token, and express is used to represent the docking solution code. Developers of logistics service providers need to replace the sandbox environment parameters with development information so that the sandbox tool can realize the logistics distribution joint debugging function. Figure 4 After the interface is developed, it can be debugged in the sandbox debugging tool. The open platform will generate simulation data based on each step of the developer's operation and perform corresponding debugging functions.
[0046] S202: Receive configuration parameters based on sandbox test application information and order application information.
[0047] In an embodiment of the present application, after the logistics service initiator obtains the sandbox test application information, it needs to replace the sandbox environment parameters in the sandbox tool according to the sandbox test application information, that is, input the configuration parameters to complete the configuration of the sandbox tool.
[0048] In the embodiment of the present application, the logistics distribution joint debugging task is a self-developed program developed by the logistics service initiator, and its feasibility needs to be verified. The logistics service initiator first fills in the order application information through the local development test interface on the open platform. The order application information includes but is not limited to the sender's address, sender's name, sender's contact information, recipient's name, recipient's address, recipient's contact information, etc. Then initiate an order request to the gateway to call the order interface related to the start of the logistics distribution joint debugging task in the business system. The order interface is the interface called after filling in the order application information when the order is started in the real order process.
[0049] S203. Based on the configuration parameters and order application information, an order request is initiated to the gateway through a local development test interface, wherein the order request is used to call an order interface in the business system.
[0050] In an embodiment of the present application, after the sandbox tool is configured, the local development test interface initiates an order request to the gateway based on the order application information to call the order interface in the business system.
[0051] In the embodiment of the present application, since when the request is initiated, it is initiated by the logistics service initiator through the local development test interface, that is, it is executed locally, therefore, at the same time, the open platform can receive order requests initiated by one or more logistics service initiators. Compared with the technical solution in the related technology that can only connect to one [test order] at the same time, the open platform does not limit the number of logistics service initiators that initiate logistics distribution coordination tasks, thereby improving the efficiency of logistics docking.
[0052] S204. Receive the order interface call result and the test order number returned by the business system through the gateway.
[0053] In the embodiment of the present application, in the actual ordering link, the business system generates an order number based on the filled order application information. Therefore, in the simulation of the normal ordering link, the business system will also generate a test order number and return the test order number to the open platform through the gateway. In addition, the business system also returns the order interface call result, which indicates whether the local development program can place an order normally. Only by ensuring that the order can be placed normally can the subsequent steps of filling in the order number, collecting, and shipping be performed; for example, if the logistics service initiator has not signed a contract with the business system, the order interface call result is not passed, indicating that the order cannot be placed normally; if the configuration parameters filled in by the logistics service initiator based on the customer code are incorrect, the order interface call result is not passed, indicating that the order cannot be placed normally.
[0054] In the embodiment of the present application, based on the selected logistics distribution joint debugging task scenario in the sandbox tool, the sandbox test application information is displayed, the logistics service provider uses the sandbox test application information to replace the sandbox environment parameters, completes the configuration of the sandbox tool, and enters the order application information, and initiates an order request to the gateway through the local development test interface to call the order interface in the business system. The gateway receives the order interface call result and the test order number returned by the business system. The logistics service initiator does not need to place a real order, but can independently verify the business process and complete the interface test without the need for the cooperation and intervention of the business system, thereby improving the efficiency of logistics docking.
[0055] In some embodiments, the operation information includes current simulation information related to the current business process, and the business interface includes a current business interface corresponding to the current business process; Figure 1 S102 and S103 can be implemented in the following ways: receiving the current simulation information on the current business interface corresponding to the current business process; sending the current simulation information to the current business interface in the business system through the gateway; receiving the current business process joint debugging result generated by the business system based on the current simulation information through the gateway; if the current business process joint debugging result is characterized as passed, switching from the current business interface to the next business interface; continuously receiving the next simulation information on the next business interface, calling the next business interface corresponding to the next business process in the business system through the gateway, until the last business process joint debugging result is characterized as passed, and completing the sandbox joint debugging process of the logistics distribution joint debugging task.
[0056] In the embodiment of the present application, taking any business process as an example, the logistics service provider enters the current simulation information on the current business interface corresponding to the current business process. The open platform calls the current business interface in the business system through the gateway and sends the current simulation information to the current business interface. The business system generates the current business process joint debugging result based on the current simulation information and sends it to the open platform through the gateway. If the current business process joint debugging result is characterized as passed, the current business interface will be transferred to the next business interface. The logistics service provider continues to enter the next simulation information in the next business interface. The open platform calls the next business interface in the business system through the gateway and sends the next simulation information to the next business interface. The business system returns the next business process joint debugging result generated based on the next simulation information to the open platform, and the cycle continues until the open platform receives the last business process joint debugging result, and the last business process joint debugging result is characterized as passed, completing the sandbox joint debugging process of the logistics distribution joint debugging task.
[0057] In an embodiment of the present application, for each business process in the logistics distribution joint debugging task, the steps of inputting simulation information on the business interface, calling the business interface through the gateway, sending simulation information, and receiving the business process joint debugging results generated based on the simulation information are executed until the last business process joint debugging result is received. The entire process is independently executed by the logistics service provider (merchant). Without placing a real order, the business process can be verified and the interface test can be completed. There is no need for the logistics system to cooperate and intervene, which improves the docking efficiency. Moreover, the entire joint debugging verification process is separated from the production system operation process and does not affect the actual operation of the site. Merchants can find problems during the test and debugging process, and make timely changes to their local development programs to improve the efficiency of logistics docking.
[0058] In some embodiments, based on the above description of the current business process, if the current business process joint debugging result representation fails, the business error result is displayed on the current business interface; the updated simulation information based on the business error result is re-received on the current business interface; the updated simulation information is sent to the current business interface through the gateway; the updated joint debugging result generated by the business system based on the updated simulation information is received through the gateway; if the updated joint debugging result representation fails, the new business error result is re-displayed on the current business interface, and the new simulation information is re-received until the joint debugging result representation passes, and the current business interface is switched to the next business interface.
[0059] In the embodiment of the present application, for a certain business process, since the logistics service initiator needs to fill in some information on the business interface, there will be errors or irregularities in filling in, which does not meet the requirements of the business system for filling in information related to logistics distribution. Therefore, there will be a scenario where the joint debugging fails. When the joint debugging result of the business process fails, the verification of the next business process cannot be carried out. It is necessary to re-fill in the relevant information of the business process and perform joint debugging again until the joint debugging result is passed before the next business process can be operated.
[0060] In an embodiment of the present application, when the business process joint debugging result representation fails, the business system will return the business error result to inform the logistics service provider where the error occurred and the reason for the error. For example, in the order placement process, the waybill number filled in does not meet the regulations; in the collection process, the weight filled in is overweight, the size filled in is too large, etc. This allows the logistics service provider to refer to the business error result so that when filling in the information related to the business process next time, it can be corrected in time and the updated simulation information can be entered. The updated simulation information is sent to the business interface of the business process through the gateway, and the joint debugging result generated by the business system based on the updated simulation information is received. If the joint debugging result representation fails, the business error result will continue to be displayed, so that the logistics service provider can fill in the simulation information again based on the business error result, and the cycle will be repeated until the joint debugging of the business process is successfully completed.
[0061] In an embodiment of the present application, if the representation of the current business process joint debugging result fails, the business error result is displayed on the current business interface. The current business interface is still stayed, and the updated simulation information input by the logistics service provider based on the business error result is re-received; and sent to the current business interface through the gateway, so that the business system generates an updated joint debugging result based on the updated simulation information. If the updated joint debugging result representation fails, the new business error result is displayed on the current business interface again, and a new round of input simulation information, sending simulation information, and generating joint debugging results is repeated until the joint debugging result representation passes, and the current business interface is switched to the next business interface. In this example, business processes are joint debugged one by one. If a business process fails to be joint debugged successfully, only the business process is changed. Compared with the technical solution that requires joint debugging from the first business process when an error occurs, the efficiency of logistics docking is improved.
[0062] In the embodiment of the present application, the sandbox joint debugging method involves an open platform (a carrier of the sandbox tool), a gateway and a business system, for example, Figure 5 As shown, Figure 5 An optional schematic diagram of the principle structure of a sandbox joint debugging system provided in an embodiment of the present application, Figure 5 The interactive process between the open platform, gateway and business system is shown in the figure, and the sandbox joint debugging method is explained in combination with the flow process of the entire business process. After the developer completes the development, the joint debugging is accurate, and the scene to be joint debugged is selected. The sandbox test application information and the business joint debugging process are displayed on the interface of the open platform. The developer uses the sandbox test application information to replace the sandbox environment parameters, so that the sandbox tool can realize the logistics distribution joint debugging function. After the accurate work of the sandbox joint debugging is completed, the developer of the logistics service provider fills in the order application information and starts the joint debugging. The test order number is constructed through the local development test interface, that is, the gateway is requested to call the jsf interface in the business system (corresponding to business interface 1). The business system includes at least business interface 1, business interface 2, business interface 3... business interface n. These n business interfaces are all related programs for processing the logistics distribution process in the real logistics scenario.
[0063] In the embodiment of the present application, the above Figure 5Business interface 1 returns the execution result and the test order number based on the order application information, and the execution result is sent to the local development test interface in the open platform through the gateway. If the execution result is passed, the next step is executed, that is, business process 1 is operated on the interface of the open platform (filling in the waybill number). After filling in the waybill number, the platform verification is performed to verify the consistency between the input waybill number and the test number, and the validity of the test number constructed by the local development test interface is verified. When executing the platform verification, the gateway is requested to call the business interface 2 in the business system. Business interface 2 returns the execution result (that is, the verification result) based on the filled waybill number, and the execution result is sent to the open platform through the gateway. If the execution result is passed, the next step is executed, that is, business process 2 is operated on the interface of the open platform (filling in the collection information). If the execution result fails (or fails), continue to operate business process 1 and re-fill in the waybill number. For the operation business process 2, after filling in the collection information, request the gateway and call the business interface 3 in the business system. Business interface 3 returns the execution result based on the filled in collection information, and the execution result is sent to the open platform through the gateway. If the execution result indicates that it passes, continue to operate business process 3. If the execution result indicates that it fails (or does not pass), continue to operate business process 2 and re-fill in the collection information. And so on, until the interface operation process n receives the execution result returned by the business interface n+1, and the execution result indicates that it passes, all joint debugging processes are completed, and the joint debugging docking is completed.
[0064] In some embodiments, the above Figure 1 In S101, based on the sandbox tool and the obtained test order number, each operation information of each business process for the logistics distribution joint debugging task is received in sequence, which can also be achieved in the following ways. The order placement interface is displayed based on the sandbox tool, and the waybill number based on the test order number is received on the order placement interface; the waybill number is sent to the business interface corresponding to the waybill number in the business system through the gateway, and the platform verification result returned by the business system is received; wherein, the platform verification result includes the validity verification result of the test order number and the consistency verification result between the waybill number and the test order number; if the platform verification result indicates a pass, each operation information is received on each business interface corresponding to each business process.
[0065] In the embodiment of the present application, the above Figure 5 For the operation process 1 (i.e. order process) on the middle interface, please refer to Figure 6 As shown, Figure 6 An optional schematic diagram of a business node of a sandbox tool provided in an embodiment of the present application. A business node refers to each key process required for the current business scenario joint debugging, such as collection, courier receipt, etc. Failure of any business node to execute will result in joint debugging failure. Figure 6The following shows an overview of the sandbox debugging in the development platform, based on the selected Figure 3 The "Express B2C Order" in the courier is used to verify the process from express order placement to courier collection. The open platform interface displays development information (i.e. sandbox test application information) and business joint debugging, among which business joint debugging displays the business processes that have been executed. Figure 6 The figure shows the process of sending a parcel (ordered by the merchant), picking up the parcel (collected by the courier) and checking the logistics track. The process of checking the logistics track can only be executed after the entire business process is completed. There are also multiple business processes between the process of picking up the parcel and the process of completing the process, such as sorting, delivering the parcel and receiving the parcel ( Figure 6 not shown). Figure 6 The order placement process is described. The order placement process is located between the shipping process and the collection process. The order placement interface corresponding to the order placement process displays the order application information entered by the logistics service provider in the order application interface. For example, Figure 6 The "Shipping address: Building 4, District F, E City" is shown in the order interface, and the following information is also prompted to the logistics service provider on the order interface: "Call the courier interface locally, and fill in the waybill number returned by the interface below", and the note "To ensure that the courier can successfully collect the package in the test environment, please fill in the shipping address according to the address provided by the platform." On the order interface, the logistics service provider needs to fill in the test order number returned by the business system in the column corresponding to the logistics waybill number. For example, Figure 6 The following information is also displayed in the place where it needs to be filled in: "Please enter the waybill number returned by the interface, such as: ABXXX", to help the logistics service provider find the correct filling location and fill in the correct waybill number. After filling in the waybill number, the logistics service provider clicks Next, and the open platform needs to perform platform verification. During the platform verification, the waybill number is sent to the business interface corresponding to the waybill number in the business system through the gateway, that is, Figure 5 In business interface 2, the business system verifies the validity of the test order number generated by the open platform based on the local development test interface, and verifies the consistency between the waybill number input by the logistics service provider and the test order number, obtains the platform verification result, and returns the platform verification result to the open platform through the gateway.
[0066] In the embodiment of the present application, after the developer has developed the interface, he can perform joint debugging in the sandbox joint debugging tool. The open platform will generate simulation data based on each step of the user's operation and perform the corresponding joint debugging function. The developer calls the open platform data creation interface locally and enters the data in the first business node interface. The backend service corresponding to the current node verifies the data validity. If it passes, the next business node is executed. If it fails, the reason for failure is transparently transmitted in the interface.
[0067] In an embodiment of the present application, for the order process, the waybill number is entered on the order interface, the business interface is called through the gateway, the validity of the test order number is verified, the consistency of the waybill number and the test order number is verified, and the platform verification result is obtained. If the platform verification result indicates that it passes, subsequent business processes are carried out, such as the collection process, the receiving site process, the shipping site process and the delivery process.
[0068] In some embodiments, if the platform verification result is characterized as passed, the order placement interface is switched to the collection interface, and the collection object information is received on the collection interface; the collection object information is sent to the business interface corresponding to the collection object information in the business system through the gateway, and the collection joint debugging result generated by the business system based on the collection object information is received; if the collection joint debugging result is characterized as passed, the order placement interface is switched to the transfer interface; the transfer information is received on the transfer interface; the transfer information is sent to the business interface corresponding to the transfer information in the business system through the gateway, and the transfer joint debugging result generated by the business system based on the transfer information is received; if the transfer joint debugging result is characterized as passed, the order placement interface is switched to the delivery interface; the delivery information is received on the delivery interface; the delivery information is sent to the business interface corresponding to the delivery information in the business system through the gateway, and the delivery joint debugging result generated by the business system based on the delivery information is received; wherein, the delivery joint debugging result is the last business process joint debugging result.
[0069] In the embodiment of the present application, the above Figure 5 For the operation process 2 on the middle interface, please refer to Figure 7 As shown, Figure 7 An optional schematic diagram of a business node of another sandbox tool provided in an embodiment of the present application. Figure 7 The following shows an overview of the sandbox debugging in the development platform, based on the selected Figure 3 The "Express B2C Order" in the courier is used to verify the process from express order placement to courier collection. The open platform interface displays development information (i.e. sandbox test application information) and business joint debugging, among which business joint debugging displays the business processes that have been executed. Figure 7 It shows the sending of parcels (orders are placed by merchants), the collection of parcels (collected by couriers at doorsteps) and the query of logistics tracks, among which the query of logistics tracks is a business process that can be executed only after the entire business process is completed. Figure 7The pickup interface displays the order information, including the waybill number: ABXXX, pickup time: 1234 / 5 / 6 12:00-13:00, sender: Ms. D, and shipping address: Building 4, District F, City E. Among them, the waybill number is the test order number returned by the business system, and it is also the waybill number filled in by the logistics service provider in the order interface; the pickup time can be the desired pickup time selected by the logistics service provider, or it can be the time generated by the system when the pickup process is triggered; the sender and shipping address are the order application information entered by the logistics service provider in the order application interface. In the pickup interface, the logistics service provider is required to enter the pickup object information (i.e. fill in the pickup information), including but not limited to the package height, package quantity, package length, package width, weight, item type, payment method, and expiration type. Correspondingly, in order to help the logistics service provider find the correct filling location and fill in the correct information, Figure 7 In the corresponding column, prompt information is also displayed, such as: please enter the height (cm), please enter the number of packages, please enter the length (cm), please enter the width (cm), please enter the weight (kg), such as: documents, monthly payment, special delivery, etc. Figure 7 After the logistics service provider clicks the collection button, the open platform sends the collection information to the business interface corresponding to the collection information in the business system through the gateway, that is, Figure 5 In business interface 3, the business system generates collection and joint debugging results based on the collection information, and returns the collection and joint debugging results to the open platform through the gateway.
[0070] In the embodiment of the present application, the above Figure 5-Figure 7 The joint debugging tool shows the interaction between the open platform and the business system, including the forms, process navigation, and page styles displayed by each business node. It also shows the technical method of executing each business node to generate simulated data for system joint debugging.
[0071] In the embodiment of the present application, combined with the above Figure 6 and Figure 7 The order placement interface and the collection interface are shown respectively. After passing the previous business node (order placement process), you can enter the next business node (collection process). In the open platform business joint debugging interface, operate the corresponding button (see Figure 6 Click the Next button or Figure 7 The gateway forwards the request to the business system, and the business system returns the corresponding execution result. Finally, after receiving the request result, the gateway returns the result to the open platform, and the open platform makes a judgment based on the result.
[0072] In an embodiment of the present application, for the collection process, the collection object information is entered on the collection interface, the business interface is called through the gateway, and the collection joint debugging result is returned; if the collection joint debugging result is characterized by passing, the collection interface jumps to the transit interface. For the transit process, the transit information is entered on the transit interface, the business interface is called through the gateway, and the transit joint debugging result is returned; if the transit joint debugging result is characterized by passing, the transit interface jumps to the delivery interface. For the delivery process, the delivery information is entered on the delivery interface, the business interface is called through the gateway, and the delivery joint debugging result is returned. The delivery joint debugging result is the last business process joint debugging result. If the delivery joint debugging result is characterized by passing, the joint debugging process is completed. Merchants can operate each step of the business process on the open platform by themselves without actually placing an order, complete the sandbox joint debugging process, and improve the efficiency of logistics docking.
[0073] In some embodiments, the transit interface includes a shipping site interface and a receiving site interface, the transit information includes shipping site information and receiving site information, and the transit joint debugging result includes shipping site joint debugging result and receiving site joint debugging result. The sandbox joint debugging method also includes the following steps: receiving the shipping site information on the shipping site interface; sending the shipping site information to the business interface corresponding to the shipping site information in the business system through the gateway, and receiving the shipping site joint debugging result generated by the business system based on the shipping site information; if the shipping site joint debugging result indicates that it has passed, then the shipping site interface is transferred to the receiving site interface; receiving the receiving site information on the receiving site interface; sending the receiving site information to the business interface corresponding to the receiving site information in the business system through the gateway, and receiving the receiving site joint debugging result generated by the business system based on the receiving site information; if the receiving site joint debugging result indicates that it has passed, then the receiving site interface is transferred to the delivery interface.
[0074] In an embodiment of the present application, the transit process includes a shipping site process and a receiving site process. For the previous process of the shipping site process (i.e., the collection process), the collection object information is entered on the collection interface, the business interface is called through the gateway, and the collection joint debugging result is returned; if the collection joint debugging result indicates that it is passed, the collection interface jumps to the shipping site interface. For the shipping site process, the shipping site information is entered on the shipping site interface, the business interface is called through the gateway, and the shipping site joint debugging result is returned; if the shipping site joint debugging result indicates that it is passed, the shipping site interface jumps to the receiving site interface. For the receiving site process, the receiving site information is entered on the receiving site interface, the business interface is called through the gateway, and the receiving site joint debugging result is returned; if the receiving site joint debugging result indicates that it is passed, the receiving site interface jumps to the delivery interface.
[0075] In the embodiment of the present application, by adding the shipping site process and the receiving site process, the logistics flow process in the actual ordering process is simulated, thereby increasing the richness and completeness of the business process in the logistics distribution coordination task.
[0076] In some embodiments, the transfer interface also includes an originating transfer station interface and a destination transfer point interface, the transfer information also includes originating transfer station information and destination transfer station information, and the transfer joint debugging result also includes originating joint debugging result and destination joint debugging result. The sandbox joint debugging method also includes the following steps: if the shipping site joint debugging result is characterized as passed, then the shipping site interface is transferred to the originating transfer station interface; the originating transfer station information is received on the originating transfer station interface; the originating transfer station information is sent to the business interface corresponding to the originating transfer station information in the business system through the gateway, and the originating joint debugging result generated by the business system based on the originating transfer station information is received; if the originating joint debugging result is characterized as passed, then the originating transfer station interface is transferred to the destination transfer station interface; the destination transfer station information is received on the destination transfer station interface; the destination transfer station information is sent to the business interface corresponding to the destination transfer station information in the business system through the gateway, and the destination joint debugging result generated by the business system based on the destination transfer station information is received; if the destination joint debugging result is characterized as passed, then the destination transfer station interface is transferred to the receiving site interface.
[0077] In the embodiment of the present application, for cross-city logistics, not only the shipping site and the receiving site are needed, but also a large centralized transfer station (origin transfer station and destination transfer station) is needed to centrally allocate resources for remote logistics and improve resource utilization. The transfer process includes the originating sorting process and the destination sorting process. For the previous process of the originating sorting process (i.e., the shipping site process), the shipping site information is entered on the shipping site interface, the business interface is called through the gateway, and the shipping site joint debugging result is returned; if the shipping site joint debugging result is characterized by passing, the shipping site interface jumps to the originating transfer station interface. Enter the originating transfer station information on the originating transfer station interface, call the business interface through the gateway, and return the originating joint debugging result; if the originating joint debugging result is characterized by passing, the originating transfer station interface jumps to the destination transfer point interface. Enter the destination transfer point information on the destination transfer point interface, call the business interface through the gateway, and return the destination joint debugging result; if the destination joint debugging result is characterized by passing, the destination transfer point interface jumps to the receiving site interface.
[0078] In the embodiment of the present application, the logistics flow process in the actual ordering process is simulated through the originating sorting process and the destination sorting process, thereby increasing the richness and completeness of the business process in the logistics distribution coordination task.
[0079] In some embodiments, the delivery interface includes a delivery interface and a receipt interface, the delivery information includes delivery information and receipt information, and the delivery joint debugging result includes a delivery joint debugging result and a receipt joint debugging result; the delivery information is received on the delivery interface. The sandbox joint debugging method also includes the following steps: sending the delivery information to the business interface corresponding to the delivery information in the business system through the gateway, and receiving the delivery joint debugging result generated by the business system based on the delivery information; if the delivery joint debugging result indicates that it passes, the delivery interface is transferred to the receipt interface; receiving the receipt information on the receipt interface; sending the receipt information to the business interface corresponding to the receipt information in the business system through the gateway, and receiving the receipt joint debugging result generated by the business system based on the receipt information; wherein the receipt joint debugging result is the last business process joint debugging result.
[0080] In the embodiment of the present application, the delivery process includes a delivery process and a receipt process. For some designated logistics, collection can be performed and the goods can be delivered directly. For some ordinary logistics, a receipt link is also required to ensure the safety and timeliness of the package. For the previous process of the delivery process (i.e., the receiving site process), the receiving site information is entered on the receiving site interface, and the business interface is called through the gateway to return the receiving site joint debugging result; if the receiving site joint debugging result indicates that it has passed, the receiving site interface jumps to the delivery interface. For the delivery process, the delivery information is entered on the delivery interface, and the business interface is called through the gateway to return the delivery joint debugging result; if the delivery joint debugging result indicates that it has passed, the delivery interface jumps to the receipt interface. For the receipt process, the receipt information is entered on the receipt interface, and the business interface is called through the gateway to return the receipt joint debugging result. The receipt joint debugging result is the last business process joint debugging result. If the receipt joint debugging result indicates that it has passed, the joint debugging process is completed.
[0081] In the embodiment of the present application, the logistics flow process in the actual ordering process is simulated through the delivery process and the receipt process, thereby increasing the richness and completeness of the business process in the logistics distribution coordination task.
[0082] In some embodiments, the delivery interface also includes an inspection interface, the delivery information also includes inspection information, and the delivery joint debugging result also includes inspection joint debugging results. The sandbox joint debugging method also includes the following steps: if the transit joint debugging result indicates that it is passed, then the transit interface is transferred to the inspection interface; the inspection information is received on the inspection interface; the inspection information is sent to the business interface corresponding to the inspection information in the business system through the gateway, and the inspection joint debugging result generated by the business system based on the inspection information is received; if the inspection joint debugging result indicates that it is passed, then the inspection interface is transferred to the delivery interface.
[0083] In an embodiment of the present application, the delivery process also includes an inspection process, which is after the transit process and before the delivery process. For the previous process of the inspection process (the receiving site process in the transit process), the receiving site information is entered on the receiving site interface, and the business interface is called through the gateway to return the receiving site joint debugging result; if the receiving site joint debugging result indicates that it has passed, the receiving site interface jumps to the inspection interface. For the inspection process, the inspection information is entered on the inspection interface, and the business interface is called through the gateway to return the inspection joint debugging result; if the inspection joint debugging result indicates that it has passed, the inspection interface jumps to the delivery interface.
[0084] In the embodiment of the present application, the goods inspection process is used to simulate the logistics flow process in the actual order placement process, thereby increasing the richness and completeness of the business process in the logistics distribution coordination task.
[0085] In the embodiment of the present application, the above Figure 5 The sandbox joint debugging steps shown in the open platform can be found in Figure 8 As shown, Figure 8 An optional flow chart of a sandbox joint debugging process provided in an embodiment of the present application, Figure 8 The entire sandbox joint debugging steps are shown in Figure 1. Create a sandbox joint debugging task and replace appkey, appSecret, and token with sandbox environment parameters. Then, the logistics service provider can operate on the open platform interface. Figure 5 In the middle interface, we introduce the operation business process 1, operation business process 2, and operation business process n. In the local code, call the [Order] interface (corresponding to calling the order interface through the local development test interface); execute the [Courier-Collection] process on the platform interface and check the callback information (corresponding to Figure 5 The execution result returned in the platform verification step); execute the [site-shipping] process on the platform interface; execute the [sorting-receiving] process on the platform interface; execute the [sorting-shipping] process on the platform interface; execute the [courier-receiving] process on the platform interface; execute the [courier-delivery] process on the platform interface; execute the [courier-successful delivery] process on the platform interface; call the [logistics track query] interface in the local code (corresponding to calling the logistics track query interface through the local development test interface); joint debugging is completed. The above Figure 8 Taking the express delivery order process as an example, the merchant operation joint debugging tool process is as follows Figure 8 As shown in the figure, after completing all the steps, the business can be launched.
[0086] In some embodiments, after the above S103, the sandbox joint debugging process also includes S104-S106. Fig. 9 As shown, Fig. 9A flowchart of optional steps of another sandbox joint debugging method provided in an embodiment of the present application.
[0087] S104. When the last business process joint debugging result is characterized as passed, a logistics track query request is initiated to the gateway through the local development test interface, wherein the logistics track query request is used to call the logistics track query interface in the business system.
[0088] S105. Receive the logistics track query interface call result returned by the business system through the gateway.
[0089] S106. If the result of the logistics track query interface call is passed, each logistics track corresponding to each business process in the logistics distribution coordination task is displayed.
[0090] In an embodiment of the present application, when the last business process joint debugging result characterization passes, it indicates that all business process joint debugging processes are completed, and a logistics track query request can be initiated to the gateway through the local development test interface to call the logistics track query interface in the business system. The logistics track query interface is the interface called during the actual logistics track query. The business system generates a logistics track query interface call result based on the logistics track query request. When the logistics track query interface call result characterization passes, it indicates that the call is successful, and multiple logistics tracks corresponding to multiple business processes are displayed to the logistics service provider, and one business process corresponds to one logistics track.
[0091] In the embodiment of the present application, when executing each business process, the logistics service provider enters relevant information on each business interface, then clicks the next step, and outputs relevant information on the next business interface until the last business process ends. The logistics service provider cannot see the flow of multiple business processes at the same time. The open platform displays multiple logistics tracks in chronological order, allowing the logistics service provider to fully understand the flow of the entire business process, improving intuitiveness and visibility.
[0092] In the embodiment of the present application, the above Figure 5 For the operation of business process 1-business process n on the middle interface, please refer to Fig.10 As shown, Fig.10 An optional schematic diagram of a business node of another sandbox tool provided in an embodiment of the present application. Fig.10 The sandbox joint debugging tool shown in is a simulation tool that assists developers in interface development and joint debugging of major functions. It can simulate the business flow between its own system and the logistics system. After completing the joint debugging, please create a production environment application in [Development Management] and perform a complete functional acceptance test. Fig.10 The following shows an overview of the sandbox debugging in the development platform, based on the selected Figure 3The "Express B2C Order" in the courier is used to verify the process from express order placement to courier collection. The open platform interface displays development information (i.e. sandbox test application information) and business joint debugging, among which business joint debugging displays the business processes that have been executed. Fig.10 The figure shows the entire process of the logistics distribution coordination task, including sending (the merchant places an order and fills in the order application information), picking up (the courier picks up the goods at the door and the site receives the goods), sorting (including origin sorting and destination sorting), delivering (including site inspection and courier receipt), receiving (receiving the goods by the consumer) and querying the logistics track (completing n business processes). The entire business process is also configured with a timestamp for the convenience of merchants and consumers to view. In the sending process, the merchant fills in the order application information (including sender, shipping address, recipient, receiving address, etc.). In the picking up process, the merchant simulates the courier to pick up the goods at the door and enters the waybill number returned by the business system. Therefore, the logistics track query interface displays logistics information: Order number: ABXXX, delivery address: 12th Street, V Road, W City, recipient: Mr. C, and the corresponding logistics track is as follows: 1234 / 5 / 6 12:01:00 The goods have been delivered to the logistics; 1234 / 5 / 6 12:02:00 The collection task has been assigned to courier Li XX, contact number 12345678910; 1234 / 5 / 6 12:02:05 The courier has collected the express. The logistics track corresponding to the site collection in the collection process is as follows: 1234 / 5 / 6 12:02:08 Your express has been collected by [M Sales Department]; 1234 / 5 / 6 12:03:00 The courier driver received the box. The logistics track corresponding to the sorting process is as follows: 1234 / 5 / 6 12:03:07 Your express has arrived at [N sorting center]; 1234 / 5 / 6 12:03:50 Your express has been sorted at [N sorting center]. 1234 / 5 / 6 12:03:55 Your express is ready to be sent to [K sales department] from [N sorting center]; The logistics track corresponding to the site inspection in the delivery process is as follows: 1234 / 5 / 6 12:03:56 Your express has been received at [K sales department]; 1234 / 5 / 6 12:04:00 Your express has arrived at [K sales department]; The logistics track corresponding to the courier's receipt process is as follows: 1234 / 5 / 6 12:10:00 Your express is being delivered, please prepare to sign for it (courier: Li ××, contact number: 12345678910). The logistics track corresponding to the consumer's delivery process is as follows: 1234 / 5 / 6 12:20:00 Your express delivery has been collected by the doorman. Thank you for using logistics and we look forward to serving you again.
[0093] In the embodiment of the present application, each step of the operation will generate an information flow. When all business node processes are completed, the interface prompts that the joint debugging is completed and displays the interaction process between each process and the logistics system, as described above. Fig.10shown.
[0094] The sandbox joint debugging method provided in the embodiment of the present application separates the merchant joint debugging test from the production system operation process, and does not affect the actual operation of the site. Through the sandbox tool, merchants can independently verify the business process and complete the interface test without the need for the logistics system to cooperate and intervene, thereby improving the docking efficiency.
[0095] In order to implement the sandbox joint debugging method of the embodiment of the present application, the embodiment of the present application also provides a sandbox joint debugging device, such as Fig.11 As shown, Fig.11 An optional structural diagram of a sandbox joint debugging device provided for an embodiment of the present application, the sandbox joint debugging device 110 includes: a receiving module 1101, which is used to receive, in sequence, various operation information of various business processes for the logistics distribution joint debugging task based on the sandbox tool and the obtained test order number when the result of placing an order interface call is characterized as passed; a sending module 1102, which is used to send various operation information to various business interfaces corresponding to various business processes in the business system through the gateway in sequence; the receiving module 1101 is also used to receive various business process joint debugging results returned by the business system based on various operation information, until the last business process joint debugging result is characterized as passed, thereby completing the sandbox joint debugging process of the logistics distribution joint debugging task.
[0096] In some embodiments, the sandbox joint debugging device 110 further includes a display module 1103;
[0097] A display module 1103 is used to display sandbox test application information for replacing sandbox environment parameters based on the selected logistics distribution joint debugging task scenario in the sandbox tool;
[0098] The receiving module 1101 is further used to receive configuration parameters based on the sandbox test application information and order application information;
[0099] The sending module 1102 is further used to initiate an order request to the gateway through the local development test interface based on the configuration parameters and the order application information, wherein the order request is used to call the order interface in the business system;
[0100] The receiving module 1101 is also used to receive the order interface call result and the test order number returned by the business system through the gateway.
[0101] In some embodiments, the sandbox joint debugging device 110 further includes a calling module 1104;
[0102] The operation information includes current simulation information related to the current business process, and the business interface includes a current business interface corresponding to the current business process;
[0103] The receiving module 1101 is further used to receive current simulation information on the current business interface corresponding to the current business process;
[0104] The sending module 1102 is also used to send the current simulation information to the current business interface in the business system through the gateway;
[0105] The receiving module 1101 is also used to receive, through the gateway, the current business process joint debugging result generated by the business system based on the current simulation information; if the current business process joint debugging result indicates that it has passed, the current business interface is switched to the next business interface;
[0106] The calling module 1104 is used to continuously receive the next simulation information on the next business interface, and call the next business interface corresponding to the next business process in the business system through the gateway until the last business process joint debugging result representation is passed, completing the sandbox joint debugging process of the logistics distribution joint debugging task.
[0107] In some embodiments, the display module 1103 is further used to display the business error result on the current business interface if the current business process joint debugging result representation fails;
[0108] The receiving module 1101 is further used to re-receive the updated simulation information based on the business error result on the current business interface;
[0109] The sending module 1102 is also used to send the update simulation information to the current service interface through the gateway;
[0110] The receiving module 1101 is also used to receive the updated joint debugging results generated by the business system based on the updated simulation information through the gateway; if the updated joint debugging result representation fails, the new business error result is re-displayed on the current business interface, and the new simulation information is re-received until the joint debugging result representation passes, and the current business interface is switched to the next business interface.
[0111] In some embodiments, the sending module 1102 is further used to initiate a logistics track query request to the gateway through the local development test interface when the last business process joint debugging result representation passes, wherein the logistics track query request is used to call the logistics track query interface in the business system;
[0112] The receiving module 1101 is also used to receive the logistics track query interface call result returned by the business system through the gateway;
[0113] The display module 1103 is also used to display each logistics track corresponding to each business process in the logistics distribution coordination task if the logistics track query interface call result characterizes passing.
[0114] In some embodiments, the receiving module 1101 is further used to display an order placement interface based on the sandbox tool, and receive a waybill number based on the test order number on the order placement interface;
[0115] The sending module 1102 is further used to send the waybill number to the business interface corresponding to the waybill number in the business system through the gateway;
[0116] The receiving module 1101 is also used to receive the platform verification results returned by the business system; wherein the platform verification results include the validity verification results of the test order number and the consistency verification results between the waybill number and the test order number; if the platform verification results indicate a pass, then various operation information is received on various business interfaces corresponding to various business processes.
[0117] In some embodiments, the receiving module 1101 is further configured to switch from the order placement interface to the collection interface if the platform verification result indicates that the information is passed, and receive the collection object information on the collection interface;
[0118] The sending module 1102 is further used to send the collection object information to the business interface corresponding to the collection object information in the business system through the gateway, and receive the collection joint debugging result generated by the business system based on the collection object information;
[0119] The receiving module 1101 is also used to transfer from the collection interface to the transfer interface if the collection and joint debugging result is characterized as passed; and receive transfer information on the transfer interface;
[0120] The sending module 1102 is further used to send the transit information to the business interface corresponding to the transit information in the business system through the gateway, and receive the transit joint debugging result generated by the business system based on the transit information;
[0121] The receiving module 1101 is also used to transfer from the transfer interface to the delivery interface if the transfer joint debugging result is characterized as passed; and receive the delivery information on the delivery interface;
[0122] The sending module 1102 is further used to send the dispatch information to the business interface corresponding to the dispatch information in the business system through the gateway;
[0123] The receiving module 1101 is also used to receive the delivery joint debugging result generated by the business system based on the delivery information; wherein the delivery joint debugging result is the last business process joint debugging result.
[0124] In some embodiments, the transit interface includes a shipping site interface and a receiving site interface, the transit information includes shipping site information and receiving site information, and the transit joint debugging result includes a shipping site joint debugging result and a receiving site joint debugging result;
[0125] The receiving module 1101 is further used to receive the shipping site information on the shipping site interface;
[0126] The sending module 1102 is further used to send the shipping site information to the business interface corresponding to the shipping site information in the business system through the gateway;
[0127] The receiving module 1101 is also used to receive the shipping site joint debugging result generated by the business system based on the shipping site information; if the shipping site joint debugging result indicates that it is passed, the shipping site interface is switched to the receiving site interface; and the receiving site information is received on the receiving site interface;
[0128] The sending module 1102 is further used to send the delivery site information to the business interface corresponding to the delivery site information in the business system through the gateway;
[0129] The receiving module 1101 is also used to receive the receiving site joint debugging result generated by the business system based on the receiving site information; if the receiving site joint debugging result indicates that it has passed, the receiving site interface is switched to the delivery interface.
[0130] In some embodiments, the transfer interface further includes an originating transfer station interface and a destination transfer point interface, the transfer information further includes originating transfer station information and destination transfer station information, and the transfer joint debugging result further includes an originating joint debugging result and a destination joint debugging result;
[0131] The receiving module 1101 is also used to switch from the shipping site interface to the originating transfer station interface if the shipping site joint debugging result is characterized as passed; and receive the originating transfer station information on the originating transfer station interface;
[0132] The sending module 1102 is further used to send the originating transfer station information to the service interface corresponding to the originating transfer station information in the service system through the gateway;
[0133] The receiving module 1101 is also used to receive the origination joint debugging result generated by the business system based on the origination transfer station information; if the origination joint debugging result indicates that it is passed, the origination transfer station interface is transferred to the destination transfer station interface; and the destination transfer station information is received on the destination transfer station interface;
[0134] The sending module 1102 is further used to send the destination transfer station information to the service interface corresponding to the destination transfer station information in the service system through the gateway;
[0135] The receiving module 1101 is also used to receive the destination joint debugging result generated by the business system based on the destination transfer station information; if the destination joint debugging result indicates that it is passed, the destination transfer station interface is transferred to the receiving site interface.
[0136] In some embodiments, the delivery interface includes a delivery interface and a receipt interface, the delivery information includes delivery information and receipt information, and the delivery joint debugging result includes a delivery joint debugging result and a receipt joint debugging result;
[0137] The receiving module 1101 is also used to receive the delivery information on the delivery interface;
[0138] The sending module 1102 is further used to send the delivery information to the business interface corresponding to the delivery information in the business system through the gateway;
[0139] The receiving module 1101 is also used to receive the delivery joint debugging result generated by the business system based on the delivery information; if the delivery joint debugging result indicates that it is passed, the delivery interface is switched to the receipt interface; and the receipt information is received on the receipt interface;
[0140] The sending module 1102 is further used to send the receipt information to the business interface corresponding to the receipt information in the business system through the gateway;
[0141] The receiving module 1101 is also used to receive the sign-off joint debugging result generated by the business system based on the sign-off information; wherein the sign-off joint debugging result is the last business process joint debugging result.
[0142] In some embodiments, the delivery interface further includes an inspection interface, the delivery information further includes inspection information, and the delivery joint debugging result further includes inspection joint debugging result;
[0143] The receiving module 1101 is also used to switch from the transfer interface to the goods inspection interface if the transfer joint debugging result is characterized as passed; and receive the goods inspection information on the goods inspection interface;
[0144] The sending module 1102 is further used to send the inspection information to the business interface corresponding to the inspection information in the business system through the gateway;
[0145] The receiving module 1101 is also used to receive the inspection and joint debugging result generated by the business system based on the inspection information; if the inspection and joint debugging result indicates that it is passed, the inspection interface is switched to the delivery interface.
[0146] It should be noted that the sandbox joint debugging device provided in the above embodiment only uses the division of the above-mentioned program modules as an example when performing sandbox joint debugging. In actual applications, the above-mentioned processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above. In addition, the sandbox joint debugging device provided in the above embodiment belongs to the same concept as the sandbox joint debugging method embodiment. Its specific implementation process and beneficial effects are detailed in the method embodiment, which will not be repeated here. For technical details not disclosed in the embodiment of this device, please refer to the description of the method embodiment of this application for understanding.
[0147] In the embodiments of the present application, Fig.12 The schematic diagram of the structure of the sandbox joint debugging device proposed in the embodiment of the present application is as follows: Fig.12As shown, the sandbox joint debugging device 120 proposed in the embodiment of the present application includes a processor 1201 and a memory 1202 for storing an executable computer program. The processor 1201 is used to implement the sandbox joint debugging method provided in the embodiment of the present application when executing the executable computer program stored in the memory 1202.
[0148] In some embodiments, the sandbox debugging device 120 may further include a communication interface 1203 and a bus 1204 for connecting the processor 1201 , the memory 1202 and the communication interface 1203 .
[0149] In the embodiment of the present application, the processor 1201 may be at least one of an application-specific integrated circuit (ASIC), a digital signal processor (DSP), a digital signal processing device (DSPD), a programmable logic device (PLD), a field programmable gate array (FPGA), a central processing unit (CPU), a controller, a microcontroller, and a microprocessor. It is understandable that for different devices, the electronic device used to implement the above-mentioned processor function may also be other, and the embodiment of the present application does not specifically limit it.
[0150] In the embodiment of the present application, the bus 1204 is used to connect the communication interface 1203, the processor 1201 and the memory 1202 to achieve mutual communication between these devices.
[0151] The memory 1202 is used to store executable computer programs and data. The executable computer program includes computer operation instructions. The memory 1202 may include a high-speed RAM memory, and may also include a non-volatile memory, for example, at least two disk memories. In practical applications, the memory 1202 may be a volatile memory (volatile memory), such as a random access memory (Random-Access Memory, RAM); or a non-volatile memory (non-volatile memory), such as a read-only memory (Read-Only Memory, ROM), a flash memory (flash memory), a hard disk (Hard Disk Drive, HDD) or a solid-state drive (Solid-State Drive, SSD); or a combination of the above types of memory, and provide the processor 1201 with executable computer programs and data.
[0152] In addition, each functional module in this embodiment can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or software functional modules.
[0153] If the integrated unit is implemented in the form of a software function module and is not sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this embodiment is essentially or the part that contributes to the prior art or the whole or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the method of this embodiment. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc., various media that can store program codes.
[0154] An embodiment of the present application provides a computer-readable storage medium storing a computer program for implementing the sandbox joint debugging method as described in any of the above embodiments when executed by a processor.
[0155] Exemplarily, a program instruction corresponding to a sandbox debugging method in this embodiment can be stored on a storage medium such as a CD, a hard disk, or a USB flash drive. When the program instruction corresponding to a sandbox debugging method in the storage medium is read or executed by an electronic device, the sandbox debugging method described in any of the above embodiments can be implemented.
[0156] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of hardware embodiments, software embodiments, or embodiments in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.
[0157] The present application is described with reference to implementation flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the process in the flowchart. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0158] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which is implemented in the implementation flow diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0159] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operation steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing the steps in the flowchart. Figure 1 A process or multiple processes and / or boxes Figure 1 The above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application.
Claims
1. A sandbox joint debugging method, It is characterized in that The method comprises: When the result of the order interface call is passed, based on the sandbox tool and the obtained test order number, each operation information of each business process for the logistics distribution joint debugging task is received in sequence; Sending each operation information to each business interface corresponding to each business process in the business system through the gateway in turn; Receive the business process joint debugging results returned by the business system based on the various operation information until the last business process joint debugging result is represented as passed, thereby completing the sandbox joint debugging process of the logistics distribution joint debugging task.
2. The method according to claim 1, It is characterized in that The method further comprises: Based on the selected logistics distribution joint debugging task scenario in the sandbox tool, display the sandbox test application information used to replace the sandbox environment parameters; Receiving configuration parameters based on the sandbox test application information and order application information; Based on the configuration parameters and the order application information, an order request is initiated to the gateway through a local development test interface, wherein the order request is used to call an order interface in the business system; The order interface call result and the test order number returned by the business system are received through the gateway.
3. The method according to claim 1, It is characterized in that The operation information includes current simulation information related to the current business process, and the business interface includes a current business interface corresponding to the current business process; The step of sending each operation information to each business interface corresponding to each business process in the business system through the gateway in turn; receiving each business process joint debugging result returned by the business system based on each operation information, until the last business process joint debugging result representation is passed, and completing the sandbox joint debugging process of the logistics distribution joint debugging task, includes: Receiving the current simulation information on a current business interface corresponding to the current business process; Sending the current simulation information to the current service interface in the service system through the gateway; Receiving, through the gateway, a current business process joint debugging result generated by the business system based on the current simulation information; If the current business process joint debugging result indicates that it has passed, the current business interface is switched to the next business interface; Continue to receive the next simulation information on the next business interface, and call the next business interface corresponding to the next business process in the business system through the gateway until the last business process joint debugging result representation is passed, completing the sandbox joint debugging process of the logistics distribution joint debugging task.
4. The method according to claim 3, It is characterized in that The method further comprises: If the current business process joint debugging result representation fails, the business error result is displayed on the current business interface; Re-receiving updated simulation information based on the business error result on the current business interface; Sending the updated simulation information to the current service interface through the gateway; Receiving, through the gateway, an update joint debugging result generated by the business system based on the update simulation information; If the update joint debugging result characterization fails, the new business error result is displayed again on the current business interface, and new simulation information is received again until the joint debugging result characterization passes, and the current business interface is switched to the next business interface.
5. The method according to any one of claims 1 to 4, It is characterized in that The method further comprises: When the last business process joint debugging result is characterized as passed, a logistics track query request is initiated to the gateway through the local development test interface, wherein the logistics track query request is used to call the logistics track query interface in the business system; Receiving the logistics track query interface call result returned by the business system through the gateway; If the result of calling the logistics track query interface is passed, the logistics tracks corresponding to the business processes in the logistics distribution coordination task are displayed.
6. The method according to any one of claims 1 to 4, It is characterized in that Based on the sandbox tool and the obtained test order number, each operation information of each business process for the logistics distribution joint debugging task is received in sequence, including: Displaying an order placement interface based on the sandbox tool, and receiving a waybill number based on the test order number on the order placement interface; Sending the waybill number to the business interface corresponding to the waybill number in the business system through the gateway, and receiving the platform verification result returned by the business system; wherein the platform verification result includes the validity verification result of the test waybill number and the consistency verification result between the waybill number and the test waybill number; If the platform verification result indicates passing, each operation information is received on each business interface corresponding to each business process.
7. The method according to claim 6, It is characterized in that If the platform verification result characterizes passing, receiving each operation information on each business interface corresponding to each business process includes: If the platform verification result indicates that the order is passed, the order placement interface is switched to the collection interface, and the collection object information is received on the collection interface; The step of sending each operation information to each business interface corresponding to each business process in the business system through the gateway in sequence; and receiving each business process joint debugging result returned by the business system based on each operation information includes: Sending the collection object information to the business interface corresponding to the collection object information in the business system through the gateway, and receiving the collection joint debugging result generated by the business system based on the collection object information; If the collection and joint debugging result is characterized as passed, the collection interface is transferred to the transfer interface; the transfer information is received on the transfer interface; the transfer information is sent to the business interface corresponding to the transfer information in the business system through the gateway, and the transfer joint debugging result generated by the business system based on the transfer information is received; If the transfer joint debugging result is characterized as passed, the transfer interface is transferred to the dispatch interface; the dispatch information is received on the dispatch interface; the dispatch information is sent to the business interface corresponding to the dispatch information in the business system through the gateway, and the dispatch joint debugging result generated by the business system based on the dispatch information is received; wherein, the dispatch joint debugging result is the last business process joint debugging result.
8. The method according to claim 7, It is characterized in that The transfer interface includes a shipping site interface and a receiving site interface, the transfer information includes shipping site information and receiving site information, and the transfer joint debugging result includes a shipping site joint debugging result and a receiving site joint debugging result; receiving transfer information on the transfer interface; Sending the transit information to the business interface corresponding to the transit information in the business system through the gateway, and receiving the transit joint debugging result generated by the business system based on the transit information; If the transfer joint debugging result is passed, the transfer interface is transferred to the delivery interface, including: receiving the shipping site information on the shipping site interface; sending the shipping site information to the business interface corresponding to the shipping site information in the business system through the gateway, and receiving the shipping site joint debugging result generated by the business system based on the shipping site information; If the shipping site joint debugging result is characterized as passed, the shipping site interface is switched to the receiving site interface; the receiving site information is received on the receiving site interface; the receiving site information is sent to the business interface corresponding to the receiving site information in the business system through the gateway, and the receiving site joint debugging result generated by the business system based on the receiving site information is received; If the joint debugging result of the receiving site is characterized as passed, the receiving site interface is switched to the delivery interface.
9. The method according to claim 8, It is characterized in that The transfer interface also includes an originating transfer station interface and a destination transfer point interface, the transfer information also includes originating transfer station information and destination transfer station information, and the transfer joint debugging result also includes an originating joint debugging result and a destination joint debugging result; The method further comprises: If the shipping site joint debugging result is characterized as passed, the shipping site interface is switched to the originating transfer station interface; the originating transfer station information is received on the originating transfer station interface; the originating transfer station information is sent to the business interface corresponding to the originating transfer station information in the business system through the gateway, and the originating joint debugging result generated by the business system based on the originating transfer station information is received; If the originating joint debugging result is characterized as passed, the originating transfer station interface is switched to the destination transfer station interface; the destination transfer station information is received on the destination transfer station interface; the destination transfer station information is sent to the business interface corresponding to the destination transfer station information in the business system through the gateway, and the destination joint debugging result generated by the business system based on the destination transfer station information is received; If the target joint debugging result is characterized as passed, the interface of the target transfer station is switched to the interface of the receiving station.
10. The method according to any one of claims 7 to 9, It is characterized in that The delivery interface includes a delivery interface and a receipt interface, the delivery information includes delivery information and receipt information, and the delivery joint debugging result includes a delivery joint debugging result and a receipt joint debugging result; receiving delivery information on the delivery interface; Sending the delivery information to a business interface corresponding to the delivery information in the business system through the gateway, and receiving a delivery joint debugging result generated by the business system based on the delivery information, including: receiving the delivery information on the delivery interface; sending the delivery information to the business interface corresponding to the delivery information in the business system through the gateway, and receiving the delivery coordination result generated by the business system based on the delivery information; If the delivery joint debugging result is characterized as passed, the delivery interface is switched to the receipt interface; the receipt information is received on the receipt interface; the receipt information is sent to the business interface corresponding to the receipt information in the business system through the gateway, and the receipt joint debugging result generated by the business system based on the receipt information is received; wherein, the receipt joint debugging result is the last business process joint debugging result.
11. The method according to claim 10, It is characterized in that The delivery interface also includes a goods inspection interface, the delivery information also includes goods inspection information, and the delivery joint debugging result also includes goods inspection joint debugging results; The method further comprises: If the transfer joint debugging result is characterized as passed, the transfer interface is transferred to the inspection interface; the inspection information is received on the inspection interface; the inspection information is sent to the business interface corresponding to the inspection information in the business system through the gateway, and the inspection joint debugging result generated by the business system based on the inspection information is received; If the inspection result is passed, the interface switches from the inspection interface to the delivery interface.
12. A sandbox joint debugging device, It is characterized in that The device comprises: The receiving module is used to receive the operation information of each business process for the logistics distribution joint debugging task in sequence based on the sandbox tool and the obtained test order number when the result of the order interface call is passed; A sending module, used to send various operation information to various business interfaces corresponding to the various business processes in the business system in sequence through the gateway; The receiving module is also used to receive each business process joint debugging result returned by the business system based on the each operation information, until the last business process joint debugging result representation is passed, thereby completing the sandbox joint debugging process of the logistics distribution joint debugging task.
13. A sandbox joint debugging device, It is characterized in that The device comprises: a memory for storing executable computer programs; A processor, configured to implement the method according to any one of claims 1 to 11 when executing the executable computer program stored in the memory.
14. A computer-readable storage medium, It is characterized in that A computer program is stored, which is used to implement the method described in any one of claims 1 to 11 when executed by a processor.
