CN107203471B

CN107203471B - Joint debugging method, service platform and computer storage medium

Info

Publication number: CN107203471B
Application number: CN201710374716.1A
Authority: CN
Inventors: 王寸涛; 吴建国
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2017-05-24
Filing date: 2017-05-24
Publication date: 2023-03-24
Anticipated expiration: 2037-05-24
Also published as: CN107203471A

Abstract

The embodiment of the invention discloses a joint debugging method, a service platform and a computer storage medium, wherein the joint debugging method comprises the following steps: initializing a joint debugging environment based on the joint debugging parameters; the joint debugging environment creates a joint debugging task and a joint debugging case under the joint debugging task according to task parameters; based on the joint debugging parameters, indicating to execute the joint debugging case and acquiring an execution result of the joint debugging case; sending execution data to an application terminal based on the joint debugging parameters and the execution result of the joint debugging case; receiving feedback data returned by the application terminal based on the execution data; and determining the execution result of the joint debugging task based on the feedback data.

Description

Joint debugging method, service platform and computer storage medium

Technical Field

The present invention relates to the field of information technologies, and in particular, to a joint debugging method, a service platform, and a computer storage medium.

Background

With the development of information technology, various service platforms have been formed on the internet. When one service platform builds an application environment for a certain application end, the service platform is manually executed or triggered by an operator in the process of building or verifying the application environment, and the application end is required to generate information interaction of various joint debugging cases in the process of building or verifying the application environment. In the prior art, execution data generated in the process of application environment construction or verification is downloaded from a platform side by an operator and then sent to an application terminal for confirmation in a mode of mail, offline or the like. The interaction between the verification mode of the application environment and the verification information has the problems of low efficiency, slow feedback, large time delay and the like on one hand; on the other hand, the human error rate is high, the self equipment resources of the service platform cannot be fully utilized, and the idle rate of the resources is high.

Disclosure of Invention

In view of this, embodiments of the present invention are intended to provide a joint debugging method and a computer storage medium of a service platform, which are used to solve at least one of the problems of low joint debugging efficiency, high human error rate and high resource idle rate in the prior art.

In order to achieve the purpose, the technical scheme of the invention is realized as follows:

a first aspect of an embodiment of the present invention provides a joint debugging method, including:

initializing a joint debugging environment based on the joint debugging parameters;

the joint debugging environment creates a joint debugging task and a joint debugging case under the joint debugging task according to task parameters;

based on the joint debugging parameters, indicating to execute the joint debugging case and acquiring an execution result of the joint debugging case;

sending execution data to an application terminal based on the joint debugging parameters and the execution result of the joint debugging case;

receiving feedback data returned by the application terminal based on the execution data;

and determining the execution result of the joint debugging task based on the feedback data.

Based on the above scheme, the joint debugging parameters include: a resource configuration parameter;

initializing a joint debugging environment based on joint debugging parameters, comprising:

and performing joint debugging resource allocation and operation state setting of the joint debugging resources according to the resource allocation parameters.

Based on the above solution, the performing the joint debugging resource configuration and the setting of the running state of the joint debugging resource according to the resource configuration parameter includes:

determining whether the target equipment pointed by the resource configuration parameters is available according to the resource configuration parameters;

when the target equipment is available, setting equipment parameters of the target equipment according to the resource configuration parameters; wherein the target device comprises: at least one of a front-end device interacting with the application end, a platform device executing application logic, a file system device recording service execution information and a feedback processing system device processing the feedback data;

and forming resource configuration alarm information when the target equipment part is unavailable.

Based on the above scheme, the joint debugging parameters further include: the method comprises the following steps of case data template and joint debugging case parameters, wherein the joint debugging case parameters comprise: at least two different types of cases of the same service;

the method further comprises the following steps:

instantiating the case data template according to the joint debugging case parameters in the joint debugging parameters and the current state of the joint debugging case to generate joint debugging case data;

the executing the joint debugging case and forming an execution result based on the joint debugging parameters and the current state of the joint debugging case comprises:

and executing the joint debugging case and acquiring an execution result based on the joint debugging case data.

Based on the above scheme, instantiating the case data template according to the joint debugging case parameters in the joint debugging parameters and the current state of the joint debugging case, and generating joint debugging case data, including:

reading the joint debugging case parameters;

loading simulation user parameters;

loading the case data template;

and filling the case data template to form the joint debugging case data based on the simulated user parameters and the joint debugging case parameters.

Based on the above scheme, the executing the joint debugging case and obtaining the execution result based on the joint debugging case data includes:

analyzing the joint debugging case data to form an execution instruction, wherein the execution instruction comprises: the execution parameters of the joint debugging case are used for triggering the target equipment to execute the corresponding application logic;

sending the execution instruction to the target device;

receiving feedback information returned by the target equipment;

and determining the execution result of the joint debugging case based on the feedback information.

Based on the above scheme, the determining the execution result of the joint debugging task based on the feedback data includes:

processing the feedback data;

and determining the execution result of the joint debugging task based on the processing result of the feedback data.

Based on the above scheme, the method further comprises:

starting the display equipment; the initializing the joint debugging environment based on the joint debugging parameters further comprises:

starting the display equipment; wherein, the display device is configured to display the joint tone related information, wherein the joint tone related information includes: joint debugging process information, joint debugging case execution condition information, information interaction condition information with an application terminal, and processing condition information of feedback data.

A second aspect of an embodiment of the present invention provides a service platform, including:

the initialization unit is used for initializing the joint debugging environment based on the joint debugging parameters;

the creating unit is used for creating a joint debugging task and creating a joint debugging case under the joint debugging task according to the task parameters in the joint debugging environment;

the execution unit is used for indicating to execute the joint debugging case and acquiring an execution result of the joint debugging case based on the joint debugging parameters;

the communication unit is used for sending execution data to an application terminal based on the joint debugging parameters and the execution result of the joint debugging case; receiving feedback data returned by the application terminal based on the execution data;

and the determining unit is used for determining the execution result of the joint debugging task based on the feedback data.

the initialization unit is specifically configured to perform joint debugging resource configuration and operation state setting of joint debugging resources according to the resource configuration parameters.

Based on the above scheme, the initialization unit is specifically configured to determine, according to the resource configuration parameter, whether a target device pointed by the resource configuration parameter is available; when the target equipment is available, setting equipment parameters of the target equipment according to the resource configuration parameters; wherein the target device comprises: at least one of a front-end device interacting with the application end, a platform device executing application logic, a file system device recording service execution information and a feedback processing system device processing the feedback data; and forming resource configuration alarm information when the target equipment part is unavailable.

Based on the above scheme, the joint debugging parameters further include: case data templates and joint debugging case parameters, wherein the joint debugging case parameters comprise: at least two different types of cases of the same service;

the service platform further comprises:

the instantiation unit is used for instantiating the case data template according to the joint debugging case parameters in the joint debugging parameters and the current state of the joint debugging case to generate joint debugging case data;

the execution unit is specifically configured to execute the joint debugging case and obtain an execution result based on the joint debugging case data.

Based on the scheme, the instantiation unit is specifically used for reading the joint debugging case parameters; loading simulation user parameters; loading the case data template; and filling the case data template to form the joint debugging case data based on the simulation user parameters and the joint debugging case parameters.

Based on the above scheme, the execution unit is specifically configured to analyze the joint debugging case data to form an execution instruction, where the execution instruction includes: the execution parameters of the joint debugging case are used for triggering the target equipment to execute the corresponding application logic; sending the execution instruction to the target device; receiving feedback information returned by the target equipment; and determining the execution result of the joint debugging case based on the feedback information.

Based on the above scheme, the determining unit is specifically configured to process the feedback data; and determining the execution result of the joint debugging task based on the processing result of the feedback data.

Based on the above scheme, the initialization unit is further configured to start the display device; wherein, the display device is configured to display the joint tone related information, wherein the joint tone related information includes: joint debugging process information, joint debugging case execution condition information, information interaction condition information with an application terminal, and processing condition information of feedback data.

The third aspect of the embodiments of the present invention further provides a computer storage medium, where a computer executable code is stored in the computer storage medium, and after the computer executable code is executed by a processor, the joint debugging method provided in any one of the foregoing technical solutions can be implemented.

According to the joint debugging method, the service platform and the computer storage medium provided by the embodiment of the invention, when joint debugging parameters are obtained, a joint debugging environment is automatically initialized, a joint debugging task is configured based on task parameters, joint debugging cases to be executed next to the joint debugging task are created, and target equipment is triggered to execute the execution result of the corresponding joint debugging cases; and the execution data is automatically sent to the application terminal based on the execution result, and feedback data returned by the application terminal based on the execution data is received. On one hand, the service environment for providing services for the application end construction by the joint debugging environment is realized through the joint debugging parameters, the correctness and the feasibility of the constructed service environment are automatically tested through the joint debugging task, and meanwhile, the information interaction can be automatically carried out with the client. Obviously, the joint debugging method has high automation and efficiency, the artificial participation degree is low, the artificial error rate is low, and the effective utilization rate of resources of the service platform is improved.

Drawings

Fig. 1 is a schematic flow chart of a first joint debugging method according to an embodiment of the present invention;

fig. 2 is a schematic flow chart of a second joint debugging method according to an embodiment of the present invention;

fig. 3 is a schematic flow chart of executing a joint debugging case according to an embodiment of the present invention;

fig. 4 is a schematic structural diagram of a service platform according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of another service platform according to an embodiment of the present invention;

fig. 6 is a schematic flowchart of an initialization joint debugging environment according to an embodiment of the present invention;

fig. 7 is a schematic state transition diagram of a joint debugging case according to an embodiment of the present invention;

fig. 8 is a schematic flow chart of generation of joint-case data according to an embodiment of the present invention;

fig. 9 is a schematic flowchart of another execution of the joint debugging case according to the embodiment of the present invention;

fig. 10 is a schematic structural diagram of a joint debugging system according to an embodiment of the present invention;

fig. 11 is a flowchart illustrating a third linkage method according to an embodiment of the present invention.

Detailed Description

The technical solution of the present invention is further described in detail with reference to the drawings and the specific embodiments of the specification.

As shown in fig. 1, an embodiment of the present invention provides a joint debugging method, including:

step S110: initializing a joint debugging environment based on the joint debugging parameters;

step S120: the joint debugging environment creates a joint debugging task and a joint debugging case under the joint debugging task according to task parameters;

step S130: based on the joint debugging parameters, indicating to execute a joint debugging case and acquiring an execution result of the joint debugging case;

step S140: sending execution data to an application terminal based on the joint debugging parameters and the execution result of the joint debugging case;

step S150: receiving feedback data returned by the application terminal based on the execution data;

step S160: and determining the execution result of the joint debugging task based on the feedback data.

The joint debugging method provided by the embodiment can be applied to an application platform for providing an application environment for an application terminal. The application environment in this embodiment includes: hardware resources of the application and software resources of the operation are provided.

In the embodiment, the service platform is used for realizing the construction of an automatic application environment in the process of constructing the application environment and interacting with relevant information of a task execution result in the process of automatically interacting the application environment with an application terminal. Various information required in the joint debugging process is configured as joint debugging parameters in the present embodiment. Typically the joint key parameters may be written to a joint key file.

In this embodiment, a connection is established between the service platform and the application terminal, and the connection can be used at least for performing interaction between the execution data and the feedback data, so as to implement joint debugging of the built joint debugging environment.

In this embodiment, before performing step S110, the service platform may acquire the joint debugging parameter from a human-machine interaction interface, or receive the joint debugging parameter from other electronic devices from a communication interface, for example, receive the joint debugging parameter from an application server of an application end. After the joint debugging parameters are obtained, initializing a joint debugging environment, wherein the initializing joint debugging environment comprises the butt joint with the built service environment, or the building of the service environment is carried out based on the joint debugging parameters and then the butt joint with the built service environment is carried out.

In step S120, task parameters are obtained, and generally, a joint debugging task may include: one or more operations; each operation may correspond to a joint debugging case. For example, where the application side is a provider side of a financial product, operations related to the financial product may include: opening an account, making a purchase of a financial product, and redeeming a financial product, among others. Here, the opening, purchase and redemption can be separated into many sub-operations. An account opening, subscription or redemption operation that a user may use in purchasing a financial product. In this embodiment, the joint debugging task may perform single debugging and verification of the application environment in one operation in the service platform, or perform cooperative debugging and verification based on multiple operations.

In this embodiment, in step S120, task parameters are first obtained, where the task parameters may be received from a human-computer interaction interface of the service platform, and the task parameters are also received from a communication interface and sent by other devices. The task parameters here are: the method can comprise the starting and ending time of the joint debugging task, the service pointed by the joint debugging task, the joint debugging operation required by each service in the joint debugging task and the like. The services may be different types of financial products, or internet application products, etc. Such as vehicle sharing products, etc. For financial products, joint debugging operations may include: one or more of the opening, subscription, and redemption described above. Other internet application products may include: account registration, application, account logout, and the like.

In this embodiment, a task instance is created based on task parameters, and after the task instance is created, the joint debugging environment responsible for joint debugging at this time in the service platform is required to execute the joint debugging task. After the task instance is created, one or more joint debugging cases are created according to the task parameters in the task parameters. All the joint debugging cases belong to the joint debugging task, and task identifiers of the joint debugging task are configured in the attributes of the joint debugging cases.

After the joint debugging case is generated, the joint debugging case is executed according to the joint debugging parameters, and an execution result of the joint debugging case is obtained. After the service platform is built, application logic or service logic for providing various applications or services is loaded. The application logic and the service logic may be embodied by application code or service code provided by an application terminal. In the execution process of the joint debugging case in this embodiment, the analog data is mainly used to trigger the corresponding device to execute the corresponding application logic or service logic, so as to obtain the execution result of each application logic or service logic, thereby verifying whether the application environment is successfully built or whether the service requirement of the application terminal is met. The application environment may be a part of the joint debugging environment, and if the joint debugging passes, the application environment built in the joint debugging environment may be directly used for online use of subsequent applications.

After the execution of the joint debugging case is completed, the service platform obtains the corresponding execution result of the joint debugging case. The execution result of the joint debugging case needs to be sent to the application end for confirmation. In this embodiment, the joint debugging parameters describe various parameters to be sent to the application, so in step S140, execution data is sent to the application based on the joint debugging parameters and the joint debugging case execution result. In this embodiment, the executing data may directly include: and executing the result and/or executing data by each joint debugging case for the application end to inquire. For example, the joint debugging parameters may include: and the interactive interface of the application end sends the execution data to the application end through the specific interactive interface in step S140. The interactive interface may be information of an application terminal such as a specific network protocol (IP) address, a mailbox address, and/or an application interface of a joint debugging page. After the execution data is returned to the application end due to the joint debugging, the feedback data of the application end needs to be obtained. After receiving the feedback data, a final joint debugging task execution result can be determined. For example, if the feedback data indicates that the joint debugging case is executed incorrectly, the joint debugging task fails, and joint debugging parameters and/or software and hardware parameters of the application environment need to be modified again.

According to the joint debugging method provided by the embodiment, after the service platform acquires the joint debugging parameters and the task parameters, the joint debugging can be automatically executed, the acting personnel only need to import the two parameters into the service platform, the service platform can automatically execute the joint debugging and perform information interaction with the application, the acting personnel do not need to manually operate each joint debugging, the acting personnel and the application end perform data interaction through mails and the like, the joint debugging efficiency is greatly improved, human errors are reduced, software and hardware resources of the application platform are better utilized, and the effective utilization rate of resources is improved.

Optionally, the joint debugging parameters include: a resource configuration parameter;

the step S110 may include:

In this embodiment, the resource allocation parameter may be used to configure resources for joint debugging, and these joint debugging resources may include: the various resources of the application environment built for the application end may include computing resources and/or storage resources. The computing resources may include: one or more servers executing various application logic. The storage resources may include: one or more databases storing data generated by application services provided by the application side.

In this embodiment, joint debugging resources are scheduled for building an application environment according to the resource configuration parameters, and the running state configuration of the joint debugging resources is performed in parallel according to the resource configuration parameters. The scheduling of the joint debugging resources may include:

and configuring corresponding resource computing resource lines and/or storage resources into an occupied state in a resource management system, and writing the corresponding attribute of the joint debugging resource into a building identifier of the application environment and the like. The configuration of the operating state may include: controlling whether the joint debugging resources are in an opening state, configuring the states of all interfaces of the joint debugging resources and the like.

In a word, according to the resource configuration parameters, the construction of the application environment can be completed through joint debugging of resource configuration and operation state setting. In this embodiment, the service platform may implement automation of the application environment establishment through setting of resource management parameters and sending of corresponding configuration parameters in the resource management system. The application environment is built as part of initialization of the joint debugging environment.

Optionally, the step S110 may include:

determining whether the target equipment pointed by the resource configuration parameter is available according to the resource configuration parameter;

The resource configuration parameters carry device identifiers of various target devices participating in the joint debugging, for example, IP addresses and/or port addresses of the target devices, and in this embodiment, the service platform may perform information interaction with the target devices according to the device representations, so as to query whether the corresponding target devices are in an idle state, and whether the corresponding target devices can participate in the construction of the application environment and/or the construction of the joint debugging environment.

In this embodiment, if it is detected that the target device is available, the device parameter of the target device is set according to the resource configuration parameter, so as to occupy the target device and control the operating state of the target device. In some embodiments, if the target device is occupied, the target device may not be used to build an application environment and perform joint debugging, and then resource configuration alarm information may be returned.

In some embodiments, if the resource configuration alarm information is detected, it may be determined that the target device is unavailable by analyzing the resource configuration alarm information, and it is further determined whether a substitute device or a backup device of the target device is available, if so, the substitute device or the backup device of the target device participates in the joint debugging, and sends the corresponding resource configuration parameter to the substitute device or the target device, so as to complete initialization of the joint debugging environment, and if the substitute device or the backup device is still unavailable, the resource configuration alarm information is output through a human-computer interaction interface or output to a device designated by the actor, so as to prompt the actor to readjust the joint debugging parameter.

After the initialization of the joint debugging environment is completed, joint debugging cases need to be created according to the task parameters, and one or more joint debugging cases are executed under one joint debugging task.

The joint debugging parameters further comprise: case data templates and joint debugging case parameters, wherein the joint debugging case parameters comprise: at least two different types of cases of the same service. The joint tone data template here can be understood as: blank data structure for joint debugging case. The joint debugging case parameters may include: specific parameters for instantiating the blank data structure.

As shown in fig. 2, the method further comprises:

step S121: and instantiating the case data template according to the joint debugging case parameters in the joint debugging parameters and the current state of the joint debugging case to generate joint debugging case data.

In this embodiment, a case data template is instantiated based on the parameters of the joint debugging case and the current state of the joint debugging case, so as to generate the joint debugging case data. The joint debugging case parameters can provide required execution data for each device in the application environment to execute corresponding application logic or business logic.

The current state of the joint debugging case can include: pending execution status, in execution, failed execution, and/or the like. These states may be represented by one or more bits. For example, four values of two bits may be used to indicate the four states, respectively. For example, after the execution control module receives the state value indication of the joint debugging case data to be executed, it will control the corresponding target device to execute the corresponding application logic. And the execution control module determines that the state value in the joint debugging case data is in execution, the execution control module waits for the return of the execution result, and updates the state value according to the success or failure of the execution after receiving the execution result.

Therefore, in this embodiment, the step S130 may include: and executing the joint debugging case and acquiring an execution result based on the joint debugging case data.

Further, the step S121 may include:

reading the joint debugging case parameters;

loading simulation user parameters;

loading the case data template;

In this embodiment, the parameters of the joint debugging case are read, and the parameters of the simulated user are loaded, where the parameters of the simulated user can be information for simulating the parameters of the real user after the application environment is put into use. Filling the simulated user parameters and the joint debugging case parameters into a blank data structure, and simply, conveniently and automatically forming joint debugging case data for target equipment to identify and execute

The following provides joint debugging parameters for a financial product:

if the module for controlling the target device to execute the joint debugging case in the joint debugging resource is an execution module, in some embodiments, as shown in fig. 3, the step S140 may include:

step S141: analyzing the joint debugging case data to form an execution instruction, wherein the execution instruction comprises: the execution parameters of the joint debugging case are used for triggering the target equipment to execute the corresponding application logic;

step S142: sending the execution instruction to the target device;

step S143: receiving feedback information returned by the target equipment;

step S144: and determining the execution result of the joint debugging case based on the feedback information.

In this embodiment, after the execution control module or the execution control system acquires the joint tone case data, the joint tone case data is analyzed, so that it is known which devices execute the corresponding joint tone cases, which information needs to be sent to the target device, and the target device is triggered to execute the corresponding application logic.

After the target device finishes executing, an execution result or specific execution data may be given, where the execution result and/or specific execution data of the target device are components of the feedback information. According to the feedback information, the execution result of each joint debugging case can be known, and the current state in the joint debugging case data is modified. When each joint debugging case is executed at least once, the execution of the joint debugging task is finished. The execution result of the joint debugging task or the executed state data can be automatically sent to the application end, so that the automatic verification and manual check of the application end are facilitated, and the feedback data can be obtained. Based on the feedback data, how the current application end evaluates the execution condition of the joint debugging task can be obtained. In this embodiment, the feedback data adopts a predetermined data structure, so that after the feedback data is received by the service system, the service system can analyze the feedback data without the participation of a worker, and process various problems carried by the feedback data. For example, if the application indicates that detailed execution state information of a certain joint debugging case needs to be checked, the service platform receives the feedback data and analyzes the feedback request, and then extracts the execution state information of the corresponding joint debugging case from the joint debugging database and sends the execution state information to the application for checking, thereby completing automatic information interaction.

And finally, determining the execution result of the joint debugging task according to the feedback data. According to the joint debugging method provided by the embodiment, after the joint debugging parameters and the task parameters are obtained, the establishment of the application environment, the initialization of the joint debugging environment and the information interaction of the application end are automatically executed, the joint debugging efficiency is improved, the joint debugging error rate is reduced, and the joint debugging effect is improved.

Optionally, the S160 may include:

processing the feedback data;

In order to facilitate monitoring and checking of the staff in the joint debugging process, the step S110 further includes:

starting the display equipment; the display device is configured to display the joint tone related information, where the joint tone related information includes: joint debugging process information, joint debugging case execution condition information, information interaction condition information with an application terminal, and processing condition information of feedback data.

In this way, the display device may be utilized to display the joint tone related information.

In this embodiment, the starting of the display device may be to start the corresponding display device according to the joint debugging parameter, display a joint debugging interface on the display device, and display various pieces of joint debugging related information in the joint debugging interface. The joint tone related information herein includes, but is not limited to, the above information. The display equipment realizes the visualization of joint debugging by displaying the relevant information of the joint debugging.

As shown in fig. 4, the present embodiment provides a service platform, including:

an initialization unit 110, configured to initialize a joint debugging environment based on the joint debugging parameters;

the creating unit 120 is configured to create a joint debugging task and create a joint debugging case under the joint debugging task according to the task parameters in the joint debugging environment;

the execution unit 130 is configured to instruct, based on the joint debugging parameter, to execute the joint debugging case and obtain an execution result of the joint debugging case;

a communication unit 140, configured to send execution data to an application end based on the joint debugging parameter and the execution result of the joint debugging case; receiving feedback data returned by the application terminal based on the execution data;

a determining unit 150, configured to determine an execution result of the joint debugging task based on the feedback data.

The embodiment provides a service platform which comprises one or more servers.

The service platform in this embodiment comprises an initialization unit 110 for initializing the joint debugging environment. The joint debugging environment may be a subsystem deployed in the service platform, or may be an external system deployed outside the service platform. In this embodiment, initializing the joint debugging environment at least includes: and docking the service environment for providing the service for the application terminal. In some embodiments, the initialization unit 110 may be specifically configured to build the service environment based on the joint debugging parameter, record the built service environment, and implement docking with the service environment. In other embodiments, the initialization unit 110 is specifically configured to directly interface with a service environment according to the joint debugging parameter. In the joint debugging environment in this embodiment, the connection with the device in the application environment can be established by recording information such as device parameters for executing various joint debugging cases in the application environment, and some application interfaces are opened, so that the joint between the joint debugging environment and the application environment is completed, and the initialization of the joint debugging environment is realized.

Here, a service environment for providing services for an application is established, including: scheduling of hardware resources, installation and configuration of software resources, control of running states of various software and hardware resources and the like.

In this embodiment, the creating unit 120 creates the joint debugging task of this time according to the task parameters, and then creates one or more joint debugging cases to be executed under the joint debugging task. In this embodiment, the joint debugging case may be a simulation case for providing a service to the user by the application after the service environment is built for simulation.

The execution unit 130 may instruct or request the application environment to execute the corresponding joint tone case by sending the execution instruction or execution instruction. The joint tone case is a real case for providing service after the simulation application environment is formally online. The joint debugging environment acquires the execution result of the application environment on the joint debugging case.

The communication unit 140 may correspond to a communication interface for performing information interaction with the application terminal, and may be configured to send the execution data to the application terminal and receive feedback data returned by the application terminal based on the execution data.

The communication unit 140 herein may be various types of communication interfaces, for example, a wired interface, which may be a cable interface, a fiber optic cable interface, or the like, or a wireless interface. The wireless interface may include a WiFi interface, a bluetooth interface, or other type of wireless interface, etc.

The determining unit 150 may be configured to determine an execution result of the joint debugging task based on the feedback data. For example, if the feedback data indicates that the execution results of all the joint debugging cases meet the service requirements, or the joint debugging cases are successfully executed, it is indicated that the joint debugging task is successfully executed, and further indicated that the established application environment passes verification and the like.

The initialization unit 110, the creation unit 120, the execution unit 130, and the determination unit 150 may correspond to a processor or a processing circuit in this embodiment.

The processor may include: a central processing unit, a microprocessor, a digital signal processor, an application processor, or a programmable array, etc. The processing circuit may include: an application specific integrated circuit.

The processor or the processing circuit executes the functions of the service platform through executable codes stored in the storage medium, and further comprises a control communication jack and performs interaction of execution data and/or feedback data with the application terminal.

In summary, the embodiment provides a service platform, which can perform case verification on an application environment through creation of a joint debugging task, and automatically send execution data of a joint debugging case in a case verification process to an application end, so that at least case verification automation of the application environment and information interaction automation of the application end are realized, joint debugging efficiency is improved, human errors of joint debugging are reduced, and software and hardware resources of the service platform are better and more effectively used.

the initialization unit 110 is specifically configured to perform joint debugging resource configuration and operation state setting of joint debugging resources according to the resource configuration parameters.

In this embodiment, the initialization unit 110 may correspond to one or more processors, and performs the configuration of the joint debugging resources and the setting of the operating state of the joint debugging resources according to the resource configuration parameters. The joint debugging resources can include software and hardware resources used by the application environment, and can also include: and performing the software and hardware resources used by the joint debugging. In some embodiments, if the software and hardware resources of the application environment are already configured, the initialization unit 110 herein may be only used for configuring the software and hardware resources participating in the joint debugging. For example, a joint debugging database is configured, and relevant parameters of joint debugging tasks and joint debugging cases are recorded in the joint debugging database. And the software and hardware resources for executing the joint debugging case in the joint debugging task can belong to the established application environment.

In some embodiments, the initialization unit 110 is specifically configured to determine, according to the resource configuration parameter, whether a target device pointed by the resource configuration parameter is available; when the target equipment is available, setting equipment parameters of the target equipment according to the resource configuration parameters; wherein the target device comprises: at least one of a front-end device interacting with the application end, a platform device executing application logic, a file system device recording service execution information and a feedback processing system device processing the feedback data; and forming resource configuration alarm information when the target equipment part is unavailable.

The target device is an execution device for executing the joint debugging case, and is a hardware resource of the application environment.

In this embodiment, when the joint debugging environment is initialized, hardware devices participating in the joint debugging or the application environment need to be located according to resource configuration parameters, and then whether subsequent configuration is performed is determined according to the state of the current device, so that the state and the operation state of the device of the target device are ready, after the device is ready, the device can execute service logic provided by an application end, and equivalently, joint debugging cases can be executed, and whether the established application environment meets the service requirements of the application end can be determined through one or more joint debugging cases under a joint debugging task.

In some embodiments, the joint debugging parameters further comprise: case data templates and joint debugging case parameters, wherein the joint debugging case parameters comprise: at least two different types of cases of the same service;

the service platform further comprises:

the executing unit 130 is specifically configured to execute the joint debugging case and obtain an execution result based on the joint debugging case data.

The instantiation unit, which may also correspond to the processor or the processing circuit in the present embodiment, is equivalent to generating the joint debugging case data that can be identified and applied by the target device based on the preset case data template that can be identified and applied by the target device based on at least part of the information in the joint debugging parameters and the current state of the joint debugging case.

When instantiating a cell, the current state of the corresponding joint tone case is generally the state to be executed when the joint tone case data is generated.

Optionally, the instantiation unit is specifically configured to read the joint debugging case parameters; loading simulation user parameters; loading the case data template; and filling the case data template to form the joint debugging case data based on the simulated user parameters and the joint debugging case parameters.

In this embodiment, the template of the joint debugging case data may correspond to a template file, and the instantiation unit needs to correspondingly fill part of information in the joint debugging parameters and/or the current state of the joint debugging case into a blank part in the template file. In other embodiments, the joint call case data template may be a preset data structure of fields to be filled. The instantiation unit is specifically used for correspondingly filling partial information in the joint debugging parameters and/or the current state of the joint debugging case into the field to be filled, so that the instantiation of the joint debugging case is realized, and the joint debugging case data which can be executed by the target equipment or the execution equipment is provided.

In some embodiments, the executing unit 130 is specifically configured to parse the joint tone case data to form an execution instruction, where the execution instruction includes: the execution parameters of the joint debugging case are used for triggering the target equipment to execute the corresponding application logic; sending the execution instruction to the target device; receiving feedback information returned by the target equipment; and determining the execution result of the joint debugging case based on the feedback information.

In this embodiment, the execution unit 130 may instruct or request the corresponding target device by sending the execution instruction based on the joint debugging case data, and execute the corresponding joint debugging case, so that the joint debugging case is used to verify the business logic of one or more target devices in the application environment, which is convenient for the application end to determine whether the application environment provided by the current service platform meets the business requirement of the current service platform, or to determine whether the service platform can provide the required application environment.

In some embodiments, the determining unit 150 is specifically configured to process the feedback data; and determining the execution result of the joint debugging task based on the processing result of the feedback data.

The communication unit 140 receives feedback data returned by the application after sending the execution data to the application. The feedback data may include: an indication of acknowledgement, an indication of non-acknowledgement, and/or a consultation of the issue, etc. The confirmation instruction can be an instruction for determining that the joint debugging task is executed without errors; the negative indication may be an indication that the joint debugging task was determined to be performing incorrectly. The question consultation can be information of specific conditions for executing the joint debugging task.

In this embodiment, after the determining unit 150 obtains the feedback data from the communication unit 140, the feedback data is analyzed, so as to determine the execution result of the joint debugging task. For example, if the feedback data carries a confirmation instruction, the joint debugging task is considered to be successfully executed, and if the feedback data carries a denial instruction, the joint debugging task is considered to be unsuccessfully executed, which joint debugging cases are unsuccessfully executed and target equipment for which the joint debugging cases are unsuccessfully executed can be further determined according to the confirmation instruction and/or the denial instruction of the joint debugging cases. The determining unit 150 may further query the execution status information of the corresponding joint debugging task according to the feedback data, feed back the feedback information to the application terminal through the communication unit 140, and determine whether the joint debugging task is successfully executed based on the reprocessing of the feedback data by the application terminal.

In some embodiments, the initialization unit is further configured to start a display device; wherein, the display device is configured to display the joint tone related information, wherein the joint tone related information includes: joint debugging process information, joint debugging case execution condition information, information interaction condition information with an application terminal, and processing condition information of feedback data.

In this embodiment, the service platform further includes a function of starting a corresponding display device when the joint debugging is performed. The display device here may be a display resource among the joint debugging resources. Through the starting of the display equipment, the work is facilitated, and the situation information and the like of the execution of various joint debugging tasks are checked through the display equipment. In the execution process of the joint debugging task, information needing to be displayed can be visualized, and the visual joint debugging task can be conveniently checked and monitored by workers.

Embodiments of the present invention further provide a computer storage medium, where a computer executable code is stored, and after being executed by a processor, the computer executable code is capable of implementing a joint debugging method provided in any one or more of the foregoing technical solutions, for example, one or more of the methods shown in fig. 1 to 3 and 6 to 11,

the computer storage medium may include: various computer storage media such as optical disks, removable hard disks, flash disks, magnetic tape, and the like, may be selected as non-transitory storage media.

One specific example is provided below in connection with any of the embodiments described above:

example one:

as shown in fig. 5, this example provides an alternative hardware structure diagram of a service platform, which includes a processor 201, an input/output interface 203 (e.g., a display screen, a touch screen, and a speaker), a storage medium 204, and a network interface 202, and various components inside the service platform may be connected and communicated via a system bus 205. Accordingly, the storage media 204 each store therein an executable instruction for executing the joint debugging method described in the embodiment of the present invention. The hardware modules shown in fig. 5 may be partially implemented, fully implemented, or other hardware modules as needed, the number of each type of hardware module may be one or more, and the hardware modules may be implemented in the same geographical location, or distributed in different geographical locations, and may be used to perform the joint debugging method shown in fig. 1 or fig. 3.

Example two:

the present example provides a joint debugging system included in the service platform, which includes a joint debugging environment management module, a joint debugging task management module, a joint debugging case data generation module, a joint debugging case execution module, a data interaction module, and a feedback processing module.

The joint debugging task management module may be a component of the initialization unit 110; the joint debugging case data generation module can be a component of the instantiation unit; the joint debugging case execution module may be a component of the execution unit 130; the data interaction module may be a constituent structure of the aforementioned determination unit 150; the feedback processing module may be a constituent structure of the aforementioned determination unit 150.

The joint debugging environment management module is configured to receive and store joint debugging parameters entered by a worker through a User Interface (UI), and initialize a joint debugging environment.

Firstly, the saved joint debugging parameters mainly include specific parameter data of the current joint debugging fund product, such as fund type, fund business number and fund code, data interaction mode, joint debugging case time range, joint debugging equipment configuration and the like, which are specifically shown in the following table.

The transaction system is one or more servers that perform the processes of funding, subscription, and redemption. The front-end processor can be one or more servers which perform data interaction between the service platform and the application terminal. The file system can be a system for storing various files operated by the service environment; the joint debugging database can be a database for storing joint debugging parameters, task parameters, execution data, feedback data and other information.

Secondly, initializing the joint debugging environment needs to read the resource configuration joint debugging parameters which are recorded by the staff, and initialize the joint debugging environment according to the parameter items,

initializing the joint debugging environment includes:

firstly, according to the merchant information in the joint debugging parameters, merchant information is created in a system database, and the merchant number, fund code and fund type of the joint debugging merchant are set.

Secondly, the joint debugging is checked in parallel to refer to the current state of the equipment deployed by each module, for example, whether the target equipment normally operates (or whether the current equipment is occupied by other joint debugging tasks), if the target equipment is available, system parameters belonging to the equipment are updated (systems belonging to different equipment are different), and whether the system needs to be restarted is judged according to the type of the system.

In addition, after the joint debugging environment is initialized, the related devices are all in the state occupied by the current task, so that other joint debugging tasks are prevented from occupying the initialized devices again.

Fig. 7 is a schematic diagram of an initialization joint debugging environment, which includes:

reading resource configuration parameters;

generating joint debugging merchant information;

detecting the state of the front-end processor, detecting the state of the transaction system, detecting the state given by the file system, and checking the state of the feedback processing system. The feedback processing systems herein each correspond to the aforementioned feedback processing module, and to one or more servers that process feedback data.

And judging whether the front-end processor, the transaction system, the file system and the feedback processing system are available, if so, executing the subsequent equipment updating operation step, and if not, sending failure alarm information.

The update operation may include:

updating parameters of a front-end processor, transaction system, file system and feedback processing systems;

and after updating, restarting the front-end processor, restarting the transaction system, restarting the file system and restarting the feedback processing system.

And the joint debugging task management module is used for generating an example of the joint debugging task according to the task parameters in the joint debugging parameters. The purpose is to clarify the specific execution time point of each case and the target equipment occupied by the execution case.

The state of the joint debugging case may include: initialization, generated joint debugging case data, successful execution of the joint debugging case and failure of execution of the joint debugging case. Assume that the status code corresponding to initialization is 1, the status code corresponding to the generated joint debugging case data is 2, the status code corresponding to successful execution of the joint debugging case is 3, and the status code corresponding to failed execution of the joint debugging case is 4.

As shown in fig. 7, which is a schematic diagram illustrating state transition of the joint debugging case, after initialization, the generated joint debugging case data may be entered, and the state of successful execution of the joint debugging case or failed execution of the joint debugging case may be entered from the generated joint debugging case data.

The joint debugging case data generation module is used for forming one or more joint debugging cases under the joint debugging task based on joint debugging case parameters and a joint debugging case data template after the joint debugging task is generated; the method specifically comprises the following steps: the joint cases associated with the joint cases cannot be directly executed because the parameters of the joint cases are not parameters that can be received and processed by the trading system, and therefore specific case data (i.e., instantiations of the joint cases) needs to be generated for each case.

The generation of the joint tone case data may be as shown in fig. 8, including:

step 1: reading the parameters of the joint debugging case;

step 2: judging whether the joint debugging case parameters are legal or not, if so, entering a step 3, and if not, entering a step 4; for example, it is determined whether the execution device pointed in the joint debugging case parameter belongs to a device in the service platform, for example, whether a plurality of joint debugging case parameters in the same joint debugging task point to the same product of the client.

And step 3: loading user parameters;

and 4, step 4: sending joint debugging parameter alarm information;

and 5: and (4) judging whether the user exists, if so, entering a step 6, and if not, entering a step 4. The step 5 may include: and querying the joint debugging database according to the user parameters to see whether the joint debugging database has the user record of the user.

Step 6: loading a joint debugging case data template;

and 7: instantiating a joint debugging case to generate joint debugging case data; for example, the user parameters and the joint debugging parameters are filled in a joint debugging case data template, so that instantiation of the joint debugging case is realized, and the joint debugging case data is generated.

And 8: and storing the joint debugging case data.

Taking the joint tone case of "ser1 account opening" of the case in the following table as an example, first, the user information with the user identifier of user1 is loaded from the joint tone database (Data Base, DB), and then the user information is filled into the account opening case Data template.

At this time, the data of the case instance may be directly sent to an account opening interface (fund _ open _ acc _ service) of the transaction system, and the specific sending mode is to simulate system front-end call.

And the joint debugging case execution module is used for executing the joint debugging case, namely sending the data generated by the case to a corresponding transaction system interface by the front end of the simulation system, so as to generate specific account opening and transaction records in the joint debugging DB.

In order to ensure that the execution time of the joint debugging case is consistent with the time specified by the staff, the system time of the equipment where the transaction system is located needs to be modified before the case is executed.

If the case execution succeeds, the state of the case is updated to 3 state, otherwise to 4 state.

Fig. 9 provides a schematic diagram of an execution state of a joint debugging case, which includes:

step 11: reading the joint debugging case data;

step 12: analyzing the joint debugging case data;

step 13: modifying the system time according to the execution time of the joint debugging case;

step 14: judging whether the system time is successfully modified, if so, entering a step 15, and if not, entering a step 16:

step 15: and generating an execution instruction, wherein the execution instruction is used for instructing the target device to execute.

Step 16: sending execution failure alarm information;

and step 17: is the joint debugging case successfully executed? If the step S18 is successfully executed, the step S19 is executed if the step S is not successfully executed;

step S18: modifying the state code of the joint debugging case into 3;

step S19: the status code of the joint debugging case is modified to 4.

And the data interaction module can be used for data interaction with the user side.

The data interaction module can be used for the file generation system to load account opening and transaction data from the joint debugging DB, generate an interaction file according to an agreed format, and synchronize the file to the front-end processor through a synchronization (sync) technology, so that a fund company can download the file through a hypertext transfer protocol (http) protocol or a text transfer protocol (ftp).

After the application terminal (fund company) processes the files of the internet financing platform, the corresponding feedback files are uploaded to the front-end processor.

The feedback file module is used for the timed task of the financing platform to automatically synchronize the feedback file to the specified directory of the equipment where the feedback file processing system is located, the feedback file processing system can continuously detect whether the feedback file exists, and if so, the feedback file can be automatically processed.

And the visualization of the joint debugging resources and the joint debugging process is used for the visualization of the joint debugging equipment and the visualization of the joint debugging process.

The visualization of the joint debugging equipment is used for initializing the joint debugging environment after the joint debugging task is started, and the initialized equipment becomes an occupied state; and after the execution of the joint debugging task is finished, all the devices configured by the joint debugging task are changed into the idle state again. In addition, the device that cannot log in is set to a failure state in the joint debugging system (the device in the failure state cannot be initialized by the joint debugging task).

The visualization of the joint debugging process mainly comprises the completion conditions of the following links in the joint debugging process: the execution progress of the joint debugging case, the file interaction completion condition, the feedback of the processing result and the failure information of the file and the like. The monitoring implementation method comprises the following steps:

the file interaction completion progress and the file processing progress are fed back, and the execution result of the link of the current task is recorded in the database after the corresponding steps are completed.

The visualization of the execution progress of the joint debugging cases is embodied by the status field of each joint debugging case of the current joint debugging task, and the proportion of the executed cases in all cases is the execution progress of the current task cases.

The financial platform downloads the file from the front-end processor and can acquire the file in an http or ftp mode.

Fig. 10 is a schematic diagram of a joint debugging system, which may specifically include:

the financial management platform corresponds to the service platform and can be used for building an application environment of practical application and a joint debugging environment during joint debugging;

a front-end processor of a financing platform;

and the application end of the fund company carries out information interaction with the financing platform through the front-end processor of the financing platform.

The financial platform uploads the transaction file to the financial platform front-end processor through a synchronization technology, and the application terminal downloads the transaction file from the financial platform front-end processor, for example, the transaction file is downloaded based on an http protocol or an ftp protocol. And sending a feedback file to the financial platform by the front-end processor of the financial platform based on the http protocol or the ftp protocol.

The transaction document herein may include: one or more of an opening file generated by opening the opening joint-regulation case, a subscription file generated by subscribing the joint-regulation case and a redemption case file generated by redeeming the joint-regulation case.

1) This example provides the degree of automation of the financial platform fund product joint debugging, and to a great extent has improved the efficiency of joint debugging, has guaranteed the execution of joint debugging.

2) The isolation of joint debugging equipment and joint debugging data is realized, and a plurality of joint debugging tasks can be executed in parallel without mutual influence.

2) The visualization of the joint debugging process is realized, including the visualization of joint debugging resources and the visualization of the joint debugging process, so that the utilization rate of the joint debugging resources can be improved, and the joint debugging progress of the fund can be controlled more effectively.

Example three:

as shown in fig. 11, the present example provides a joint debugging method, including:

step S1: the joint debugging environment management module receives joint debugging parameters;

step S2: the joint debugging environment management module stores joint debugging parameters;

and step S3: the joint debugging environment management module initializes a joint debugging environment;

and step S4: the joint debugging task management module generates a joint debugging task instruction to the joint debugging task management module, and after initialization is completed, the joint debugging task instruction can be sent based on received task parameters.

Step S5: the joint debugging task management module reads the joint debugging parameters, and specifically comprises the following steps: reading the joint debugging parameters from a joint debugging environment management module or a joint debugging database for storing the joint debugging parameters;

step S6: the joint debugging task management module creates an example of the joint debugging task; examples herein are cases of specific joint debugging tasks.

Step S7: the joint debugging task management module creates an example of the joint debugging case; examples herein may be embodied in a joint tone case;

step S8: and the joint debugging task management module sends a joint debugging case data generation instruction to the case data generation module, and generates joint debugging case data after receiving the instruction and returns the joint debugging case data to the joint debugging task management module.

Step S9: the case data generation module returns the joint debugging case data to the joint debugging task management module;

step S10: the joint debugging task management module is used for debugging the case execution module to send an execution instruction;

step S11: the joint debugging case execution module executes the instance of the current joint debugging case;

step S12: the joint debugging case execution module stores the execution result of the joint debugging case;

step S13: the joint debugging case execution module returns an execution result to the joint debugging task management module;

step S14: the joint debugging task management module transmits a sending instruction to the data interaction module;

step S15: the data interaction module generates an execution data file and sends the execution data file to the application terminal, and specifically, after receiving a sending instruction, the data interaction module reads the execution data to generate the execution data file;

step S16: the data interaction module returns a sending result to the joint debugging task management module, and specifically, the data interaction module feeds back the sending result to the joint debugging task management module based on the sending condition of the execution data file;

step S17: the joint debugging task management module sends an acquisition instruction to the data interaction module;

step S18: the data interaction module acquires a feedback file, specifically, after receiving the acquisition instruction, the data interaction module reads the feedback file from the application terminal, wherein the feedback file carries the feedback data;

step S19: the data interaction module feeds back a file acquisition result to the joint debugging task management module, and specifically, the data interaction module sends the acquisition result to the joint debugging task management module according to the acquisition condition of the feedback file;

step S20: and the joint debugging task module sends a processing instruction to the feedback processing module, and specifically, after the joint debugging task determines that the current service platform obtains the feedback file, the joint debugging task sends the processing instruction to the feedback processing module.

Step S21: the feedback processing module processes the feedback file, specifically, after receiving the processing instruction, the feedback processing module reads the feedback file from the data interaction module, analyzes the feedback file, and executes corresponding processing operation;

step S22: the feedback processing module stores the processing result;

step S23: the joint debugging task management module stores the execution result of the joint debugging task;

step S24: the joint debugging task management module generates a feedback result of the execution of the joint debugging task;

step S25: and the joint debugging task management module outputs a feedback result executed by the joint debugging task.

In one case, the steps S13, S16, and S19 may be optional, omitted, or executed.

In some implementations, the step S9 may instead be sending the joint case generated condition information to the joint task management module. The joint debugging task management module is convenient to send execution instructions.

In this embodiment, the joint debugging task management module is equivalent to a central control module in the joint debugging process. In some embodiments, the trigger in the joint debugging process can be sent from the execution module of the previous operation to the execution module of the next operation, and the trigger without the execution of various operations is executed by one joint debugging task management module.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, all the functional units in the embodiments of the present invention may be integrated into one processing module, or each unit may be separately used as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: a mobile storage device, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.

Claims

1. A joint debugging method, comprising:

acquiring joint debugging parameters, wherein the joint debugging parameters comprise an interactive interface of an application end, a case data template and joint debugging case parameters;

based on the joint debugging parameters, completing the butt joint of a joint debugging environment and an application environment, initializing the joint debugging environment, and starting display equipment;

setting the initialized equipment corresponding to the joint debugging environment to be in a state occupied by the joint debugging task;

the joint debugging environment creates the joint debugging task according to task parameters of the joint debugging task and creates a joint debugging case under the joint debugging task, wherein the task parameters comprise services pointed by the joint debugging task and joint debugging operation required by each service;

instantiating the case data template based on the joint debugging case parameters and the current state of the joint debugging case to obtain joint debugging case data;

based on the joint debugging case data, instructing to execute the joint debugging case, displaying the case execution progress on the display equipment, and acquiring the execution result of the joint debugging case;

based on the joint debugging parameters and the execution results of the joint debugging cases, executing data is sent to the application terminal through the interactive interface, and the file interaction completion progress, the processing progress of feedback data and failure information are displayed on the display equipment;

receiving the feedback data obtained by the application terminal through verifying the execution data;

analyzing the feedback data based on a preset data structure to obtain the execution condition of the joint debugging task;

and after the execution of the joint debugging task is finished, setting the equipment corresponding to the joint debugging environment of the joint debugging task in an idle state.

2. The method of claim 1,

the joint debugging parameters comprise: a resource configuration parameter;

initializing the joint debugging environment based on the joint debugging parameters, including:

3. The method of claim 2,

the performing joint debugging resource configuration and operation state setting of joint debugging resources according to the resource configuration parameters comprises:

4. The method of claim 1, 2 or 3,

the joint debugging case parameters comprise: at least two different types of cases of the same service.

5. The method of claim 1,

instantiating the case data template based on the parameters of the joint debugging case and the current state of the joint debugging case to obtain joint debugging case data, wherein the steps of:

reading the joint debugging case parameters;

loading simulation user parameters;

loading the case data template;

6. The method of claim 1,

the instructing, based on the joint debugging case data, to execute the joint debugging case and obtain an execution result of the joint debugging case includes:

sending the execution instruction to the target device;

receiving feedback information returned by the target equipment;

7. A service platform, comprising:

the system comprises an initialization unit, a joint debugging unit and a data processing unit, wherein the initialization unit is used for acquiring joint debugging parameters, and the joint debugging parameters comprise an interactive interface of an application end, a case data template and joint debugging case parameters; based on the joint debugging parameters, completing the butt joint of a joint debugging environment and an application environment, initializing the joint debugging environment, and starting display equipment;

the initialization unit is further configured to set the initialized device corresponding to the joint debugging environment to a state occupied by the joint debugging task;

the creating unit is used for creating the joint debugging task according to the task parameters of the joint debugging task in the joint debugging environment and creating a joint debugging case under the joint debugging task, wherein the task parameters comprise the services pointed by the joint debugging task and the joint debugging operation required by each service;

the instantiation unit is used for instantiating the case data template based on the joint debugging case parameters and the current state of the joint debugging case to obtain joint debugging case data;

the execution unit is used for indicating to execute the joint debugging case based on the joint debugging case data, displaying the case execution progress on the display equipment and acquiring the execution result of the joint debugging case;

the communication unit is used for sending execution data to the application terminal through the interactive interface based on the joint debugging parameters and the execution result of the joint debugging case, and displaying file interaction completion progress, processing progress of feedback data and failure information on the display equipment; receiving the feedback data obtained by the application terminal through verifying the execution data;

the determining unit is used for analyzing the feedback data based on a preset data structure to obtain the execution condition of the joint debugging task;

the initialization unit is further configured to set the device corresponding to the joint debugging environment of the joint debugging task in an idle state after the execution of the joint debugging task is finished.

8. The service platform of claim 7,

the joint debugging parameters comprise: a resource configuration parameter;

9. The service platform of claim 8,

the initialization unit is specifically configured to determine, according to the resource configuration parameter, whether a target device pointed by the resource configuration parameter is available; when the target equipment is available, setting equipment parameters of the target equipment according to the resource configuration parameters; wherein the target device comprises: at least one of a front-end device interacting with the application end, a platform device executing application logic, a file system device recording service execution information and a feedback processing system device processing the feedback data; and forming resource configuration alarm information when the target equipment part is unavailable.

10. The service platform of claim 7, 8 or 9,

11. The service platform of claim 7,

the instantiation unit is specifically used for reading the joint debugging case parameters; loading simulation user parameters; loading the case data template;

12. The service platform of claim 7,

the execution unit is specifically configured to analyze the joint debugging case data to form an execution instruction, where the execution instruction includes: the execution parameters of the joint debugging case are used for triggering the target equipment to execute the corresponding application logic; sending the execution instruction to the target device; receiving feedback information returned by the target equipment; and determining the execution result of the joint debugging case based on the feedback information.

13. A computer storage medium having stored thereon computer executable code which, when executed by a processor, is capable of implementing the joint debugging method of any one of claims 1 to 6.