Software continuous integration inspection method and system

Abstract

The invention is suitable for the technical field of software integration and testing, and relates to a software continuous integration inspection method and system.The method comprises the steps that static code inspection is executed, and classification testing results are recorded and fed back; performing code review, and submitting a review conclusion to a code management platform; initiating an inspection application form, and checking the validity of the process by the system; the system automatically captures codes through the code baseline labels, counts modification code lines and modifiers, executes compiling scripts, and automatically compiles the captured source codes; encrypting and packaging source codes, automatically summarizing code modification instructions, and pushing processes to a high-level supervisor; executing a test, and uploading a test result to a defect management system; confirming modification codes and submitting the codes; initiating an inspection application again and associating the inspection application to the code modification record; and after the test is qualified, the system carries out filing and publishing. The method is simple in process and convenient to operate, the software inspection work efficiency is improved, and the defect rate of software inspection is also reduced.

Description

Technical Field

[0001] The present invention belongs to the technical field of software integration and testing, and particularly relates to a software continuous integration inspection method and system. Background Art

[0002] In software engineering, after software is coded and implemented, it is necessary to verify whether the software functions and performance meet the requirements and design requirements through testing activities. The testing methods include unit testing, integration testing, and system testing, etc. The existing software inspection and testing methods mostly adopt manual methods or partially informatized integration methods. After software development is completed, compilation, packaging, and debugging are carried out. Due to cost considerations in testing, unit testing is rarely performed. Often, simple self-testing is directly used for inspection, and an inspection application is filled out using Office documents or a testing system. The content includes relevant information such as source code packages, executable program packages, software modification descriptions, operating environments, and deployment methods. After receiving the inspection application, testers build a testing environment, install the software, design test cases for integration or system testing, record testing defects after testing, and feedback to developers for modification and regression testing until the testing is qualified. This method lacks accurate and effective defect tracking and management means, and has problems such as low work efficiency and high defect rates in back-end integration testing and system testing.

[0003] The patent application with the publication number CN111813678A provides a self-checking test system for network software development, including a software development module, a development database, a code testing module, a function testing module, and a test case library; the development database is respectively connected to the software development module, the test management module, the regression testing module, the recovery module, the modification self-checking analysis module, the code testing module, and the detected code feedback module; the test management module is connected to the auxiliary testing module, the regression testing module is connected to the recovery selection module, the recovery selection module is connected to the simulation recovery self-checking module, the simulation recovery selection module is connected to the modification record module, and the modification record module is connected to the recovery module; the function testing module is respectively connected to the test script recording module, the compatibility testing module, and the speed control module, the test script recording module is connected to the modification self-checking analysis module, and the compatibility testing module is connected to the configuration condition selection module. This patent application has its own self-checking module and also belongs to simple self-testing and inspection, with the same drawbacks as the prior art.

[0004] Therefore, how to provide a software inspection method with high work efficiency and low defect rate is an urgent problem to be solved by those skilled in the art. Summary of the Invention

[0005] In view of the deficiencies of the prior art, the purpose of the present invention is to provide a software continuous integration inspection method to solve the problems of low work efficiency and high defect rate in the software inspection and testing methods in the prior art; in addition, the present invention also provides a software continuous integration inspection system.

[0006] To solve the above technical problems, the present invention adopts the following technical solutions:

[0007] In the first aspect, the present invention provides a software continuous integration inspection method, including the following steps:

[0008] S10. Developers complete code development and submit the code to the code repository. The system automatically performs static code checks, records and feedbacks classified test results;

[0009] S20. Members of the development project team conduct code reviews and submit the review conclusions to the code management platform, linking to specific code lines;

[0010] S30. Developers initiate an inspection application form, with the type being standard inspection, select the code baseline label and the current inspection branch label, fill in the hardware platform and software version, enter the compilation script, and the system checks the legality of the process;

[0011] S40. The system automatically grabs the code through the code baseline label, counts the modified code lines and the modifiers, executes the compilation script, automatically compiles the grabbed source code, and automatically returns if the compilation fails or the compilation warning information level exceeds the set value;

[0012] S50. The system encrypts and packages the source code through an encryption algorithm, automatically summarizes the code modification instructions, and pushes the process to the senior supervisor;

[0013] S60. After confirmation by the senior supervisor, it is pushed to the testing department. The testing department receives the inspection application, builds a test environment and conducts tests, and uploads the test results to the defect management system;

[0014] S70. The system grabs the test records and pushes them to the developers, and the developers confirm the modified code and submit it;

[0015] S80. Developers initiate an inspection application again, with the application type being replacement inspection, select the code baseline label and the current inspection branch label, set the status of each test defect to regression test, and associate it with the code modification record;

[0016] S90. Repeat the above steps until the test is qualified, and the system archives and publishes.

[0017] Further, in the step S10, when the system detects that code is submitted to the repository, it immediately triggers automatic code pulling, calls a static code checking tool to perform static code checking, and the checking results include several fatal problems, serious problems, and general problems.

[0018] Further, in the step S20, the review adopts an online or offline peer review form. After the review, the review conclusion is uploaded, and the review conclusion includes passing the review, review problems, and review suggestions.

[0019] Further, in the step S30, the system checks the legality of the process specifically including:

[0020] Statistical code manual review coverage rate is ensured that each submission is reviewed. If the coverage rate does not meet the standard, the process is rolled back;

[0021] Check whether all the remaining problems in branch testing have been solved. If not, it is automatically rolled back;

[0022] Check that there are no fatal problems and serious problems in static code checking and the number of general problems does not exceed the set value. Otherwise, it is automatically rolled back.

[0023] Further, for the code submitted each time, code review records are captured through keywords. Those without review records or with unprocessed review problems are all rolled back.

[0024] Further, the system accesses the data of the defect management system. Each defect status includes new, development processing, regression testing, and closed. When there are still remaining defects in the branch of the reported code that have not been closed, it is directly rolled back.

[0025] Further, the system queries the results of static code checking, calculates weights according to the problem level and quantity, and directly rolls back when it exceeds the set threshold.

[0026] Further, in the step S40, the compilation script is edited and entered by the developer in the step S30. The system is only responsible for executing the compilation and capturing the compilation results and process warning information during the compilation. If the compilation is unsuccessful or the level of compilation warning information exceeds the set value, it is automatically rolled back.

[0027] In the second aspect, the present invention also provides a software continuous integration inspection system, including:

[0028] An integrated inspection management system for integrating and using corresponding professional capabilities, including inspection application, inspection review, test assignment, test task tracking, and archiving;

[0029] A code repository and management platform for managing source code;

[0030] A static code checking platform for performing static code checking and outputting the checking results;

[0031] A defect management system for managing defects tested by testers.

[0032] The integrated inspection application management system is respectively communicatively connected to the code repository management platform, the static code management platform, and the defect management system.

[0033] Compared with the prior art, the software continuous integration inspection method and system provided by the present invention have at least the following beneficial effects:

[0034] Existing software inspection and testing methods mostly adopt manual methods or partially informatized integration methods, lacking accurate and effective defect tracking and management means, resulting in problems such as low work efficiency, high defect rates in back-end integration testing and system testing. The process of the present invention is simple and convenient to operate. Based on the inspection application, it automatically grabs the code, compiles and packages it, and identifies compilation exception information, automatically executes static code checks, compares the code scale and historical defects, effectively improving the work efficiency of inspection and software integration and delivery, and reducing the software inspection defect rate. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the solution of the present invention, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0036] Figure 1 It is a flowchart of a software continuous integration inspection method provided by an embodiment of the present invention;

[0037] Figure 2 It is a structural block diagram of a software continuous integration inspection system provided by an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0038] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those of ordinary skill in the technical field to which this invention belongs; the terms used in this specification are only for the purpose of describing specific embodiments and are not intended to limit the present invention. For example, the terms "length", "width", "upper", "lower", "left", "right", "front", "rear", "vertical", "horizontal", "top", "bottom", "inner", "outer", etc. indicate the orientation or position based on the orientation or position shown in the drawings, and are only for convenience of description and cannot be understood as a limitation to the technical solution of the present application.

[0039] In the description, claims and the above description of the drawings of the present invention, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion; the terms "first", "second", etc. in the description, claims or the above drawings of the present invention are used to distinguish different objects, rather than to describe a specific order. In the description, claims and the above description of the drawings of the present invention, when an element is referred to as being "fixed to" or "mounted on" or "disposed on" or "connected to" another element, it may be directly or indirectly located on that other element. For example, when an element is referred to as being "connected to" another element, it may be directly or indirectly connected to that other element.

[0040] In addition, the mention of "embodiments" herein means that the specific features, structures or characteristics described in connection with the embodiments may be included in at least one embodiment of the present invention. The phrase appears at various places in the description and does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0041] The present invention provides a software continuous integration inspection method, which is applied to the software inspection and testing process. The software continuous integration inspection method includes the following steps:

[0042] S10. The developer completes the code development and submits the code to the code repository. The system automatically performs static code inspection, records and feeds back the classified test results; S20. The members of the development project team conduct code review and submit the review conclusion to the code management platform, linking to the specific code lines; S30. The developer initiates an inspection application form, with the type being standard inspection, selects the code baseline label and the current inspection branch label, fills in the hardware platform and software version, and enters the compilation script. The system checks the legality of the process; S40. The system automatically grabs the code through the code baseline label, counts the modified code lines and the modifiers, executes the compilation script, automatically compiles the grabbed source code, and automatically returns if the compilation is unsuccessful or the level of the compilation warning message exceeds the set value; S50. The system encrypts and packages the source code through an encryption algorithm, automatically summarizes the code modification description, and pushes the process to the senior supervisor; S60. After the senior supervisor confirms, it is pushed to the testing department. The testing department receives the inspection application, sets up the test environment and conducts the test, and uploads the test results to the defect management system; S70. The system grabs the test records and pushes them to the developer. The developer confirms the modified code and submits it; S80. The developer initiates an inspection application again, with the application type being replacement inspection, selects the code baseline label and the current inspection branch label, sets the status of each test defect to regression test, and associates it with the code modification record; S90. Repeat the above steps until the test is qualified, and the system archives and publishes.

[0043] The process of the present invention is simple and the operation is convenient, which improves the work efficiency of software inspection and also reduces the defect rate of software inspection.

[0044] In order to enable the personnel in the technical field to better understand the solution of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings.

[0045] The present invention provides a software continuous integration inspection method, which is applied to the software inspection and testing process, such as Figure 1 As shown, in this embodiment, the software continuous integration inspection method includes the following steps:

[0046] S10. The developer completes the code development and submits the code to the code repository GIT, and the system automatically performs static code inspection and records and feeds back the classified test results.

[0047] Specifically, in this embodiment, when the system detects that code is submitted to the repository, it is immediately triggered to pull the code, call the static code inspection tool (the locally deployed AI model), and automatically perform static code inspection.

[0048] S20. The members of the development project team conduct code reviews and submit the review conclusions item by item to the code management platform, linking to the specific code lines.

[0049] Specifically, in this embodiment, the review adopts the form of online or offline peer review. After the review, the review conclusions are uploaded, and the conclusions include: review passed, review issues, and review suggestions.

[0050] S30. The developer initiates an inspection application form of the standard inspection type, selects the code baseline label and the current inspection branch label, fills in the hardware platform, software version, and enters the compilation script, such as the Linux cross-compilation script, and the system checks the legality of the process.

[0051] Specifically, in this embodiment, the system's checking of the process legality specifically includes:

[0052] Statistical code manual review coverage rate to ensure that each submission is reviewed. If the coverage rate does not meet the standard, the process is returned. For the code submitted each time, the code review records are captured through keywords. If there is no review record or there are review issues that have not been processed, it is returned.

[0053] Check whether all the remaining problems in the branch test have been solved. If not, it is automatically returned. The system accesses the data of the defect management system, and each defect status includes new, development in progress, regression testing, closed, etc. When there are still remaining defects in the branch of the inspected code that have not been closed, it is directly returned.

[0054] Check that there are no fatal problems and serious problems in the static code inspection and the general problems do not exceed the set value, otherwise it is automatically returned.

[0055] The system queries the results of static code checking, calculates weights based on the level and number of problems, and directly returns them when they exceed the set threshold.

[0056] S40. The system automatically captures the code through the code baseline tag, counts the modified code lines and the modifiers, and executes the compilation script to automatically compile the captured source code. If the compilation fails or the compilation alarm level exceeds the set value, it will automatically return.

[0057] Furthermore, in this embodiment, the compilation script is edited and entered by the developer in step S30. The system is only responsible for executing the compilation and capturing the compilation results and process alarm information during the compilation process. If the compilation fails or the compilation alarm information level exceeds the set value, it will automatically return.

[0058] S50. The system encrypts and packages the source code using an encryption algorithm, automatically summarizes the code modification instructions, and pushes the process to senior executives.

[0059] S60: After confirmation by the senior manager, it is pushed to the testing department. The testing department receives the inspection application, builds the test environment, executes the test, and uploads the test results to the defect management system.

[0060] S70. The system captures the test records and pushes them to the developer, who confirms the code modification and submits it.

[0061] Specifically, in this embodiment, the system automatically captures test defects and pushes them to developers using OA messages and system messages.

[0062] S80. The developer initiates an inspection application again, with the application type being replacement inspection, and selects the code baseline label and the current inspection branch label. The status of each test defect is set to regression test and associated with the code modification record.

[0063] S90. Repeat the above steps until the test is passed, and the system will archive and release it.

[0064] The embodiment of the present invention further provides a software continuous integration inspection system, including:

[0065] The integrated inspection report management system is used to integrate and use corresponding professional capabilities, including inspection application, inspection review, test allocation, test task tracking and archiving; the code warehouse and management platform is used to manage source code; the static code inspection platform is used to perform static code inspection and output inspection results; the defect management system is used to manage defects tested by testers; the integrated inspection report management system is communicated and connected with the code warehouse management platform, static code management platform and defect management system respectively.

[0066] The software continuous integration inspection method and system described in the above embodiments, compared with the prior art, the existing software inspection and testing methods mostly adopt manual methods or partial informatization integration methods, lacking accurate and effective defect tracking and management means, resulting in problems such as low work efficiency, high defect rates in back-end integration testing and system testing. The process of the present invention is simple and convenient to operate. Based on the inspection application, it automatically grabs the code, compiles and packages it, and identifies compilation exception information, automatically performs static code inspection, compares the code scale and historical defects, effectively improves the work efficiency of inspection and software integration and delivery, and reduces the software inspection defect rate.

[0067] Obviously, the embodiments described above are only the preferred embodiments of the present invention, rather than all embodiments. The preferred embodiments of the present invention are given in the drawings, but do not limit the patent scope of the present invention. The present invention can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosed content of the present invention more thorough and comprehensive. Although the present invention has been described in detail with reference to the foregoing embodiments, for those skilled in the art, they can still modify the technical solutions recorded in the foregoing specific embodiments, or perform equivalent replacements on some of the technical features. Any equivalent structure made by using the specification and drawings of the present invention, directly or indirectly applied in other related technical fields, is equally within the scope of the patent protection of the present invention.

Claims

1. A software continuous integration inspection method, characterized in that: The following steps are involved: S10. After the developer completes code development and submits the code to the code repository, the system automatically performs static code checking, records and feeds back classification test results; S20. Development project team members conduct code reviews and submit review conclusions to the code management platform, linking to specific code lines; S30. The developer initiates an inspection application form, the type is standard inspection, selects the code baseline label and the current inspection branch label, fills in the hardware platform and software version, enters the compilation script, and the system checks the legality of the process; S40, the system automatically captures the code through the code baseline tag, counts the modified code lines and the modifiers, executes the compilation script, and automatically compiles the captured source code. If the compilation fails or the compilation warning information level exceeds the set value, it will be automatically returned; S50, the system encrypts and packages the source code through encryption algorithms, automatically summarizes the code modification instructions, and pushes the process to senior managers; S60: After confirmation by the senior manager, the application is sent to the testing department, which receives the inspection application, builds the test environment, performs the test, and uploads the test results to the defect management system. S70, the system captures the test records and pushes them to the developer, who confirms the code modification and submits it; S80. The developer initiates an inspection application again, with the application type being replacement inspection. The developer selects the code baseline label and the current inspection branch label, sets the status of each test defect to regression test, and associates it with the code modification record. S90. Repeat the above steps until the test is passed, and the system archives and releases it.

2. A software continuous integration inspection method according to claim 1, characterized in that: In step S10, when the system detects that code has been submitted to the warehouse, it immediately triggers automatic code retrieval and calls a static code checking tool to perform static code checking. The checking results include several fatal problems, serious problems and general problems.

3. A software continuous integration inspection method according to claim 1, characterized in that: In step S20, the review is conducted in the form of online or offline peer review, and the review conclusion is uploaded after the review. The review conclusion includes review approval, review issues and review suggestions.

4. A software continuous integration inspection method according to claim 1, characterized in that: In step S30, the system checks the legitimacy of the process specifically including: Count the code manual review coverage to ensure that each submission is reviewed. If the coverage does not meet the requirements, the process will be returned. Check whether all remaining issues of branch testing have been resolved. If not, the test will be automatically returned. Check the static code to ensure there are no fatal or serious problems and that general problems do not exceed the set value, otherwise the code will be automatically returned.

5. A software continuous integration inspection method according to claim 4, characterized in that: For each code submission, the code review record is captured by keywords. Codes without review records or with unresolved review issues will be returned.

6. A software continuous integration inspection method according to claim 4, characterized in that: The system accesses the data of the defect management system. The status of each defect includes new creation, development processing, regression testing, and closure. When there are still legacy defects in the branch of the inspection code that have not been closed, it will be returned directly.

7. A software continuous integration inspection method according to claim 4, characterized in that: The system queries the results of static code checking, calculates weights based on the level and number of problems, and directly returns them if they exceed the set threshold.

8. A software continuous integration inspection method according to claim 1, characterized in that: In step S40, the compilation script is edited and entered by the developer in step S30. The system is only responsible for executing the compilation and capturing the compilation results and process alarm information during the compilation process. If the compilation is unsuccessful or the compilation alarm information level exceeds the set value, it will automatically return.

9. A system using the method according to any one of claims 1 to 8, characterized in that: include: Integrated inspection and testing management system, used to integrate and use corresponding professional capabilities, including inspection and testing application, inspection and testing review, test allocation, test task tracking and archiving; Code repository and management platform, used to manage source code; Static code checking platform, used to perform static code checking and output the checking results; Defect management system, used to manage defects tested by testers; The integrated inspection reporting management system is respectively connected to the code repository management platform, the static code management platform, and the defect management system in communication.

Images