CN112380129A

CN112380129A - Debugging method, device, equipment and medium suitable for docking agent system

Info

Publication number: CN112380129A
Application number: CN202011295069.3A
Authority: CN
Inventors: 齐秀
Original assignee: Ping An Puhui Enterprise Management Co Ltd
Current assignee: Chongqing Jinwei Technology Co ltd; Shenzhen Lian Intellectual Property Service Center
Priority date: 2020-11-18
Filing date: 2020-11-18
Publication date: 2021-02-19
Anticipated expiration: 2040-11-18
Also published as: CN112380129B

Abstract

The application relates to the technical field of artificial intelligence, and discloses a debugging method, a device, equipment and a medium suitable for a docking agent system, wherein the method is applied to a debugging system, and the debugging system is used for docking and debugging a consumption system, a service system and the agent system; the method comprises the steps that defect inspection is carried out on a simulation system code to obtain a defect inspection result, when the defect inspection result is failure, a target defect identifier, a target error reason and a target solution are determined according to the defect inspection result and a reason scheme model base, and if not, whether identification log information of successful butt joint exists in a printing log is judged; when the identification log information of successful butt joint exists in the printing log, acquiring a parameter receiving mode and calling configuration parameters according to the interface type; and performing joint debugging on the simulation system according to the simulation system code, the parameter receiving mode and the calling configuration parameter to obtain a simulation joint debugging result. Therefore, the docking process is simplified, and common problems in the docking process of the agent system are solved.

Description

Debugging method, device, equipment and medium suitable for docking agent system

Technical Field

The present application relates to the field of artificial intelligence technologies, and in particular, to a method, an apparatus, a device, and a medium for debugging a docking agent system.

Background

The proxy system is a tool system for integrated packaged request calling and response, has a unique calling mode, and is convenient for supervision and the like. Each agent system corresponds to a plurality of service systems and a plurality of consumption systems, the service systems provide interface calls for the agent systems, and the consumption systems provide call requests for the agent systems. The agent system packages the request of the consumption system and forwards the request to the service system, the service system feeds back the calling result to the agent system after realizing the service logic, and the agent system pushes the calling result to the consumption system.

The existing agent system has a set of regularized processes to guide manual testing of joint debugging to realize butt joint of the service system, the consumption system and the agent system, the butt joint process is complicated, errors are easy to occur, and the joint debugging efficiency is seriously reduced.

Disclosure of Invention

The application mainly aims to provide a debugging method, a debugging device, equipment and a debugging medium suitable for a butt joint agent system, and aims to solve the technical problems that in the prior art, butt joint of a service system, a consumption system and the agent system is realized through manual testing joint debugging based on a regularization process, the butt joint process is complicated, errors are prone to occur, and the joint debugging efficiency is low seriously.

In order to achieve the above object, the present application provides a debugging method suitable for a docking agent system, where the method is applied to a debugging system, the debugging system is used for docking and debugging a consumption system and a service system with the agent system, and the agent system is used for establishing a communication connection between the consumption system and the service system for requesting a call and a response; and the number of the first and second groups,

the method comprises the following steps:

acquiring a code checking request;

responding to the code inspection request, acquiring a simulation system code, performing defect inspection according to the simulation system code to obtain a defect inspection result, determining a target defect identifier, a target error reason and a target solution according to the defect inspection result and a reason scheme model library when the defect inspection result is failure, otherwise, acquiring a printing log, and judging whether identification log information of successful butt joint exists in the printing log;

when the printing log has identification log information of successful butt joint, acquiring an interface type, and acquiring a parameter receiving mode and calling configuration parameters according to the interface type;

acquiring a simulation joint debugging request;

and according to the simulation joint debugging request, carrying out simulation system joint debugging according to the simulation system code, the parameter receiving mode and the calling configuration parameter to obtain a simulation joint debugging result.

Further, the step of performing defect inspection according to the simulation system code to obtain a defect inspection result, when the defect inspection result is failure, determining a target defect identifier, a target error reason and a target solution according to the defect inspection result and the reason scheme model library, otherwise, obtaining a print log, and judging whether the print log has identification log information of successful docking includes:

carrying out defect inspection on a configuration item, JAR package dependence, a control layer and an interface abstract class on a simulation system code to obtain a defect inspection result;

when the defect inspection result is failure, obtaining the target defect identification according to the defect inspection result, and determining the target error reason and the target solution corresponding to the target defect identification from the reason scheme model library according to the target defect identification;

and when the defect inspection result is successful, acquiring a printing log, and judging whether the printing log has identification log information of successful butt joint.

Further, the step of performing defect inspection on the configuration item, JAR package dependency, control layer, and interface abstract class on the simulation system code to obtain the defect inspection result, and when the defect inspection result is a failure, obtaining the target defect identifier according to the defect inspection result includes:

acquiring a configuration file to be inspected from the simulation system code, performing configuration item defect inspection according to the configuration file to be inspected to obtain a configuration item inspection result, and determining the target defect identifier according to the configuration item inspection result when the configuration item inspection result is failure;

performing JAR package dependence inspection according to a simulation system code to obtain a JAR package dependence inspection result, and determining the target defect identifier according to the JAR package dependence inspection result when the JAR package dependence inspection result is failed;

performing control layer defect inspection according to the simulation system code to obtain a control layer defect inspection result, and determining the target defect identifier according to the control layer defect inspection result when the control layer defect inspection result is failure;

obtaining a JAR package list of the proxy system, checking a JAR package path name according to a simulation system code and the JAR package list to obtain an interface abstract type checking result, and determining the target defect identifier according to the interface abstract type checking result when the interface abstract type checking result is failure.

Further, the step of obtaining the configuration file to be inspected from the simulation system code, performing configuration item defect inspection according to the configuration file to be inspected to obtain a configuration item inspection result, and determining the target defect identifier according to the configuration item inspection result when the configuration item inspection result is a failure, includes:

acquiring the configuration file to be checked from the simulation system code;

acquiring standard configuration data according to the configuration file to be checked;

comparing the configuration file to be checked with the standard configuration data to obtain a configuration item checking result;

and when the configuration item inspection result is failure, determining the target defect identifier according to the configuration item inspection result.

Further, the step of performing JAR package dependency check according to the simulation system code to obtain a JAR package dependency check result, and when the JAR package dependency check result is a failure, determining the target defect identifier according to the JAR package dependency check result includes:

obtaining a JAR packet list of the proxy system;

performing inclusion cover inspection according to a simulation system code and a JAR packet list of the proxy system to obtain an inclusion cover inspection result;

when the inclusion cover inspection result is partial coverage, determining the target defect identifier according to the inclusion cover inspection result;

checking whether a warehouse of a simulation system code contains the version of the JAR package in the JAR package list of the proxy system to obtain a JAR package version checking result;

and when the JAR package version inspection results are different, determining the target defect identifier according to the JAR package version inspection result.

Further, the step of performing control layer defect inspection according to the simulation system code to obtain a control layer defect inspection result, and when the control layer defect inspection result is failure, determining the target defect identifier according to the control layer defect inspection result includes:

acquiring a control layer code from a simulation system code;

and performing packet guide verification on the preset annotation file of the control layer code to obtain a control layer defect inspection result, and determining the target defect identifier according to the control layer defect inspection result when the control layer defect inspection result is failure.

Further, the steps of obtaining an interface type when the printing log has identification log information of successful docking, obtaining a parameter receiving mode according to the interface type, and calling a configuration parameter include:

acquiring host information of a production environment, host information of a test environment and host information of an agent system;

performing firewall opening inspection and remote connection inspection according to the host information of the agent system and the host information of the production environment by adopting a Telnet login mode to obtain a production environment firewall opening result and a production environment remote connection inspection result;

performing firewall opening inspection and remote connection inspection according to the host information of the agent system and the host information of the test environment by adopting a Telnet login mode to obtain a test environment firewall opening result and a test environment remote connection inspection result;

when the production environment firewall opening result, the production environment remote connection inspection result, the test environment firewall opening result and the test environment remote connection inspection result are successful, an interface type is obtained, a parameter receiving mode is obtained according to the interface type, and a calling configuration parameter is obtained according to the parameter receiving mode.

The application also provides a debugging device suitable for the butt joint agent system, the device is applied to a debugging system, the debugging system is used for butt joint debugging of a consumption system, a service system and the agent system, and the agent system is used for establishing communication connection for requesting calling and responding between the consumption system and the service system; and the number of the first and second groups,

the device comprises:

the request acquisition module is used for acquiring a code check request;

the defect inspection module is used for responding to the code inspection request, acquiring a simulation system code, performing defect inspection according to the simulation system code to obtain a defect inspection result, determining a target defect identifier, a target error reason and a target solution according to the defect inspection result and the reason scheme model library when the defect inspection result is failure, and otherwise acquiring a print log and judging whether identification log information of successful butt joint exists in the print log;

and the simulation joint debugging module is used for acquiring an interface type when identification log information of successful butt joint exists in the printing log, acquiring a parameter receiving mode and a calling configuration parameter according to the interface type, acquiring a simulation joint debugging request, and performing simulation system butt joint debugging according to the simulation joint debugging request and the simulation system code, the parameter receiving mode and the calling configuration parameter to obtain a simulation joint debugging result.

The present application further proposes a computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the steps of any of the above methods when executing the computer program.

The present application also proposes a computer-readable storage medium having stored thereon a computer program which, when being executed by a processor, carries out the steps of the method of any of the above.

According to the debugging method, the debugging device, the debugging equipment and the debugging medium, which are suitable for the docking agent system, the defect inspection of the simulation system codes is automatically realized by responding to the code inspection request, the docking process is simplified, the errors of the simulation system codes are rapidly checked through the code defect inspection, and the joint debugging efficiency is improved; error reasons and solutions are automatically given through a reason scheme model library, and developers are helped to quickly position and troubleshoot problems; by automatically simulating the butt joint debugging of the consumption system and/or the service system and the agent system, common problems in the butt joint process of the agent system and the agent system can be checked, the workload of development and testing is reduced, and the joint debugging efficiency is improved.

Drawings

Fig. 1 is a schematic flowchart of a debugging method applied to a docking agent system according to an embodiment of the present application;

fig. 2 is a schematic block diagram illustrating a configuration of a debugging apparatus suitable for a docking agent system according to an embodiment of the present application;

fig. 3 is a block diagram illustrating a structure of a computer device according to an embodiment of the present application.

The objectives, features, and advantages of the present application will be further described with reference to the accompanying drawings.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

In order to solve the technical problems that in the prior art, a service system, a consumption system and an agent system are butted through manual testing joint debugging based on a regularized flow, the butt joint flow is complicated, errors are prone to occurring, and joint debugging efficiency is low seriously. The debugging method suitable for the docking agent system is applied to a debugging system, the simulation system codes are subjected to defect inspection, and after the defect inspection is successful, the docking joint debugging of the consumption system and/or the service system and the agent system is automatically simulated, so that the common problems in the docking process of the rapid inspection and agent system are realized, the workload of development and testing is reduced, and the joint debugging efficiency is improved.

Referring to fig. 1, the debugging method applicable to the docking agent system is applied to a debugging system, the debugging system is used for docking and debugging a consumption system and a service system with the agent system, and the agent system is used for establishing a communication connection for requesting call and response between the consumption system and the service system; and the number of the first and second groups,

the method comprises the following steps:

s1: acquiring a code checking request;

s2: responding to the code inspection request, acquiring a simulation system code, performing defect inspection according to the simulation system code to obtain a defect inspection result, determining a target defect identifier, a target error reason and a target solution according to the defect inspection result and a reason scheme model library when the defect inspection result is failure, otherwise, acquiring a printing log, and judging whether identification log information of successful butt joint exists in the printing log;

s3: when the printing log has identification log information of successful butt joint, acquiring an interface type, and acquiring a parameter receiving mode and calling configuration parameters according to the interface type;

s4: acquiring a simulation joint debugging request;

s5: and according to the simulation joint debugging request, carrying out simulation system joint debugging according to the simulation system code, the parameter receiving mode and the calling configuration parameter to obtain a simulation joint debugging result.

The embodiment realizes automatic defect inspection of the simulation system code by responding to the code inspection request, simplifies the butt joint flow, quickly checks the error of the simulation system code by the code defect inspection, and improves the joint debugging efficiency; error reasons and solutions are automatically given through a reason scheme model library, and developers are helped to quickly position and troubleshoot problems; by automatically simulating the butt joint debugging of the consumption system and/or the service system and the agent system, common problems in the butt joint process of the agent system and the agent system can be checked, the workload of development and testing is reduced, and the joint debugging efficiency is improved.

The agent system is used for receiving a consumption calling request sent by the consumption system, sending a service calling request to the service system according to the consumption calling request, receiving a service calling result sent by the service system according to the service calling request, and sending the service calling result to the consumption system.

For S1, a code check request sent by the user is obtained.

The code check request refers to a request for checking a code of the simulation system.

Simulation system code includes, but is not limited to: consumption system simulation code, service system simulation code.

The consumption system simulation code is debugging code for simulating the consumption system.

The service system simulation code is debugging code for simulating the service system.

And S2, responding to the code inspection request to trigger a code inspection mechanism, reading the simulation system code from the database of the debugging system, performing defect inspection according to the simulation system code to obtain a defect inspection result, determining a target defect identifier according to the defect inspection result when the defect inspection result is failure, and searching the target defect identifier in a reason scheme model library to obtain a target error reason and a target solution corresponding to the target defect identifier.

The step of judging whether the printing log has the identification log information of successful docking comprises the following steps: judging whether proxy system configuration information exists in the printing log, if so, indicating that proxy system configuration in the simulation system code is successful, determining that identification log information of successful butt joint exists in the printing log, otherwise, determining that identification log information of successful butt joint does not exist in the printing log. It is understood that the identifying log information may also be other information, and is not specifically limited herein.

The agent system configuration information is information to be configured when interfacing with the agent system.

Target defect identification, i.e. defect identification. The defect identifier may be a defect ID, a defect name, or the like that uniquely identifies a defect.

The target error cause, which is also the error cause, is the cause of the occurrence of such a defect.

The target solution, which is also a solution, is an instructive solution to address this deficiency.

For S3, the step of obtaining the interface type when the print log has the identification log information of successful docking, obtaining the parameter receiving mode and calling the configuration parameter according to the interface type includes: when the identification log information of successful butt joint exists in the printing log, performing firewall opening inspection and remote connection inspection according to the simulation system code to obtain a firewall opening inspection result and a remote connection inspection result; and when the firewall opening inspection result and the remote connection inspection result are both successful, acquiring an interface type, acquiring a parameter receiving mode according to the interface type, and acquiring a calling configuration parameter according to the parameter receiving mode. Therefore, automatic firewall opening inspection and remote connection inspection are realized, and firewall opening inspection and remote connection inspection are not needed when online deployment is not needed, so that the online deployment time is shortened.

Preferably, the steps of obtaining an interface type when the printing log has identification log information of successful docking, obtaining a parameter receiving mode and calling a configuration parameter according to the interface type further include: and when the printing log has identification log information of successful butt joint, directly acquiring an interface type, and acquiring a parameter receiving mode and calling configuration parameters according to the interface type. Thereby simplifying the flow of debugging the system.

The interface type may be user input or may be default settings for the debugging system.

Interface types include, but are not limited to: POST interface, GET interface. The POST interface is used for receiving a POST request (request for data), and the GET interface is used for receiving a GET request (request for sending data).

The parameter receiving mode can be input by a user or set by default of the debugging system.

The parameter receiving method includes but is not limited to: and (4) visualizing the configuration. And visual configuration is realized by performing parameter configuration in a webpage.

Invoking configuration parameters includes, but is not limited to: calling the return information and calling the application information. The call return information is used as a service call result when simulating the service system. The calling application information is sent to the agent system along with the service calling request when the consumption system is simulated.

For S4, the simulated joint tune request sent by the user is obtained. Wherein, the user can trigger the simulation joint debugging request by one-click through the button.

The simulation joint debugging request refers to a request for simulating the joint debugging between a consumption system and/or a service system and an agent system.

The simulation joint debugging request comprises the following steps: the method comprises the steps of simulating a consumption system joint debugging request, a service system joint debugging request and a debugging system self-calling request.

The debugging system self-calling request is a request for simultaneously simulating a consumption system and a service system to carry out joint debugging.

And S5, adopting a webpage debugging tool to send a request mode to simulate the butt joint of the service system and/or the consumption system with the service system according to the simulation system code, the parameter receiving mode and the call configuration parameter, and obtaining a simulation joint debugging result after the butt joint is completed.

Web page debugging tools include, but are not limited to: postman (a plug-in) is used to send HTTP requests.

The HTTP request refers to a request message from a client to a server. The method comprises the following steps: in the message head line, the request method for the resource, the identifier of the resource and the protocol used.

The simulation joint debugging result comprises the following steps: the simulation service system and the agent system coordinate results, the simulation consumption system and the agent system coordinate results, and the simulation service system and the consumption system and the agent system coordinate results.

The joint debugging result of the simulation service system and the agent system refers to the joint debugging result of the simulation service system and the agent system of the debugging system, and the consumption system adopts a system of a production environment at the moment.

The joint debugging result of the simulated consumption system and the agent system refers to the joint debugging result of the simulated consumption system and the agent system of the debugging system, and the service system adopts a system of a production environment at the moment.

The joint debugging result of the simulation service system, the consumption system and the agent system refers to the joint debugging result of the simulation service system, the consumption system and the agent system simultaneously.

The joint debugging result of the simulation service system and the agent system comprises the following steps: success or failure. The joint debugging result of the simulated consumption system and the agent system comprises the following steps: success or failure. The joint debugging result of the service planning system, the consumption system and the agent system comprises the following steps: success or failure.

Preferably, the step of performing the joint debugging of the simulation system according to the simulation joint debugging request, the simulation system code, the parameter receiving manner, and the calling configuration parameter to obtain a simulation joint debugging result includes:

simulating the simulation joint debugging request by adopting an IDEA (integrated environment developed by Java programming language) editor, integrating simulation system codes into a simulation calling plug-in the IDEA editor, and performing joint debugging by adopting the simulation calling plug-in according to the parameter receiving mode and the calling configuration parameter simulation system to obtain a simulation joint debugging result. Thereby enabling a simulated invocation of the service system service request from the consuming system through the proxy system.

Preferably, the step of performing the joint debugging of the simulation system according to the simulation joint debugging request, the simulation system code, the parameter receiving manner, and the calling configuration parameter to obtain a simulation joint debugging result further includes:

and when the simulation joint debugging request is a debugging system self-calling request, simultaneously simulating the consumption system and the service system according to self-calling configuration parameters carried by the proxy system self-calling request to obtain a simulation service system and proxy system joint debugging result and a consumption system and proxy system joint debugging result, wherein URL (uniform resource locator) data of the calling configuration parameters are changed into URL addresses of the debugging system to obtain the self-calling configuration parameters.

And when the simulation joint debugging result is failure, determining the target defect identification according to the simulation joint debugging result, and searching the target defect identification in the reason scheme model base to obtain a target error reason and a target solution corresponding to the target defect identification.

In an embodiment, the performing defect inspection according to the simulation system code to obtain a defect inspection result, determining a target defect identifier, a target error reason, and a target solution according to the defect inspection result and the reason scheme model library when the defect inspection result is failure, otherwise, obtaining a print log, and determining whether the print log has identification log information of successful docking, includes:

s21: carrying out defect inspection on a configuration item, JAR package (Java file) dependence, a control layer and an interface abstract class on a simulation system code to obtain a defect inspection result;

s22: when the defect inspection result is failure, obtaining the target defect identification according to the defect inspection result, and determining the target error reason and the target solution corresponding to the target defect identification from the reason scheme model library according to the target defect identification;

s23: and when the defect inspection result is successful, acquiring a printing log, and judging whether the printing log has identification log information of successful butt joint.

In the embodiment, the defect inspection of configuration items, JAR package dependence, control layers and interface abstract classes is carried out on the simulation system codes, so that the defect inspection of the simulation system codes is automatically realized, the butt joint process is simplified, the errors of the simulation system codes are rapidly checked through the code defect inspection, and the joint debugging efficiency is improved; error reasons and solutions are automatically given through the reason scheme model library, and developers are helped to quickly position and troubleshoot problems.

JAR package, i.e. JAR file, Java archive file, english: java Archive, a software package file format, is commonly used to aggregate a large number of Java class files, associated metadata and resource (text, pictures, etc.) files into one file in order to develop Java platform applications or libraries. The JAR file is an archived file, constructed in ZIP format, with JAR as the file extension. The user can create or extract a JAR file using the JDK's own JAR commands. Other zip compression tools may also be used, although the order of entries in the zip file header is important when compressing, as Manifest files often need to be placed first. The filename within the JAR file is Unicode text.

And S21, performing defect inspection on the configuration item, JAR package dependence, the control layer and the interface abstract class of the analog system code, and determining that the defect inspection result is failure when at least one defect exists, otherwise, determining that the defect inspection result is success.

And defect detection of configuration items, JAR package dependence, a control layer and interface abstract classes can be performed in sequence. It is understood that the configuration items, JAR package dependencies, control layers, and interface abstraction classes may be checked for defects in other sequences, which are not specifically limited herein.

For S22, when the defect inspection result is failure, determining a defect identifier according to the failure defect inspection result, and taking the determined defect identifier as a target defect identifier; and searching the target defect identification from the reason scheme model library, taking the error reason corresponding to the defect identification searched in the reason scheme model library as the target error reason corresponding to the target defect identification, and taking the solution corresponding to the defect identification searched in the reason scheme model library as the target solution corresponding to the target defect identification.

For S23, when the defect check result is successful, it means that the configuration item of the simulation system code, JAR package dependency, control layer, and interface abstraction class have no defect, at this time, the identifying log information may be printed through the print log, and whether the identifying log information of successful docking exists in the print log is determined by obtaining the print log, so that the identifying log information is verified through the print log.

In an embodiment, the step of performing defect inspection on the configuration item, the JAR package dependency, the control layer, and the interface abstract class on the simulation system code to obtain the defect inspection result, and when the defect inspection result is a failure, obtaining the target defect identifier according to the defect inspection result includes:

s221: acquiring a configuration file to be inspected from the simulation system code, performing configuration item defect inspection according to the configuration file to be inspected to obtain a configuration item inspection result, and determining the target defect identifier according to the configuration item inspection result when the configuration item inspection result is failure;

s222: performing JAR package dependence inspection according to a simulation system code to obtain a JAR package dependence inspection result, and determining the target defect identifier according to the JAR package dependence inspection result when the JAR package dependence inspection result is failed;

s223: performing control layer defect inspection according to the simulation system code to obtain a control layer defect inspection result, and determining the target defect identifier according to the control layer defect inspection result when the control layer defect inspection result is failure;

s224: obtaining a JAR package list of the proxy system, checking a JAR package path name according to a simulation system code and the JAR package list to obtain an interface abstract type checking result, and determining the target defect identifier according to the interface abstract type checking result when the interface abstract type checking result is failure.

The embodiment realizes the defect detection of configuration items, JAR package dependence, control layers and interface abstract classes, realizes the automatic defect detection of the simulation system codes, simplifies the butt joint flow, quickly checks the errors of the simulation system codes through the code defect detection, and improves the joint debugging efficiency.

For S221, scanning the analog system code, reading the configuration file, taking the read configuration file as a configuration file to be inspected, performing defect inspection on configuration information in the configuration file to be inspected, determining that the inspection result of the configuration item is successful when all the configuration information is inspected to be correct, and otherwise, determining that the inspection result of the configuration item is failed; and when the configuration item check result is failure, taking the defect mark corresponding to the error configuration information as a target defect mark.

For S222, it is checked according to the simulation system code whether the JAR package that should be introduced is already covered in the file on which the project depends, and whether there is a JAR package of a corresponding version in the repository of the simulation system code. Determining that the JAR packet dependence check result is failure when the unconverged JAR packet exists, otherwise determining that the JAR packet dependence check result is success; and when the dependency check result of the JAR packet is failure, taking the defect identifier corresponding to the uncovered JAR packet as the target defect identifier. Determining that the JAR package dependence check result is failure when the unconverged JAR package version exists, otherwise determining that the JAR package dependence check result is success; and when the dependency check result of the JAR packet is failure, taking the defect identifier corresponding to the unconvered JAR packet version as the target defect identifier.

JAR packages that should be introduced include: JAR packages for proxy systems and JAR packages for microservices.

The warehouse, which is the underlying support binder, provides a series of dependencies.

For S223, a control layer (e.g., a Controller) that provides services to the outside is read from the simulation system code, the control layer traverses a folder where the control layer is located under a specific folder, performs a packet guidance verification, and determines that a control layer defect inspection result is successful when the packet guidance verification is successful, otherwise determines that the control layer defect inspection result is failed. And when the control layer defect inspection result is failure, taking the defect identifier of the packet guide verification failure as a target defect identifier.

Packet-guided checks include, but are not limited to: and checking the leading packet of the service mapping packet.

And S224, acquiring a JAR package list from the proxy system, acquiring a JAR package path name of a JAR package in the simulation system code, checking whether the JAR package path name of the JAR package in the simulation system code is the same as the JAR package path name in the JAR package list, determining that the interface abstract class checking result is successful when the JAR package path names are the same, and otherwise determining that the interface abstract class checking result is failed. And when the interface abstract class check result is failure, taking the corresponding defect identifier with different JAR package path names as a target defect identifier.

In an embodiment, the step of obtaining the configuration file to be inspected from the simulation system code, performing configuration item defect inspection according to the configuration file to be inspected to obtain a configuration item inspection result, and determining the target defect identifier according to the configuration item inspection result when the configuration item inspection result is a failure includes:

s2211: acquiring the configuration file to be checked from the simulation system code;

s2212: acquiring standard configuration data according to the configuration file to be checked;

s2213: comparing the configuration file to be checked with the standard configuration data to obtain a configuration item checking result;

s2214: and when the configuration item inspection result is failure, determining the target defect identifier according to the configuration item inspection result.

According to the method and the device, the configuration item defect inspection of the analog system code is automatically carried out, the butt joint process is simplified, the errors of the analog system code are rapidly checked through the configuration item defect inspection, and the joint debugging efficiency is improved.

For S2211, acquiring the configuration file to be checked from the simulation system code;

for S2212, when the simulation system code is the consumption system simulation code, the configuration file to be verified is the configuration file of the consumption system, and the consumption system standard configuration data is obtained from the agent system; when the simulation system code is the service system simulation code, the configuration file to be verified is the configuration file of the service system, and the standard configuration data of the service system is obtained from the agent system; when the simulation system code simultaneously comprises a consumption system simulation code and a service system simulation code, the configuration file to be verified comprises a configuration file of a consumption system and a configuration file of a service system, and consumption system standard configuration data and service system standard configuration data are obtained from the agent system.

And S2213, when the simulation system code is the consumption system simulation code, comparing the configuration file to be checked with the consumption system standard configuration data to obtain a comparison result of the consumption system configuration items, if the configuration item comparison result is the same, determining that the comparison result of the consumption system configuration items is successful, otherwise, determining that the comparison result of the consumption system configuration items is failed.

And when the simulation system code is the service system simulation code, comparing the configuration file to be checked with the standard configuration data of the service system to obtain a comparison result of the configuration items of the service system, if the configuration items of the service system are the same, determining that the comparison result of the configuration items of the service system is successful, otherwise, determining that the comparison result of the configuration items of the service system is failed.

When the simulation system code simultaneously comprises a consumption system simulation code and a service system simulation code, comparing the consumption system standard configuration data and the consumption system standard configuration data in the configuration file to be checked to obtain a consumption system configuration item comparison result, if the consumption system configuration item comparison result is the same, determining that the success is the success, otherwise, determining that the failure is the failure; and then comparing the service system standard configuration data and the service system standard configuration data in the configuration file to be checked to obtain a service system configuration item comparison result, if the service system configuration item comparison result is the same as the service system configuration item comparison result, determining that the service system configuration item comparison result is successful, otherwise, determining that the service system configuration item comparison result is failed.

For S2214, when the simulation system code is the consumption system simulation code, taking the defect identifier corresponding to the different consumption system configuration items as the target defect identifier; when the simulation system code is the service system simulation code, taking the defect identification corresponding to different service system configuration items as the target defect identification; and when the simulation system code simultaneously comprises a consumption system simulation code and a service system simulation code, taking the defect identifications corresponding to different consumption system configuration items as target defect identifications, and taking the defect identifications corresponding to different service system configuration items as target defect identifications.

In an embodiment, the performing JAR package dependency check according to the simulation system code to obtain a JAR package dependency check result, and when the JAR package dependency check result is a failure, determining the target defect identifier according to the JAR package dependency check result includes:

s2221: obtaining a JAR packet list of the proxy system;

s2222: performing inclusion cover inspection according to a simulation system code and a JAR packet list of the proxy system to obtain an inclusion cover inspection result;

s2223: when the inclusion cover inspection result is partial coverage, determining the target defect identifier according to the inclusion cover inspection result;

s2224: checking whether a warehouse of a simulation system code contains the version of the JAR package in the JAR package list of the proxy system to obtain a JAR package version checking result;

s2225: and when the JAR package version inspection results are different, determining the target defect identifier according to the JAR package version inspection result.

According to the method and the device, JAR package dependence check is automatically carried out on the analog system codes, the butt joint process is simplified, errors of the analog system codes are rapidly checked through the JAR package dependence check, and joint debugging efficiency is improved.

For S2221, a JAR package list is obtained from the proxy system.

And for S2222, searching each JAR packet in the JAR packet list of the proxy system in the simulation system code, determining that the inclusion cover inspection result is partial coverage when the JAR packet in the JAR packet list of the proxy system cannot be found in the simulation system code, and otherwise determining that the inclusion cover inspection result is full coverage. When the simulation system code does not contain all JAR packages in the JAR package list of the proxy system, the introduction of functions or methods is influenced, and a corresponding logic processing method cannot be provided.

For S2223, when the inclusion cover check result is partial coverage, the JAR packet in the JAR packet list of the proxy system cannot find the corresponding defect identifier in the simulation system code as the target defect identifier.

For step S2224, the version of each JAR package in the JAR package list of the proxy system is searched in the simulation system code, and when the version of the JAR package in the JAR package list of the proxy system cannot be found in the simulation system code, the JAR package version check results are determined to be different, otherwise, the JAR package version check results are determined to be the same.

For S2225, when the JAR package version check results are different, the version of the JAR package in the JAR package list of the proxy system cannot find the corresponding defect identifier in the simulation system code as the target defect identifier.

In an embodiment, the step of performing control layer defect inspection according to the simulation system code to obtain a control layer defect inspection result, and when the control layer defect inspection result is a failure, determining the target defect identifier according to the control layer defect inspection result includes:

s2231: acquiring a control layer code from a simulation system code;

s2232: and performing packet guide verification on the preset annotation file of the control layer code to obtain a control layer defect inspection result, and determining the target defect identifier according to the control layer defect inspection result when the control layer defect inspection result is failure.

The embodiment realizes the automatic control layer defect inspection of the analog system codes, simplifies the butt joint flow, rapidly checks the errors of the analog system codes through the control layer defect inspection, and improves the joint debugging efficiency.

For S2231, the simulation system code is scanned to obtain the control layer code.

For S2232, performing packet guiding verification of a service mapping packet on the preset annotation file of the control layer code to obtain a control layer defect inspection result; and when the control layer defect inspection result is failure, taking the defect identifier corresponding to the unsuccessful guide packet as a target defect identifier when the control layer defect inspection result is failure. It will be appreciated that the guided packet check may also check other packets.

For example, a Controller (i.e. control layer code) for providing an external service is acquired from the simulation system code, a file where the Controller is located is traversed, package guide check is performed on the file containing the @ PA _ API annotation, and whether the file exists or not is identified

The method includes the steps of determining that a control layer defect inspection result is failed when there is no instruction, and otherwise determining that the control layer defect inspection result is successful, wherein the instruction is a service mapping packet and is not specifically limited herein.

In an embodiment, the step of obtaining an interface type when the print log has identification log information of successful docking, obtaining a parameter receiving mode according to the interface type, and calling a configuration parameter includes:

s31: acquiring host information of a production environment, host information of a test environment and host information of an agent system;

s32: performing firewall opening inspection and remote connection inspection according to the host information of the agent system and the host information of the production environment by adopting a Telnet login mode to obtain a production environment firewall opening result and a production environment remote connection inspection result;

s33: performing firewall opening inspection and remote connection inspection according to the host information of the agent system and the host information of the test environment by adopting a Telnet login mode to obtain a test environment firewall opening result and a test environment remote connection inspection result;

s34: when the production environment firewall opening result, the production environment remote connection inspection result, the test environment firewall opening result and the test environment remote connection inspection result are successful, an interface type is obtained, a parameter receiving mode is obtained according to the interface type, and a calling configuration parameter is obtained according to the parameter receiving mode.

The embodiment realizes automatic firewall verification, further reduces the workload of development and testing, and improves joint debugging efficiency.

At S31, the host information of the production environment, the host information of the test environment, and the host information of the proxy system may be acquired at the same time, or the host information of the production environment, the host information of the test environment, and the host information of the proxy system may be acquired in another order.

The host information of the production environment can be obtained from the database, and the host information of the production environment can also be obtained from the configuration information maintenance unified management system.

The host information of the test environment can be obtained from the database, and the host information of the test environment can also be obtained from the configuration information maintenance unified management system.

The host information of the agent system can be obtained from the agent system, the host information of the agent system can also be obtained from a database, and the host information of the agent system can also be obtained from a configuration information maintenance unified management system.

For S32, judging whether the firewall is opened or not by adopting a Telnet login mode according to the host information of the proxy system and the host information of the production environment, and determining that the firewall opening result of the production environment is successful when the firewall is opened, or determining that the firewall opening result of the production environment is failed; and judging whether the remote connection can be successfully connected or not according to the host information of the agent system and the host information of the production environment by adopting a Telnet login mode, determining that the remote connection inspection result of the production environment is successful when the remote connection can be successfully connected or not, and determining that the remote connection inspection result of the production environment is failed if the remote connection inspection result of the production environment is not successful.

The Telnet login mode is a remote login mode adopting a Telnet protocol.

The Telnet protocol is a member of the TCP/IP suite of protocols, and is the standard protocol and the main mode for Internet Telnet services. It provides the user with the ability to do remote host work on the local computer. The Telnet program is used on the end user's computer and is used to connect to the server. The end user can enter commands in the Telnet program that will run on the server as if entered directly on the server's console. The server can be controlled locally. To start a Telnet session, a username and password must be entered to log in to the server. Telnet is a commonly used method of remotely controlling a Web server.

For S33, judging whether the firewall is opened or not by adopting a Telnet login mode according to the host information of the proxy system and the host information of the test environment, and determining that the firewall opening result of the test environment is successful when the firewall is opened, or determining that the firewall opening result of the test environment is failed; and judging whether the remote connection can be successfully connected or not according to the host information of the agent system and the host information of the test environment by adopting a Telnet login mode, determining that the test environment remote connection test result is successful when the remote connection can be successfully connected or not, and otherwise determining that the test environment remote connection test result is failed.

For S34, when the production environment firewall opening result, the production environment remote connection inspection result, the test environment firewall opening result and the test environment remote connection inspection result are all successful, the step of obtaining the interface type, obtaining a parameter receiving mode according to the interface type and obtaining a calling configuration parameter according to the parameter receiving mode is executed, so that the firewall and remote connection inspection required for online deployment after joint debugging is reduced, and the online deployment time is shortened.

Referring to fig. 2, the present application further proposes a debugging apparatus suitable for a docking agent system, where the apparatus is applied to a debugging system, the debugging system is used for docking and debugging a consumption system and a service system with the agent system, and the agent system is used for establishing a communication connection between the consumption system and the service system for requesting invocation and response; and the number of the first and second groups,

the device comprises:

a request obtaining module 100, configured to obtain a code checking request;

a defect checking module 200, configured to respond to the code checking request, obtain a simulation system code, perform defect checking according to the simulation system code, obtain a defect checking result, when the defect checking result is a failure, determine a target defect identifier, a target error reason, and a target solution according to the defect checking result and a reason scheme model library, otherwise, obtain a print log, and determine whether there is identification log information of successful docking in the print log;

the simulation joint debugging module 300 is configured to, when identification log information of successful docking exists in the print log, obtain an interface type, obtain a parameter receiving manner and a calling configuration parameter according to the interface type, obtain a simulation joint debugging request, and perform simulation system docking joint debugging according to the simulation joint debugging request and the simulation system code, the parameter receiving manner, and the calling configuration parameter, to obtain a simulation joint debugging result.

Referring to fig. 3, a computer device, which may be a server and whose internal structure may be as shown in fig. 3, is also provided in the embodiment of the present application. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the computer designed processor is used to provide computational and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used for storing data such as a debugging method suitable for the docking agent system. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a debugging method suitable for a docking agent system. The debugging method is applied to a debugging system, the debugging system is used for the butt debugging of a consumption system and a service system and the agent system, and the agent system is used for establishing communication connection for requesting calling and responding between the consumption system and the service system; and, the method comprises: acquiring a code checking request; responding to the code inspection request, acquiring a simulation system code, performing defect inspection according to the simulation system code to obtain a defect inspection result, determining a target defect identifier, a target error reason and a target solution according to the defect inspection result and a reason scheme model library when the defect inspection result is failure, otherwise, acquiring a printing log, and judging whether identification log information of successful butt joint exists in the printing log; when the printing log has identification log information of successful butt joint, acquiring an interface type, and acquiring a parameter receiving mode and calling configuration parameters according to the interface type; acquiring a simulation joint debugging request; and according to the simulation joint debugging request, carrying out simulation system joint debugging according to the simulation system code, the parameter receiving mode and the calling configuration parameter to obtain a simulation joint debugging result.

An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the computer program implements a debugging method suitable for a docking agent system, the method is applied to a debugging system, the debugging system is used for docking and debugging a consumption system and a service system with the agent system, and the agent system is used for establishing a communication connection requesting invocation and response between the consumption system and the service system; and, the method comprises: acquiring a code checking request; responding to the code inspection request, acquiring a simulation system code, performing defect inspection according to the simulation system code to obtain a defect inspection result, determining a target defect identifier, a target error reason and a target solution according to the defect inspection result and a reason scheme model library when the defect inspection result is failure, otherwise, acquiring a printing log, and judging whether identification log information of successful butt joint exists in the printing log; when the printing log has identification log information of successful butt joint, acquiring an interface type, and acquiring a parameter receiving mode and calling configuration parameters according to the interface type; acquiring a simulation joint debugging request; and according to the simulation joint debugging request, carrying out simulation system joint debugging according to the simulation system code, the parameter receiving mode and the calling configuration parameter to obtain a simulation joint debugging result.

According to the debugging method which is suitable for the docking agent system and is executed, the defect inspection of the simulation system code is automatically realized by responding to the code inspection request, the docking process is simplified, the error of the simulation system code is rapidly checked through the code defect inspection, and the joint debugging efficiency is improved; error reasons and solutions are automatically given through a reason scheme model library, and developers are helped to quickly position and troubleshoot problems; by automatically simulating the butt joint debugging of the consumption system and/or the service system and the agent system, common problems in the butt joint process of the agent system and the agent system can be checked, the workload of development and testing is reduced, and the joint debugging efficiency is improved.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium provided herein and used in the examples may include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double-rate SDRAM (SSRSDRAM), Enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and bus dynamic RAM (RDRAM).

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, apparatus, article, or method that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, apparatus, article, or method. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, apparatus, article, or method that includes the element.

The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application, or which are directly or indirectly applied to other related technical fields, are also included in the scope of the present application.

Claims

1. A debugging method suitable for a docking agent system is applied to a debugging system, the debugging system is used for docking and debugging a consumption system and a service system with the agent system, and the agent system is used for establishing a communication connection for requesting calling and responding between the consumption system and the service system; and the number of the first and second groups,

the method comprises the following steps:

acquiring a code checking request;

acquiring a simulation joint debugging request;

2. The debugging method applicable to a docking agent system according to claim 1, wherein the step of performing defect inspection according to a simulation system code to obtain a defect inspection result, determining a target defect identifier, a target error reason and a target solution according to the defect inspection result and a reason scheme model library when the defect inspection result is failure, and otherwise acquiring a print log to determine whether identification log information of successful docking exists in the print log comprises:

3. The debugging method applicable to a docking agent system according to claim 2, wherein the step of performing defect inspection on a configuration item, JAR package dependency, a control layer, and an interface abstraction class on the simulation system code to obtain the defect inspection result, and obtaining the target defect identifier according to the defect inspection result when the defect inspection result is a failure includes:

4. The debugging method for a docking agent system according to claim 3, wherein the step of obtaining a configuration file to be checked from the simulation system code, performing configuration item defect check according to the configuration file to be checked to obtain a configuration item check result, and determining the target defect identifier according to the configuration item check result when the configuration item check result is failure comprises:

acquiring the configuration file to be checked from the simulation system code;

5. The debugging method applicable to the docking agent system of claim 3, wherein the step of performing JAR package dependency check according to a simulation system code to obtain a JAR package dependency check result, and when the JAR package dependency check result is a failure, determining the target defect identifier according to the JAR package dependency check result comprises:

obtaining a JAR packet list of the proxy system;

6. The debugging method applicable to a docking agent system according to claim 3, wherein the step of performing control layer defect inspection according to the simulation system code to obtain a control layer defect inspection result, and determining the target defect identifier according to the control layer defect inspection result when the control layer defect inspection result is a failure includes:

acquiring a control layer code from a simulation system code;

7. The debugging method applicable to the docking agent system according to claim 1, wherein the steps of obtaining an interface type when the print log has identification log information of successful docking, obtaining a parameter receiving manner and calling configuration parameters according to the interface type include:

8. A debugging device suitable for a docking agent system is applied to a debugging system, the debugging system is used for docking and debugging a consumption system and a service system and the agent system, and the agent system is used for establishing a communication connection for requesting calling and responding between the consumption system and the service system; and the number of the first and second groups,

the device comprises:

the request acquisition module is used for acquiring a code check request;

9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.