Java code quality inspection method, device and apparatus and storage medium

Abstract

The invention relates to the technical field of computers, in particular to a Java code quality inspection method, device and apparatus and a storage medium. The method comprises the steps of obtaining at least one Java code file to be uploaded; inputting at least one Java code file to be uploaded into an open source analysis tool; performing traversal of abstract syntax trees, performing comparative detection on each row of java code statements in an abstract syntax book through preset rule analysis and obtaining a detection result, wherein the detection result comprises an array and a regular expression, and the array at least comprises a granularity function of the to-be-analyzed Java code and a result, which does not meet a preset rule, in a class in the to-be-analyzed Java code; storing the granularity function and a result, which does not accord with a preset rule, in the to-be-analyzed Java code into a first set; calculating a difference value between the first set and as condition set to obtain a non-compliance information set; and if the non-compliance information set is not the empty set, blocking the hook of the Git and returning a result which does not accord with the preset rule to the user. The quality problem of uploaded codes is reduced.

Description

technical field [0001] The present application relates to the field of computer technology, in particular to a Java code quality inspection method, device, device and storage medium. Background technique [0002] The evaluation of code quality is the key to measuring a programmer's ability in the IT field, and it is also one of the foundations for a robust project. If there are no comments and irregular formats in the written code, the written code will be obscure. However, the existing codes are judged based on the existing syntax of the programming language, and the possible results of the program are predicted. In the case of high concurrency, the results of the multi-user thread test program are judged, so that the code looks normal. Logic, however, may also harbor fatal hidden dangers. Most of the traditional code inspection is to check code defects manually, or to check during the development process of developers through the development tool plug-ins provided by ope...

AI Technical Summary

Problems solved by technology

If there are no comments and irregular formats in the written code, the written code will be obscure

However, the existing codes are judged based on the existing syntax of the programming language, and the possible results of the program are predicted. In the case of high concurrency, the results of the multi-user thread test program are judged, so that the code looks normal. Logic may also hide fatal hidden dangers

Most of the traditional code inspection is to check code defects manually, or to check during the development process of developers through the development tool plug-ins provided by open source projects. Developers are required to actively cooperate with the company's standard use. If developers do not take the initiative to accept such plug-ins, they may not follow some development rules, resulting in hidden dangers in the code. At least, there will be problems in the running process, and at worst, it will cause the company to make technical mistakes. resulting in loss

Images