Method and device for automatically detecting interface service abnormity

Abstract

The invention discloses a method for automatically detecting interface service abnormity. The method comprises the following steps: reading a system configuration file; reading an interface IP address; judging whether a network at the interface is normal, if the network is normal, analyzing a result of requesting an interface URL address and recording a detected interface log report; if the network is abnormal, directly recording the detected interface log file; judging whether an undetected interface is existent, if the undetected interface is inexistent, judging whether to send the log report to test or development related personnel; if the undetected interface is existent, returning to continuously read the system configuration file; if the interface is abnormal, sending the log report to the test or development related personnel; if the interface is normal, directly ending the task. The technical scheme disclosed by the invention can be applied to automatically detecting a third-party interface in system initialization, and can be applied to automatically detecting the third-party interface when the system is in interface abnormity.

Description

technical field [0001] The invention relates to the technical field of computer networks, in particular to a method and device for automatically detecting interface service anomalies. Background technique [0002] In order to improve the coupling of the system, many internal and external interfaces will be provided between the systems. These interfaces are maintained by other teams, and the testers test or jointly debug the interfaces during the test process and communicate with the third-party interface maintenance team. Time plays a large part in the project software testing life cycle. At present, when there is a problem with system interruption, the following measures are generally taken: manually check the system log, locate the specific third-party interface, and initially investigate the cause of the problem. There are mainly two situations: one is the problem of the system, and the system Relevant personnel locate and track and solve problems; the other is third-par...

AI Technical Summary

Problems solved by technology

In either case, it is very passive for testers. If multiple modules use the same interface, and multiple modules correspond to different testers, then there will be multiple testers who may be testing at the same time. While investigating issues due to the same interface

[0005] 2. Inefficient maintenance of third-party interfaces

[0008] The system contains multiple third-party interfaces. Due to network abnormalities or other environmental reasons, multiple interfaces are interrupted at the same time, and multiple interfaces work serially. Due to the passive discovery of interface problems and the inefficiency of maintenance work, resulting in All interface exception handling links are repetitive tasks

[0009] 4. Too much manual communication work

[0010] During the joint debugging test, it is often found that the test is interrupted due to the mismatch of the input or output parameters of the two interfaces. In this case, the communication time between the two parties will occupy more than 50% of the actual joint debugging time.

Images