CN113760723B - Business process debugging method and device - Google Patents

Business process debugging method and device Download PDF

Info

Publication number
CN113760723B
CN113760723B CN202110043923.5A CN202110043923A CN113760723B CN 113760723 B CN113760723 B CN 113760723B CN 202110043923 A CN202110043923 A CN 202110043923A CN 113760723 B CN113760723 B CN 113760723B
Authority
CN
China
Prior art keywords
debugging
business process
event
debug
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110043923.5A
Other languages
Chinese (zh)
Other versions
CN113760723A (en
Inventor
岳文红
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Jingdong Qianshi Technology Co Ltd
Original Assignee
Beijing Jingdong Qianshi Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Jingdong Qianshi Technology Co Ltd filed Critical Beijing Jingdong Qianshi Technology Co Ltd
Priority to CN202110043923.5A priority Critical patent/CN113760723B/en
Publication of CN113760723A publication Critical patent/CN113760723A/en
Application granted granted Critical
Publication of CN113760723B publication Critical patent/CN113760723B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/362—Software debugging
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0633—Workflow analysis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management

Abstract

The invention discloses a method and a device for debugging a business process, and relates to the technical field of computers. One embodiment of the method comprises the following steps: acquiring business process configuration information, and creating a business process route according to the business process configuration information; obtaining debugging message information, and running a service flow to be debugged by using the debugging message in the debugging message information; when the operation is carried out to the routing node woven with the embedded point, judging whether to trigger a debugging event in the embedded point according to the debugging message information; if yes, executing the debugging event to debug the business flow. According to the embodiment, the experience of developers is improved, the complexity of debugging the business process is reduced, the efficiency of debugging the business process is improved, and the efficiency of developing the business process is improved.

Description

Business process debugging method and device
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and an apparatus for debugging a business process.
Background
Before formally releasing the business process to be online, debugging is needed to ensure that the business process can normally run. In an online environment, the status of a business process is mostly determined by monitoring nodes, so the nodes are generally considered as the minimum controllable granularity in the running process of the business process.
For relatively closed business process nodes, because of strong message relevance such as data conversion, service call and the like, the nodes relate to whether the whole business process can be normally executed or not, and gradual debugging is often not performed. The existing service flow debugging method is that after the whole service flow is developed, the service flow is tested on line, verified and debugged.
The prior art has at least the following problems:
the existing business process debugging method cannot debug the business process nodes, so that experience of developers is poor; message modification is not supported, so that the service flow debugging efficiency and the service flow debugging complexity are affected, and the service flow development efficiency is low.
Disclosure of Invention
In view of the above, the embodiment of the invention provides a method and a device for debugging a business process, which can debug a business process node and improve the experience of developers; meanwhile, message modification is supported, so that the service flow debugging efficiency is improved, the service flow debugging complexity is reduced, and the service flow development efficiency is further improved.
To achieve the above object, according to a first aspect of an embodiment of the present invention, there is provided a method for debugging a business process, including:
Acquiring business process configuration information, and creating a business process route according to the business process configuration information;
obtaining debugging message information, and running a service flow to be debugged by using the debugging message in the debugging message information;
when the operation is carried out to the routing node woven with the embedded point, judging whether to trigger a debugging event in the embedded point according to the debugging message information;
if yes, executing the debugging event to debug the business flow.
Further, the debug event includes a callback debug event; executing the debug event to perform business process debugging, further comprising:
acquiring a current debugging message and a current debugging event;
and calling back the current debugging message and the current debugging event to an operation initiator of the business process to be debugged, so that the operation initiator can debug the business process according to the current debugging message and the current debugging event.
Further, after the step of callback the current debug message and the current debug event to the operation initiator of the to-be-debugged business process, the method further comprises:
receiving a debugging message updated by an operation initiator;
replacing the current debugging message with the updated debugging message, and continuing to run the business flow to be debugged.
Further, the debug message information also comprises a buried point list and a debug mode; judging whether to trigger a debugging event in the embedded point according to the debugging message information, and further comprising:
And acquiring current routing node information, and judging whether to trigger a debugging event according to the current routing node information, the buried point list and the debugging mode.
Further, the debug event also includes a simulated service event; executing the debug event to perform business process debugging, further comprising:
and acquiring the simulated service type, and executing a corresponding simulated service event according to the simulated service type so as to debug the business process.
Further, if the debug event in the buried point is not triggered, the method further comprises:
and continuing to operate the service flow to be debugged until the next routing node woven with the buried point or the operation of the service flow to be debugged is completed.
According to a second aspect of an embodiment of the present invention, there is provided a business process debugging apparatus, including:
the business process route creation module is used for acquiring business process configuration information and creating a business process route according to the business process configuration information;
the running module is used for acquiring the debugging message information and running the business flow to be debugged by utilizing the debugging message in the debugging message information;
the judging module is used for judging whether to trigger a debugging event in the buried point according to the debugging message information when the judging module runs to the routing node woven with the buried point;
And the debugging module is used for executing the debugging event to debug the business flow if the debugging event in the debugging is triggered.
Further, the debug event includes a callback debug event; the debug module is also for:
acquiring a current debugging message and a current debugging event;
and calling back the current debugging message and the current debugging event to an operation initiator of the business process to be debugged, so that the operation initiator can debug the business process according to the current debugging message and the current debugging event.
According to a third aspect of an embodiment of the present invention, there is provided an electronic apparatus including:
one or more processors;
storage means for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement any of the business process debugging methods described above.
According to a fourth aspect of embodiments of the present invention, there is provided a computer readable medium having stored thereon a computer program which, when executed by a processor, implements a business process debugging method as described above.
One embodiment of the above invention has the following advantages or benefits: because the service flow configuration information is acquired, a service flow route is established according to the service flow configuration information; obtaining debugging message information, and running a service flow to be debugged by using the debugging message in the debugging message information; when the operation is carried out to the routing node woven with the embedded point, judging whether to trigger a debugging event in the embedded point according to the debugging message information; if yes, the technical means of executing the debugging event to debug the business process is adopted, so that the problem that in the existing business process debugging method, because debugging can not be carried out on the business process node, the experience of developers is poor is solved; the method does not support message modification, influences the service flow debugging efficiency and the service flow debugging complexity, further causes the technical problem of low service flow development efficiency, further achieves the purpose of debugging aiming at service flow nodes, and improves the experience of developers; meanwhile, message modification is supported, so that the service flow debugging efficiency is improved, the service flow debugging complexity is reduced, and the technical effect of the service flow development efficiency is further improved.
Further effects of the above-described non-conventional alternatives are described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
fig. 1 is a schematic diagram of a main business process of a business process debugging method according to a first embodiment of the present invention;
FIG. 2a is a schematic diagram of a main business process of a business process debugging method according to a second embodiment of the present invention;
FIG. 2b is a schematic diagram of a main architecture corresponding to the business process debugging method shown in FIG. 2 a;
FIG. 3 is a schematic diagram of main modules of a business process debugging device according to an embodiment of the present invention;
FIG. 4 is an exemplary system architecture diagram in which embodiments of the present invention may be applied;
fig. 5 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present invention are included to facilitate understanding, and are to be considered merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a schematic diagram of a main business process of a business process debugging method according to a first embodiment of the present invention; as shown in fig. 1, the method for debugging a business process provided by the embodiment of the invention mainly includes:
step S101, acquiring business process configuration information, and creating a business process route according to the business process configuration information.
Specifically, according to the embodiment of the invention, after a business process debugging framework is started, a business process engine is initialized (in order to ensure efficient execution of a business process in a business system, coordination work of related components needs to be controlled through a corresponding business process engine, so that information storage, authority, approval, message notification and the like in the business process flow are circulated according to a certain process rule, and all or part of the business process is automatically realized), a debugging instance is created by utilizing the business process engine, and a handler interface (callback interface) needing callback is registered in the debugging instance (so as to facilitate subsequent triggering of a debugging callback event, and callback operation of corresponding data information is executed by utilizing the callback interface). And acquiring business process configuration information such as a business process file, a configuration file, a function file and the like by using a business process engine, and creating a business process route according to the business process configuration information.
Through the arrangement, before the business process to be debugged is operated to carry out business process debugging, the business process route corresponding to the business process debugging is determined, so that the routing nodes can be debugged step by step later, the business process debugging efficiency is improved, and the experience of developers is improved.
Further, according to an embodiment of the present invention, after the step of creating the business process route, the method further includes: embedding a buried point at a target routing node of the business process route, and adding a debugging event in the buried point.
The embedded point is to implant a relevant statistical code at a key part of the product business process, and is used for tracking the behavior of each user and counting the use degree of the key business process. In the process of program development, the purposes of counting access times, recording input parameters, output parameters and the like can be realized by arranging buried points in front of and behind the service flow nodes (the routing nodes).
Through the arrangement, in the process of arranging the business processes, the embedded points are woven in the corresponding positions (such as the positions of a plurality of routing nodes before the business processes are executed, before the nodes are executed, after the business processes are executed and the like) in a tangent plane mode, and meanwhile, corresponding debugging events are added into each embedded point according to the configuration information of the business processes. According to the embodiment of the invention, in the process of arranging the business flow, aiming at a plurality of routing nodes with strong message (the message represents the data packet related in the business flow), as the configuration of the routing nodes influences whether the whole business flow can be normally executed, the embedded points can be not woven into the routing nodes with strong message relevance, but the embedded points can be debugged as a whole.
Through the arrangement, in the process of arranging the business processes, embedding points are woven according to the business process configuration information, corresponding debugging events are added, and even for a relatively closed business process, gradual debugging of business process nodes (routing nodes) can be realized, so that the business process debugging and development efficiency is remarkably improved.
Step S102, obtaining debugging message information, and running a business process to be debugged by using the debugging message in the debugging message information.
Specifically, according to the embodiment of the present invention, the above-mentioned debug message information includes a debug message (having a certain message format), a buried point list (indicating the corresponding relation between the route node position corresponding to the buried point and the debug event added in the buried point), and a debug mode (including three modes of executing or skipping to debug, step-in and step-out, step-over, step-skip (when a single step is executed, a single step-in is encountered in a function, the sub-function will not be entered into the sub-function, but the whole execution of the sub-function is stopped again, that is, the whole sub-function is regarded as a step), step-out, and step-out (when a single step is executed into the sub-function, the rest of the sub-function can be executed by step-out, and the previous function is returned).
Furthermore, the debug message information may further include simulation service configuration information such as a simulation service type, a simulation service instance, etc., so as to determine a corresponding simulation service event according to the simulation service configuration information later, so as to debug the service flow.
Further, according to an embodiment of the present invention, the step of obtaining debug message information and running a to-be-debugged service flow by using a debug message in the debug message information includes:
obtaining debugging message information, adding the debugging message information into a debugging instance, and operating the business flow to be debugged by utilizing the debugging instance.
The debugging examples are in one-to-one correspondence with the threads, and through the arrangement, the multi-thread debugging can be realized by respectively adding the debugging message information into different debugging examples, so that the service flow debugging efficiency is further improved.
Step S103, when the router node is operated to the routing node woven with the embedded point, judging whether to trigger the debugging event in the embedded point according to the debugging message information.
Specifically, according to an embodiment of the present invention, the determining whether to trigger the debug event in the buried point according to the debug message information further includes:
and acquiring current routing node information, and judging whether to trigger a debugging event according to the current routing node information, the buried point list and the debugging mode.
According to the embodiment of the invention, if the callback debug event is added in the embedded point, when the callback debug event is executed to the routing node woven with the embedded point, whether the callback debug event and the debug mode are triggered can be judged by comparing the embedded point list in the debug message information, the current debug mode and the current node information. For example, if the "buried point included in the buried point list corresponds to the current routing node, it is determined that the debug event is triggered, and the debug is performed on the current routing node according to the debug mode. Further, node information at the time of triggering the last debug event may also be obtained, and whether to trigger the debug event may be determined according to the current node information, the last node information, the buried point list, and the debug mode (e.g. when the debug mode is a step-by-step execution, whether to trigger the debug time is determined by comparing the last node information with the current node information).
Step S104, if the debugging event in the embedded point is triggered, executing the debugging event to debug the business process.
According to a specific embodiment of the invention, the to-be-debugged service flow comprises A, B, C nodes, wherein buried points are woven in front of the node B, and the message information in the debug message information comprises the actual content of the debug message and buried point B information (buried point list); when the business flow to be debugged runs to the A node, the context information comprises: the actual content of the debug message, the embedded point B information, the current node being the A node, the debug mode being step over, the A node not needing to trigger the debug event after comparison, continuing to operate the business flow to be debugged, and when operating to the node B, the context information is as follows: the actual content of the debug message, the embedded point B information (embedded point list), the current node being the node B, the debug mode being step over, after comparison, the node B needs to trigger the debug event, and the debug event is executed. Assuming we select step into mode, when executing to the C node, the context information is: the actual content of the debug message, the embedded point B, the current node being the C node and the debug mode being step intro, and the C node needing to trigger the debug event (because the last node triggers the debug event, the debug mode corresponding to the current node is step intro, therefore, the debug event is continuously triggered) after comparison, executing the debug event. And so on
Specifically, according to an embodiment of the present invention, the debug event includes a callback debug event; the step of executing the debug event to debug the business process further comprises:
acquiring a current debugging message and a current debugging event;
and calling back the current debugging message and the current debugging event to an operation initiator of the business process to be debugged, so that the operation initiator can debug the business process according to the current debugging message and the current debugging event.
According to the embodiment of the invention, if the callback debugging event is triggered, the handler interface is called to callback the current debugging message and the current debugging event to the operation initiator (i.e. the client) of the business process to be debugged, so that the client can debug the business process according to the current debugging message and the corresponding debugging event. The setting is more fit with the habit of the developer, and is favorable for improving the development user experience.
Further, after the step of callback the current debug message and the current debug event to the operation initiator of the to-be-debugged business process, the method further comprises:
receiving a debugging message updated by an operation initiator;
replacing the current debugging message with the updated debugging message, and continuing to run the business flow to be debugged.
The operation initiator (i.e. client) of the service flow to be debugged can modify the debug message according to the debug condition, and returns the modified debug message (i.e. updated debug message) to continue to operate the service flow to be debugged, and execute the subsequent service flow debugging operation. Through the arrangement, the debugging message can be modified in the debugging process, and the service process debugging is continuously carried out according to the modified debugging message, so that the situation that more debugging messages need to be prepared in order to verify all branches and scenes in the service process due to single debugging data in the prior art is avoided, the service process debugging efficiency and the service process development efficiency are improved, and the complexity of the service process debugging is reduced.
Preferably, according to an embodiment of the present invention, the debug event further includes an analog service event; the step of executing the debug event to debug the business process further comprises:
and acquiring the simulated service type, and executing a corresponding simulated service event according to the simulated service type so as to debug the business process.
According to an embodiment of the present invention, the above simulation service types include simulation (Mock), non-simulation, and inquiry about whether simulation is performed. If the simulation service type is simulation, determining a target message from the debugging message information according to the Mock calling interface name and the Mock calling method name, and executing a corresponding simulation transaction event aiming at the target message so as to realize the debugging of the service flow; if the simulated service type is not simulated, directly calling an actual RPC (Remote Procedure Call Protocol, remotely calling a service) to realize the debugging of the business flow; if the simulation service type is the query whether to simulate, a consultation request needs to be sent to an operation initiator (i.e. a client) of the to-be-debugged service flow, and whether to adopt a simulation mode or an un-simulation mode is determined according to a feedback result of the client.
Further, according to an embodiment of the present invention, if the debug event in the embedded point is not triggered, the method further includes:
and continuing to operate the service flow to be debugged until the next routing node woven with the buried point or the operation of the service flow to be debugged is completed.
According to the technical scheme of the embodiment of the invention, because the service flow configuration information is acquired, the service flow route is created according to the service flow configuration information; obtaining debugging message information, and running a service flow to be debugged by using the debugging message in the debugging message information; when the operation is carried out to the routing node woven with the embedded point, judging whether to trigger a debugging event in the embedded point according to the debugging message information; if yes, the technical means of executing the debugging event to debug the business process is adopted, so that the problem that in the existing business process debugging method, because debugging can not be carried out on the business process node, the experience of developers is poor is solved; the method does not support message modification, influences the service flow debugging efficiency and the service flow debugging complexity, further causes the technical problem of low service flow development efficiency, further achieves the purpose of debugging aiming at service flow nodes, and improves the experience of developers; meanwhile, message modification is supported, so that the service flow debugging efficiency is improved, the service flow debugging complexity is reduced, and the technical effect of the service flow development efficiency is further improved.
FIG. 2a is a schematic diagram of a main business process of a business process debugging method according to a second embodiment of the present invention; FIG. 2b is a schematic diagram of a main architecture corresponding to the business process debugging method shown in FIG. 2 a; as shown in fig. 2a, the method for debugging a business process provided by the embodiment of the present invention mainly includes:
step S201, initializing a business process engine, creating a debugging instance by using the business process engine, and registering a handler interface into the debugging instance.
Specifically, after the business process debugging framework is started, the business process engine is initialized, a debugging instance is further created, a handler interface (callback interface) needing callback is registered in the debugging instance (so as to trigger a debugging callback event subsequently, and callback operation of corresponding data information is executed by using the callback interface). As shown in FIG. 2b, the debug Server is an interactive interface to the debug engine, and after the business process debug framework is started, the debug Server is used to initialize the business process engine (FlowEngine), create debug instance (DebugInstance), and register the handler interface in the DebugInstance. Each debugging instance corresponds to one thread, and a plurality of debugging instances are created, so that multi-thread debugging can be realized, and further, the service flow debugging efficiency is improved.
Step S202, obtaining business process configuration information, and creating a business process route according to the business process configuration information.
Through the arrangement, before the business process to be debugged is operated to carry out business process debugging, the business process route corresponding to the business process debugging is determined, so that the routing nodes can be debugged step by step later, the business process debugging efficiency is improved, and the experience of developers is improved.
Step S203, embedding a buried point at a target routing node of the business flow route, and adding a debugging event in the buried point.
Through the arrangement, in the process of arranging the business processes, the embedded points are woven in the corresponding positions (such as the positions of a plurality of routing nodes before the business processes are executed, before the nodes are executed, after the business processes are executed and the like) in a tangent plane mode, and meanwhile, corresponding debugging events are added into each embedded point according to the configuration information of the business processes. For example, callback debug events are added within the buried point before the routing node, simulated service events are added before the service node, multithreaded events are added before the multithreaded concurrent node, and so on.
According to the embodiment of the invention, in the process of arranging the business flow, aiming at one or more routing nodes with strong message relevance, as the configuration of the routing nodes influences whether the whole business flow can be normally executed, the embedded points can be not woven in the routing nodes with strong message relevance, but the embedded points can be used as a whole to finish debugging. Specifically, according to a specific real-time manner of the embodiment of the present invention, a hook technology (a special message processing mechanism that can monitor various event messages in a system or a process, intercept and process a message sent to a target window) is adopted to set a corresponding embedding point, so as to obtain one or more debug hooks.
Through the arrangement, in the process of arranging the business processes, embedding points are woven according to the business process configuration information, corresponding debugging events are added, and even for a relatively closed business process, gradual debugging of business process nodes (routing nodes) can be realized, so that the business process debugging and development efficiency is remarkably improved.
Step S204, obtaining debugging message information, and running the business flow to be debugged by using the debugging message in the debugging message information.
Specifically, according to the embodiment of the present invention, the step of obtaining debug message information and running a to-be-debugged service flow by using the debug message in the debug message information includes: obtaining debugging message information, adding the debugging message information into a debugging instance, and operating the business flow to be debugged by utilizing the debugging instance.
Because the debugging examples are in one-to-one correspondence with the threads, through the arrangement, the multi-thread debugging can be realized by respectively adding the debugging message information into different debugging examples, and the service flow debugging efficiency is further improved.
Further, according to an embodiment of the present invention, the debug message information includes a debug message, a buried point list, and a debug mode. Furthermore, the debug message information may further include simulation service configuration information such as a simulation service type, a simulation service instance, etc., so as to determine a corresponding simulation service event according to the simulation service configuration information later, so as to debug the service flow. As shown in FIG. 2b, the debug message information (debug Profile) includes a buried point list (BreakP point 0) and simulation service configuration information (Mock Config), and the debug Profile is added to the D ebugInstance to Run the to-be-debugged business Flow (Run Flow).
Step S205, when the router node is operated to the routing node woven with the embedded point, whether to trigger the debugging event in the embedded point is judged according to the debugging message information. If yes, triggering a debugging event in the embedded point, and executing step S207; if not, i.e. the debug event in the buried point is not triggered, the process goes to step S206.
Specifically, according to an embodiment of the present invention, the determining whether to trigger the debug event in the buried point according to the debug message information further includes: and acquiring current routing node information, and judging whether to trigger a debugging event according to the current routing node information, the buried point list and the debugging mode.
According to the embodiment of the invention, if the callback debug event is added in the embedded point, when the callback debug event is executed to the routing node woven with the embedded point, whether the callback debug event is triggered can be judged by comparing the embedded point list in the debug message information, the current debug mode and the current node information. Further, node information when the last debugging event is triggered can be obtained, and whether the debugging event is triggered or not is judged according to the current node information, the last node information, the embedded point list and the debugging mode.
As shown in fig. 2b, when the running is to a routing node with embedded point (debug hook), the F lowdebug model records the current routing node information, the node information when the last debug event is triggered, and determines whether to trigger the debug event according to the recorded information, the embedded point list and the current debug mode.
Step S206, the service flow to be debugged is continued to be operated until the next routing node woven with the buried point or the service flow to be debugged is operated.
Step S207, determining the triggered debug event type. For callback debug event, execute step S208; for the simulated service event, step S210 is performed.
According to the embodiment of the invention, the debug event types mainly comprise callback debug events and simulation service events; the system further comprises a multithreading event, and the type of the debugging event is only an example, and can be set according to actual situations when the system is specifically executed.
Step S208, obtaining a current debugging message and a current debugging event; and calling back the current debugging message and the current debugging event to an operation initiator of the business process to be debugged, so that the operation initiator can debug the business process according to the current debugging message and the current debugging event.
According to the embodiment of the invention, if the callback debugging event is triggered, the handler interface is called to callback the current debugging message and the current debugging event to the operation initiator (i.e. the client) of the business process to be debugged, so that the client can debug the business process according to the current debugging message and the corresponding debugging event. The setting is more fit with the habit of the developer, and is favorable for improving the development user experience.
Step S209, receiving a debug message updated by an operation initiator; replacing the current debugging message with the updated debugging message, and continuing to run the business flow to be debugged.
The operation initiator (i.e. client) of the service flow to be debugged can modify the debug message according to the debug condition, and returns the modified debug message (i.e. updated debug message) to continue to operate the service flow to be debugged, and execute the subsequent service flow debugging operation. Through the arrangement, the debugging message can be modified in the debugging process, and the service flow debugging is continuously carried out according to the modified debugging message, so that the service flow debugging efficiency and the service flow development efficiency are further improved.
Step S210, obtaining the simulation service type, and executing the corresponding simulation service event according to the simulation service type so as to debug the business process.
According to an embodiment of the present invention, the above simulation service types include simulation (Mock), non-simulation, and inquiry about whether simulation is performed. If the simulation service type is simulation, determining a target message from the debugging message information according to the Mock calling interface name and the Mock calling method name, and executing a corresponding simulation transaction event aiming at the target message so as to realize the debugging of the service flow; if the simulated service type is not simulated, directly calling an actual RPC (Remote Procedure Call Protocol, remotely calling a service) to realize the debugging of the business flow; if the simulation service type is the query whether to simulate, a consultation request needs to be sent to an operation initiator (i.e. a client) of the to-be-debugged service flow, and whether to adopt a simulation mode or an un-simulation mode is determined according to a feedback result of the client.
According to the technical scheme of the embodiment of the invention, because the service flow configuration information is acquired, the service flow route is created according to the service flow configuration information; obtaining debugging message information, and running a service flow to be debugged by using the debugging message in the debugging message information; when the operation is carried out to the routing node woven with the embedded point, judging whether to trigger a debugging event in the embedded point according to the debugging message information; if yes, the technical means of executing the debugging event to debug the business process is adopted, so that the problem that in the existing business process debugging method, because debugging can not be carried out on the business process node, the experience of developers is poor is solved; the method does not support message modification, influences the service flow debugging efficiency and the service flow debugging complexity, further causes the technical problem of low service flow development efficiency, further achieves the purpose of debugging aiming at service flow nodes, and improves the experience of developers; meanwhile, message modification is supported, so that the service flow debugging efficiency is improved, the service flow debugging complexity is reduced, and the technical effect of the service flow development efficiency is further improved.
FIG. 3 is a schematic diagram of main modules of a business process debugging device according to an embodiment of the present invention; as shown in fig. 3, the business process debugging device 300 provided in the embodiment of the present invention mainly includes:
The business process route creation module 301 is configured to obtain business process configuration information, and create a business process route according to the business process configuration information.
Specifically, according to the embodiment of the invention, after the business process debugging framework is started, the business process engine is initialized, a debugging instance is created by utilizing the business process engine, and a handler interface (callback interface) needing callback is registered in the debugging instance (so as to trigger a debugging callback event subsequently, and callback operation of corresponding data information is executed by utilizing the callback interface). And acquiring business process configuration information such as a business process file, a configuration file, a function file and the like by using a business process engine, and creating a business process route according to the business process configuration information.
Through the arrangement, before the business process to be debugged is operated to carry out business process debugging, the business process route corresponding to the business process debugging is determined, so that the routing nodes can be debugged step by step later, the business process debugging efficiency is improved, and the experience of developers is improved.
Further, according to an embodiment of the present invention, the above-mentioned business process debugging device 300 further includes a buried point embedding module, and after the step of creating the business process route, the buried point embedding module is configured to embed a buried point at a target route node of the business process route, and add a debugging event in the buried point.
Through the arrangement, in the process of arranging the business processes, the embedded points are woven in the corresponding positions (such as the positions of a plurality of routing nodes before the business processes are executed, before the nodes are executed, after the business processes are executed and the like) in a tangent plane mode, and meanwhile, corresponding debugging events are added into each embedded point according to the configuration information of the business processes. According to the embodiment of the invention, in the process of arranging the business flow, aiming at a plurality of routing nodes with strong message relevance, as the configuration of the plurality of routing nodes influences whether the whole business flow can be normally executed, embedded points can be not woven in the plurality of routing nodes with strong message relevance, but the embedded points can be used as a whole to finish debugging.
Through the arrangement, in the process of arranging the business processes, embedding points are woven according to the business process configuration information, corresponding debugging events are added, and even for a relatively closed business process, gradual debugging of business process nodes (routing nodes) can be realized, so that the business process debugging and development efficiency is remarkably improved.
The operation module 302 is configured to obtain the debug message information, and operate the service flow to be debugged by using the debug message in the debug message information.
Specifically, according to the embodiment of the present invention, the debug message information includes a debug message (having a certain message format), a buried point list (indicating a corresponding relationship between a routing node position corresponding to a buried point and a debug event added in the buried point), and a debug mode. Furthermore, the debug message information may further include simulation service configuration information such as a simulation service type, a simulation service instance, etc., so as to determine a corresponding simulation service event according to the simulation service configuration information later, so as to debug the service flow.
Further, according to an embodiment of the present invention, the operation module 302 is further configured to:
obtaining debugging message information, adding the debugging message information into a debugging instance, and operating the business flow to be debugged by utilizing the debugging instance.
The debugging examples are in one-to-one correspondence with the threads, and through the arrangement, the multi-thread debugging can be realized by respectively adding the debugging message information into different debugging examples, so that the service flow debugging efficiency is further improved.
The judging module 303 is configured to judge whether to trigger a debug event in the buried point according to the debug message information when running to the routing node woven with the buried point.
Specifically, according to an embodiment of the present invention, the determining module 303 is further configured to:
and acquiring current routing node information, and judging whether to trigger a debugging event according to the current routing node information, the buried point list and the debugging mode.
According to the embodiment of the invention, if the callback debug event is added in the embedded point, when the callback debug event is executed to the routing node woven with the embedded point, whether the callback debug event is triggered can be judged by comparing the embedded point list in the debug message information, the current debug mode and the current node information. Further, node information when the last debugging event is triggered can be obtained, and whether the debugging event is triggered or not is judged according to the current node information, the last node information, the embedded point list and the debugging mode.
The debug module 304 is configured to execute the debug event to perform the business process debugging if the debug event in the debug is triggered.
Specifically, according to an embodiment of the present invention, the debug event includes a callback debug event; the debug module 304 is configured to:
acquiring a current debugging message and a current debugging event;
and calling back the current debugging message and the current debugging event to an operation initiator of the business process to be debugged, so that the operation initiator can debug the business process according to the current debugging message and the current debugging event.
According to the embodiment of the invention, if the callback debugging event is triggered, the handler interface is called to callback the current debugging message and the current debugging event to the operation initiator (i.e. the client) of the business process to be debugged, so that the client can debug the business process according to the current debugging message and the corresponding debugging event. The setting is more fit with the habit of the developer, and is favorable for improving the development user experience.
Further, after the step of callback the current debug message and the current debug event to the operation initiator of the to-be-debugged business process, the above debug module 304 is further configured to:
receiving a debugging message updated by an operation initiator;
replacing the current debugging message with the updated debugging message, and continuing to run the business flow to be debugged.
The operation initiator (i.e. client) of the service flow to be debugged can modify the debug message according to the debug condition, and returns the modified debug message (i.e. updated debug message) to continue to operate the service flow to be debugged, and execute the subsequent service flow debugging operation. Through the arrangement, the debugging message can be modified in the debugging process, and the service flow debugging is continuously carried out according to the modified debugging message, so that the service flow debugging efficiency and the service flow development efficiency are further improved.
Preferably, according to an embodiment of the present invention, the debug event further includes an analog service event; the debug module 304 is also configured to:
and acquiring the simulated service type, and executing a corresponding simulated service event according to the simulated service type so as to debug the business process.
According to an embodiment of the present invention, the above simulation service types include simulation (Mock), non-simulation, and inquiry about whether simulation is performed. If the simulation service type is simulation, determining a target message from the debugging message information according to the Mock calling interface name and the Mock calling method name, and executing a corresponding simulation transaction event aiming at the target message so as to realize the debugging of the service flow; if the simulated service type is not simulated, directly calling an actual RPC (Remote Procedure Call Protocol, remotely calling a service) to realize the debugging of the business flow; if the simulation service type is the query whether to simulate, a consultation request needs to be sent to an operation initiator (i.e. a client) of the to-be-debugged service flow, and whether to adopt a simulation mode or an un-simulation mode is determined according to a feedback result of the client.
Further, according to an embodiment of the present invention, the above-mentioned business process debugging device 300 further includes a circulation module, where the circulation module is configured to:
And continuing to operate the service flow to be debugged until the next routing node woven with the buried point or the operation of the service flow to be debugged is completed. And if the operation is performed to the next routing node woven with the buried point, executing the operations corresponding to the judging module and the debugging module.
According to the technical scheme of the embodiment of the invention, because the service flow configuration information is acquired, the service flow route is created according to the service flow configuration information; obtaining debugging message information, and running a service flow to be debugged by using the debugging message in the debugging message information; when the operation is carried out to the routing node woven with the embedded point, judging whether to trigger a debugging event in the embedded point according to the debugging message information; if yes, the technical means of executing the debugging event to debug the business process is adopted, so that the problem that in the existing business process debugging method, because debugging can not be carried out on the business process node, the experience of developers is poor is solved; the method does not support message modification, influences the service flow debugging efficiency and the service flow debugging complexity, further causes the technical problem of low service flow development efficiency, further achieves the purpose of debugging aiming at service flow nodes, and improves the experience of developers; meanwhile, message modification is supported, so that the service flow debugging efficiency is improved, the service flow debugging complexity is reduced, and the technical effect of the service flow development efficiency is further improved.
Fig. 4 illustrates an exemplary system architecture 400 to which a business process debugging method or business process debugging apparatus of embodiments of the present invention may be applied.
As shown in fig. 4, a system architecture 400 may include terminal devices 401, 402, 403, a network 404, and a server 405 (this architecture is merely an example, and the components contained in a particular architecture may be tailored to the application specific case). The network 404 is used as a medium to provide communication links between the terminal devices 401, 402, 403 and the server 405. The network 404 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
A user may interact with the server 405 via the network 404 using the terminal devices 401, 402, 403 to receive or send messages or the like. Various communication client applications, such as a business process debugging class application, a data processing class application, etc. (only examples) may be installed on the terminal devices 401, 402, 403.
The terminal devices 401, 402, 403 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 405 may be a server providing various services, such as a server (by way of example only) that tests users with the terminal devices 401, 402, 403. The server may analyze and process the received data such as the service flow configuration information, and feed back the processing result (for example, a result corresponding to the service flow debugging—only an example) to the terminal device.
It should be noted that, the method for debugging a business process according to the embodiment of the present invention is generally executed by the server 405, and accordingly, the device for debugging a business process is generally disposed in the server 405.
It should be understood that the number of terminal devices, networks and servers in fig. 4 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 5, there is illustrated a schematic diagram of a computer system 500 suitable for use in implementing a terminal device or server in accordance with an embodiment of the present invention. The terminal device or server shown in fig. 5 is only an example, and should not impose any limitation on the functions and scope of use of the embodiments of the present invention.
As shown in fig. 5, the computer system 500 includes a Central Processing Unit (CPU) 501, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 502 or a program loaded from a storage section 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the system 500 are also stored. The CPU 501, ROM 502, and RAM 503 are connected to each other through a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
The following components are connected to the I/O interface 505: an input section 506 including a keyboard, a mouse, and the like; an output portion 507 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker, and the like; a storage portion 508 including a hard disk and the like; and a communication section 509 including a network interface card such as a LAN card, a modem, or the like. The communication section 509 performs communication processing via a network such as the internet. The drive 510 is also connected to the I/O interface 505 as needed. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 510 as needed so that a computer program read therefrom is mounted into the storage section 508 as needed.
In particular, according to embodiments of the present disclosure, the processes described above with reference to the business flow diagrams may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the methods shown in the business flow diagrams. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 509, and/or installed from the removable media 511. The above-described functions defined in the system of the present invention are performed when the computer program is executed by a Central Processing Unit (CPU) 501.
The computer readable medium shown in the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The business flow diagrams and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules involved in the embodiments of the present invention may be implemented in software or in hardware. The described modules may also be provided in a processor, for example, as: the processor comprises a business flow route creation module, an operation module, a judgment module and a debugging module. The names of these modules do not constitute a limitation on the module itself in some cases, and for example, the business process route creation module may also be described as "a module for acquiring business process configuration information and creating a business process route from the business process configuration information".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to include: acquiring business process configuration information, and creating a business process route according to the business process configuration information; obtaining debugging message information, and running a service flow to be debugged by using the debugging message in the debugging message information; when the operation is carried out to the routing node woven with the embedded point, judging whether to trigger a debugging event in the embedded point according to the debugging message information; if yes, executing the debugging event to debug the business flow.
According to the technical scheme of the embodiment of the invention, because the service flow configuration information is acquired, the service flow route is created according to the service flow configuration information; obtaining debugging message information, and running a service flow to be debugged by using the debugging message in the debugging message information; when the operation is carried out to the routing node woven with the embedded point, judging whether to trigger a debugging event in the embedded point according to the debugging message information; if yes, the technical means of executing the debugging event to debug the business process is adopted, so that the problem that in the existing business process debugging method, because debugging can not be carried out on the business process node, the experience of developers is poor is solved; the method does not support message modification, influences the service flow debugging efficiency and the service flow debugging complexity, further causes the technical problem of low service flow development efficiency, further achieves the purpose of debugging aiming at service flow nodes, and improves the experience of developers; meanwhile, message modification is supported, so that the service flow debugging efficiency is improved, the service flow debugging complexity is reduced, and the technical effect of the service flow development efficiency is further improved.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.

Claims (8)

1. The business process debugging method is characterized by comprising the following steps:
acquiring business process configuration information, and creating a business process route according to the business process configuration information;
obtaining debugging message information, and running a business process to be debugged by using the debugging message in the debugging message information;
when the operation is carried out to the routing node woven with the embedded point, judging whether to trigger a debugging event in the embedded point according to the debugging message information; the debug event comprises a callback debug event;
if yes, executing the debugging event to debug the business process; the method specifically comprises the following steps: acquiring a current debugging message and a current debugging event; and callback the current debugging message and the current debugging event to an operation initiator of the business process to be debugged, so that the operation initiator can debug the business process according to the current debugging message and the current debugging event.
2. The business process debugging method according to claim 1, wherein after the step of callback the current debugging message and the current debugging event to the operation initiator of the business process to be debugged, the method further comprises:
receiving the updated debugging message of the operation initiator;
replacing the current debugging message with the updated debugging message, and continuing to operate the business flow to be debugged.
3. The business process debugging method according to claim 1, wherein the debugging message information further comprises a buried point list and a debugging mode; judging whether to trigger the debugging event in the embedded point according to the debugging message information, and further comprising:
and acquiring current routing node information, and judging whether to trigger the debugging event according to the current routing node information, the buried point list and the debugging mode.
4. The business process debugging method of claim 1, wherein the debugging event further comprises a simulated service event; the executing the debug event to debug the business process further includes:
and acquiring the simulation service type, and executing a corresponding simulation service event according to the simulation service type so as to debug the service flow.
5. The business process debugging method of claim 1, wherein if a debugging event within the buried point is not triggered, the method further comprises:
and continuing to operate the service flow to be debugged until the next routing node woven with the buried point or the operation of the service flow to be debugged is completed.
6. A business process debugging device, comprising:
the business process route creation module is used for obtaining business process configuration information and creating business process routes according to the business process configuration information;
the operation module is used for acquiring the debugging message information and operating the business flow to be debugged by utilizing the debugging message in the debugging message information;
the judging module is used for judging whether to trigger a debugging event in the buried point according to the debugging message information when the judging module runs to the routing node woven with the buried point; the debug event comprises a callback debug event;
the debugging module is used for executing the debugging event to debug the business flow if the debugging event in the debugging is triggered; the method is particularly used for acquiring the current debugging message and the current debugging event; and callback the current debugging message and the current debugging event to an operation initiator of the business process to be debugged, so that the operation initiator can debug the business process according to the current debugging message and the current debugging event.
7. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs,
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-5.
8. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-5.
CN202110043923.5A 2021-01-13 2021-01-13 Business process debugging method and device Active CN113760723B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110043923.5A CN113760723B (en) 2021-01-13 2021-01-13 Business process debugging method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110043923.5A CN113760723B (en) 2021-01-13 2021-01-13 Business process debugging method and device

Publications (2)

Publication Number Publication Date
CN113760723A CN113760723A (en) 2021-12-07
CN113760723B true CN113760723B (en) 2024-04-16

Family

ID=78786396

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110043923.5A Active CN113760723B (en) 2021-01-13 2021-01-13 Business process debugging method and device

Country Status (1)

Country Link
CN (1) CN113760723B (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016173275A1 (en) * 2015-04-30 2016-11-03 深圳市中兴微电子技术有限公司 Debugging method, debugging device and storage medium
CN109862379A (en) * 2018-12-29 2019-06-07 北京奇艺世纪科技有限公司 A kind of log processing method, device, mobile terminal and storage medium
CN110120970A (en) * 2019-04-15 2019-08-13 钛马信息网络技术有限公司 Data processing method, device and gateway system based on car networking
CN110414842A (en) * 2019-07-30 2019-11-05 杭州一骑轻尘信息技术有限公司 Air control management method and system
CN111782534A (en) * 2020-07-03 2020-10-16 普信恒业科技发展（北京）有限公司 Business process monitoring method, device and system
CN111813648A (en) * 2019-06-03 2020-10-23 北京嘀嘀无限科技发展有限公司 Automatic testing method and device applied to App, storage medium and electronic equipment

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8122292B2 (en) * 2009-08-19 2012-02-21 Oracle International Corporation Debugging of business flows deployed in production servers
US8429622B2 (en) * 2010-04-15 2013-04-23 Oracle International Corporation Business process debugger with parallel-step debug operation

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016173275A1 (en) * 2015-04-30 2016-11-03 深圳市中兴微电子技术有限公司 Debugging method, debugging device and storage medium
CN109862379A (en) * 2018-12-29 2019-06-07 北京奇艺世纪科技有限公司 A kind of log processing method, device, mobile terminal and storage medium
CN110120970A (en) * 2019-04-15 2019-08-13 钛马信息网络技术有限公司 Data processing method, device and gateway system based on car networking
CN111813648A (en) * 2019-06-03 2020-10-23 北京嘀嘀无限科技发展有限公司 Automatic testing method and device applied to App, storage medium and electronic equipment
CN110414842A (en) * 2019-07-30 2019-11-05 杭州一骑轻尘信息技术有限公司 Air control management method and system
CN111782534A (en) * 2020-07-03 2020-10-16 普信恒业科技发展（北京）有限公司 Business process monitoring method, device and system

Also Published As

Publication number Publication date
CN113760723A (en) 2021-12-07

Similar Documents

Publication Publication Date Title
CN111124906B (en) Tracking method, compiling method and device based on dynamic embedded points and electronic equipment
CN112333096A (en) Micro-service traffic scheduling method and related components
CN111580926A (en) Model publishing method, model deploying method, model publishing device, model deploying device, model publishing equipment and storage medium
CN111695827B (en) Business process management method and device, electronic equipment and storage medium
WO2019075845A1 (en) Construction method and device for link call relationship, computer device and storage medium
CN112631919A (en) Comparison test method and device, computer equipment and storage medium
CN108121650B (en) Method and device for testing page user interface
CN113191889A (en) Wind control configuration method, configuration system, electronic device and readable storage medium
CN112597134A (en) Configuration method and device of distributed configuration center, electronic equipment and medium
CN113760723B (en) Business process debugging method and device
CN113282444A (en) Visualization method and device for business process debugging
CN116051031A (en) Project scheduling system, medium and electronic equipment
CN113392002B (en) Test system construction method, device, equipment and storage medium
CN111382058A (en) Service testing method and device, server and storage medium
CN111209018B (en) Method and device for processing application upgrading prompt information and electronic equipment
CN111080250B (en) Flow backspacing compensation method and device, storage medium and electronic equipment
CN112463616A (en) Chaos testing method and device for Kubernetes container platform
CN112965910A (en) Automatic regression testing method and device, electronic equipment and storage medium
CN112306723A (en) Operation information acquisition method and device applied to small program
CN112579447A (en) Browser testing method and device
CN113032004A (en) Method, apparatus and program product for managing development jobs in a development environment
CN111338968A (en) Project function module debugging method, device, medium and electronic equipment
CN112783753B (en) Testing method and device for stream data processing system
CN117130945B (en) Test method and device
CN112306324B (en) Information processing method, apparatus, device and medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant